AEON v1

AEON is the human-readable typed notation at the foundation of the Aeonite family. This index is organized by implementation task: begin with the normative core, use the focused references while building, then consult the conformance and publication records.

AEOS is the related schema and validation system. Its specification and compliance documents now have a separate AEOS v1 documentation index.

Start here

Read the core specification first, then use the compliance specification to turn its requirements into an implementation checklist.

Start here for the overall AEON Core v1 model, scope, behavior modes, and the companion documents that define the rest of the specification surface.

official · normative

Conformance requirements for implementations, including required syntax support, reference legality, policy controls, and canonical rendering rules.

official · normative

Core reference

Focused references for the language surfaces most often needed while building parsers, writers, and processors.

Reference for AEON value kinds, reserved datatype names, literal families, container forms, and reference-bearing values.

official · normative

Reference for binding shape, keys, attributes, datatype clarifiers, newline rules, and structural grammar decisions in AEON Core v1.

official · normative

Conformance and publication

Verification requirements and the records that define the official v1 publication set, release process, and supersession history.

Governance policy for AEON v1 releases, changelog rules, version claims, and how conformance claims relate to released artifacts.

official · normative

Official v1 Index

Published

Index of canonical normative documentation for AEON v1.

official · informative

Shows which v1 documents are canonical for each topic and how appendices relate to the main specification set.

official · normative

Maps canonical v1 documents to the historical source material they consolidate.

official · informative

Appendices

Detailed conceptual and implementation references covering processing, addressing, bindings, nodes, canonical form, transport, profiles, and AEOS integration.

Design notes and proposals

Non-baseline material that records design reasoning or explores possible future changes.

Accepted informative design note recording the rationale and boundaries for parameterized object<T> and node<T> claims in AEON v1.

official · informative

Architectural proposal for shared deterministic value behavior across AEON, AEOS, SANSA, Tonics, and future ecosystem components.

official · informative