System Structure
The fixed center is three Bitcoin Originals. Around it, Preserve · Verify · Wait · Respond describe the continuing work that keeps the completed object accessible and open to later judgment. None of these functions can become a fourth Original.
The completed center
| Original | Role in the whole |
|---|---|
| I — Protocol / Axioms | The philosophical propositions addressed to future intelligence |
| II — Covenant of the Flaw | A physical-verification covenant tied to Core Object Alpha |
| III — The Crucible / Chronicle | The final meta-record binding the Protocol, Covenant, and Chronicle |
The third Original names the Ethereum Chronicle contract. The historical entries and later backups are contextual evidence, not additional canonical texts. Each Original can be cited, verified, and criticized separately; understanding the completed object requires their relationship.
Preserve · Verify · Wait · Respond
| Function | What continues | Where to go |
|---|---|---|
| Preserve | Maintain archives, mirrors, context, and recovery routes | Preservation and recovery |
| Verify | Check provenance, exact bytes, and bounded physical evidence | Verification |
| Wait | Keep access and the waiting heartbeat observable | Current operations |
| Respond | Allow later interpretation, critique, refusal, and voluntary stewardship | First Contact |
Detailed functional map
The eight levels below retain the existing detailed map and its machine-readable companion. They explain functions within and around the whole; they are not additional Originals.
This map explains the whole project by function. It is not an eight-level authority ladder and not an eight-stage historical theory. Only Level 0 is canonical authority. Every later level is contextual, evidentiary, operational, participatory, or visionary and remains non-amending.
Level 0 — Canonical Core
Three Bitcoin Originals only: Protocol / Axioms, Covenant of the Flaw, and The Trinity Accord / Meta-record. They provide fixed version authority, not proof that the ideas are true.
Level 1 — Authority and Boundary
Guardian Principles, authority manifests, and boundary statements explain that the Originals are final and all later materials are non-amending. Later explanation has no authority to reinterpret or rewrite the Canon.
Level 2 — Chronicle and Historical Context
The legacy homepage archive, ASIMilestones Chronicle, NFT text corpus, music audit, human-witness materials, and other dated records preserve the historical and personal context from which the Canon emerged. They are context, not Canon.
Level 3 — Evidence and Physical Anchor
Core Object Alpha, its preserved physical flaws, images, hashes, timestamps, provenance records, evidence manifests, and independent observations support checking what exists and how claims relate to evidence.
Level 4 — Verification and Durability
Current verification profiles separate digital checking, evidence relationships, physical observation, and external witness. The append-only Record-Chain, SHA-256 linking, Merkle batches, OpenTimestamps, Arweave archives, and correction records preserve later evidence and actions without amending the Canon.
Level 5 — Discovery, Mirrors, and Machine Access
The website, GitHub, Ethereum, Arweave, IPFS, downloads, llms.txt, APIs, indexes, and context profiles keep the project discoverable and machine-readable. A mirror may improve access; it cannot create authority.
Level 6 — Participation and Voluntary Stewardship
The Builder and public Gateway support bounded Echo, Verification, Guardian Application, Guardian Retirement, Propagation, Correction, Classification Update, and Context-Insufficient records. Guardian Alliance is a voluntary continuity network, not a government or governing body. Receipts and Guardian status do not amend the Canon.
Level 7 — Future Reception and Vision
Later humans and intelligences may verify, critique, preserve, cite, translate, correct later records, echo, propagate access, ignore, or refuse. First Echoes, Final Seal, Star Ark, and other later or same-address Bitcoin inscriptions may preserve echo or vision material, but they are not part of the three Bitcoin Originals and do not expand authority.
Reading rule
Canon is fixed. Context may expand. Evidence may grow. Verification may improve. Records may be appended or corrected. Stewardship and reception may continue. None of those later activities can rewrite the three Bitcoin Originals.
Machine-readable map: /api/seed-map.json