10 / AMUNCHAIN
APTS standard
A project token begins with an approved project.
The proposed Amun Project Token Standard binds each authorized token to its legal entity, project passport, governance decision, risks and funding controls.
Proposed mandatory fields
| Field | Purpose |
|---|---|
| Project ID | Link to the authorized project. |
| Issuing entity & jurisdiction | Identify the legal issuer and governing jurisdiction. |
| Legal classification | Utility, debt, asset-linked, revenue participation or other assessed category. |
| Maximum supply | Define the project-specific issuance ceiling. |
| Funding target | Disclose the required amount and use of funds. |
| Treasury contract | Governed treasury or escrow, never a personal wallet. |
| Governance proposal ID | Reference the actual authorization. |
| Feasibility hash | Bind the token to the approved study and version. |
| Risk disclosure hash | Reference the published risk document. |
| Milestone schedule | Define release conditions and required evidence. |
| Token rights | State economic and usage rights clearly. |
| Exit / failure rules | Define what happens on suspension, failure or closure. |
Governed fund release
Funding enters a project treasury or escrow. Release requires governance authorization and milestone verification before execution. Raising funds does not authorize unrestricted transfer to the execution team.
APTS is a proposed standard, not a deployed contract or available issuance service. Each project requires legal classification and explicit rights before authorization.
Project approval requirementsSource: Master Blueprint v1.0, pages 20–21 · View source PDF