AST Core Canon
Mission, first principles, PoT criteria P1–P4, token protocol, Release Phase, formulas, hard prohibitions and invariants I1–I9.
Read the canon →Resources · AST
AST documentation
The AST repository is public. The Core Canon is the single binding source; every layer specification, module and automated guard is checked against it.
Ratified technical decisions
The decisions taken before implementation, and why.
Read →Layer specifications
Specifications per layer and module — written before code, visible in the tree.
Browse layers →Release 1.2.0
What the pilot-ready baseline includes — and, just as clearly, what it does not.
Release notes →Institutional portal
Edge admission, signature verification, institution authentication and the public explorer.
Portal docs →Security policy
How to report a vulnerability responsibly.
SECURITY.md →Canon enforced by code
Every change to the repository runs automated guards that fail the build if the canon is broken — for example: no issuance path that bypasses Proof of Transaction or NodeChain, no executive powers for the All-Seeing Eye, no ERC standard treated as the source of truth, and no vocabulary that would turn payment for work into something else.
The canon changes only through a formal amendment procedure, and every amendment is logged in the canon itself.
Suggested reading order
- Decision-makers — AST overview, then System: can and cannot.
- Auditors and reviewers — the Core Canon, then the white paper.
- Engineers — the technical deep dive, then the layer specifications and ratified decisions.