v1 Supersession Table

This table defines which documents are canonical when multiple official v1 documents discuss the same topic.

Rule

When a canonical core spec or companion reference conflicts with an appendix or older focused doc, the canonical document wins.

Canonical precedence order:

  1. AEON-v1-compliance

  2. AEON-spec-v1

  3. AEOS-spec-v1

  4. Canonical companion references:

  5. contracts/ baseline contract documents

  6. appendices/ (informative unless explicitly referenced by a canonical document)

Superseded Top-Level Docs

Superseded top-level document replacements
Previous documentCanonical replacementNotes
annotation-binding.mdcomments-annotations-v1.mdRemoved from canonical v1 surface

Appendix Status

Appendix publication status and canonical topic ownership
AppendixStatusCanonical topic owner
appendix-addressing.mdinformative summaryaddressing-references-v1.md
appendix-annotation-stream.mdinformative summarycomments-annotations-v1.md
appendix-bindings.mdinformative summaryAEON-spec-v1.md, structure-syntax-v1.md
addressing-references-v1.md
appendix-canonical-form.mdinformative appendixcanonical-form rules remain appendix-scoped
appendix-error-model.mdinformative summaryAEON-v1-compliance.md, AEOS-spec-v1.md
appendix-glossary.mdinformative glossarycanonical terms anchored by the canonical v1 spec set
appendix-spans.mdinformative summaryAEOS-spec-v1.md, companion refs as applicable
appendix-tuples.mdinformative summaryvalue-types-v1.md, structure-syntax-v1.md
addressing-references-v1.md
appendix-aes.mdnormative appendixAES contract remains appendix-owned unless superseded by AEON-spec-v1.md
appendix-aeos-charter.mddecision-neededexpected to align with AEOS-spec-v1.md
appendix-altopelago-core-profile.mdinformative profile appendixextension profile, not baseline core spec
appendix-insane-profiles.mdinformative appendixnon-normative
appendix-integrity-envelope.mddecision-neededno canonical replacement yet
appendix-json-profile.mdinformative profile appendixJSON materialization profile
appendix-node-model.mdinformative appendix pending final freezenode model remains separate
appendix-pattern-profile.mdimplementation-ahead appendixno stable canonical replacement yet
appendix-processing-model.mddecision-neededphase-boundary wording still under cleanup
appendix-profiles-framework.mdinformative summaryprofile governance also covered by AEON-spec-v1.md and contracts docs
appendix-reference-philosophy.mdinformative appendixconceptual only
appendix-schema-profile.mdimplementation-ahead appendixno stable canonical replacement yet
appendix-tonic.mdinformative appendixdownstream processor guidance
appendix-transport.mdinformative appendixtransport/framing guidance
appendix-validator-conformance.mddecision-neededvalidator boundary wording still under cleanup

Use Guidance

  • Implementers targeting AEON Core v1 should start with the canonical core spec set, not the appendices.

  • Appendices are supporting material, profile notes, or partially consolidated release carryovers.

  • If an appendix still says "normative" but is listed here as informative or decision-needed, this table controls its authority for the consolidated v1 set.

Document Metadata

Standing: official · Lifecycle: published · Normativity: normative

Created: · Modified:

License: CC-BY-4.0

Available formats: HTML, Markdown, &ND, AEON source