Aediles (AEDI) — White Paper
Status: Research draft for issuer review · 20 November 2026 Directory: https://xmarkets.ca/tokens/ Linked website: https://aediles.ca/ Network: Avalanche C-Chain. Verified contract: `0x0895AD723c1268456625E18A5788491c79C99CDE`.
Executive summary
Aediles is the sector ERP for waste management and waste removal: landfills, and industrial, commercial and residential cleanups, including spill and specialist cleanups. This paper outlines a coherent product and accountability model for that purpose. It does not certify that all described workflows are deployed. The intended users are waste-management operators, cleanup contractors, municipalities and residents.
Problem and product
Sector work is often split across documents, messages and isolated applications. The proposed product gives authorized participants a shared operating record for waste collection and removal jobs, landfill operations, cleanup projects and spill-response records. Each record should have an owner, timestamp, version history and permission boundary. An event should be considered verified only when the source evidence and reviewer decision can be inspected.
Token utility and access
The directory presents AEDI as the sector token. Access is a balance hold, never a payment: the participant connects a wallet, the product verifies its balance, and permissions apply at the workspace and module level. Held tokens are never spent, transferred or escrowed by the gate. Aediles' sector suite is 27 modules; the full-suite hold is 28 AEDI (entry plus one per module). Holding a token does not by itself convey ownership of an underlying asset, a claim on revenue, or decision rights. Supply, mint authority and burn rules are not stated in this paper; they must be published from the deployed contract and actual product terms.
Operating workflow
- An organization creates an isolated workspace and assigns authorized users.
- A user creates or imports a record covering waste collection and removal jobs, landfill operations, cleanup projects and spill-response records.
- A designated reviewer checks supporting evidence and records corrections without erasing the audit trail.
- The workspace reports status to the people entitled to see it; external participants see only their permitted subset.
- If blockchain anchoring is enabled, publish a hash or batch proof while protecting confidential source documents.
Governance, security and measurements
Publish the entity responsible for the service, treasury and contract upgrades. Separate administrators from reviewers and provide a process for correcting errors and revoking access. Monitor adoption by active organizations, completed workflows, validated evidence and dispute resolution, rather than by token price. Protect personal and commercial data with encryption, retention limits, access logs and incident response. Smart-contract claims should be backed by deployed code and an audit.
Site-specific findings and publication checks
The public directory establishes the sector positioning and linked website. Product features, token economics and rollout dates require issuer confirmation and direct testing before publication. The linked site was not reliably accessible during this review; no site-specific functionality is asserted.
Before an issuer-approved release, add the canonical token name and verified contract, issuer/legal entity, token supply and allocation, access fee schedule, custody and treasury controls, technical architecture, audit reports, operational status, roadmap with dates, and jurisdiction-specific risk disclosures. No return, liquidity or redemption is promised in this draft.
Sources
- XMarkets directory: https://xmarkets.ca/tokens/
- Project site: https://aediles.ca/