Defines appendix scope, authority boundaries, and precedence relative to canonical v1 specs.
Status: Draft
AEON v1 Appendices
Appendices provide detailed reference material and conceptual guides for AEON Core and AEOS. The documents below are grouped by concern and publication order.
Guidance by use case:
- New to AEON? Start with the Glossary and Processing Model to understand core concepts.
- Building a parser or processor? See the Structure, Addressing and References, Tuples, and Node Model documents.
- Creating schemas or validators? See the AEOS Charter, Schema Profile, and Authority Boundary documents.
- Understanding architecture and philosophy? See the Reference Philosophy, Profiles Framework, and Binding Identity guides.
Orientation
Appendix - Glossary
DraftNormative terminology used across AEON Core, AEOS, and companion references.
Status: Draft
Core Semantics
Binding identity model, uniqueness constraints, and canonical identity behavior.
Status: informative summary for consolidated v1
Appendix - Spans
DraftSource span representation and diagnostic location semantics.
Status: informative summary for consolidated v1
Appendix - Error Model
DraftError code shape, failure classes, and deterministic diagnostic reporting conventions.
Status: informative summary for consolidated v1
Conceptual phase pipeline from lexing through finalization, including assignment events.
Status: decision-needed for consolidated v1
Assignment event stream structure and event-level consistency expectations.
Status: Normative
Structured annotation channel model and source-order emission behavior.
Status: informative summary for consolidated v1
Appendix - Addressing
DraftDetailed path addressing examples and canonical segment traversal clarifications.
Status: informative summary for consolidated v1
Tuple semantics and indexed path behavior at parse, pathing, and validation boundaries.
Status: informative summary for consolidated v1
Appendix - Node Model
UnspecifiedNode literal model and representation boundaries relative to canonical pathing.
Status: Optional, profile-gated feature
Canonicalization conventions and normalization outputs for stable interchange.
Status: Draft
Transport envelopes, framing assumptions, and interchange-safe packaging concerns.
Status: Draft
Integrity envelope structure and representation rules for signed or hashed payload metadata.
Status: normative v1 appendix
Rationale behind clone vs pointer reference semantics and determinism constraints.
Status: Draft
Core Appendices
Informative parser-context flow cards for AEON Core v1 keys, attributes, types, values, containers, references, and comments.
Status: informative companion appendix
Core Syntax
Clarifies where line breaks behave like ordinary whitespace and where compact tokens must remain contiguous.
Status: informative clarification for consolidated v1
AEOS and Profiles
Profile system architecture, authority model, and integration boundaries.
Status: Draft
Charter-level scope and governance constraints for AEOS validation behavior.
Status: decision-needed for consolidated v1
Schema profile constraints, rule application semantics, and compatibility expectations.
Status: normative authoring profile for AEOS v1 schema documents
Appendix - AEOS Pattern Profile v1
UnspecifiedPattern-oriented profile semantics and deterministic pattern evaluation guidance.
Status: implementation-ahead appendix for consolidated v1
Governance model and operational constraints for tonic processor behavior.
Status: informative appendix for consolidated v1
Appendix - Third-Party Validator Conformance
UnspecifiedPointer to the CTS-owned validator conformance guidance for AEON-family validators.
Status: pointer to CTS-owned document
Profiles and Extensions
Informative profile appendix describing the `altopelago.core.v1` profile and its minimal form-oriented behavior.
Status: informative profile appendix for consolidated v1
Informative appendix describing the AEON-to-JSON interoperability profile and transformation expectations.
Status: Draft
Evolution
Informative v1 reservation for directive-block based capability evolution and future v2 activation.
Status: informative v1 reservation; candidate normative activation in v2 or later.