AEON
Human-readable typed notation, canonical structure, references, annotations, and conformance expectations.
Specifications
Aeonite publishes system specifications first, then the shared contract and convention layers that sit around them. Each system keeps its own version track so drafts, proposals, and published releases can move independently.
Systems
Start here when you need the formal specification surface for a specific member of the Aeonite family.
AEOS
Schema and validation system for checking AEON structures without mutating or typecasting the input stream.
NEON
Hybrid text/binary codec and container work for compact transport while preserving the same family-level separation between representation and interpretation.
&ND
AEON Native Document language for deterministic document-shaped text, with draft v1 behavior and proposal-stage v2 evolution.
Contracts
Contract-layer documentation for published profile and schema identifiers, contract artifacts, and the trusted registry model.
Conventions
Shared interpretation-layer documents covering convention structure, security envelopes, document metadata, context labels, and related informative references.
GitHub repositories
Public source repositories for the canonical specification text and the conformance test surface.
aeonite-specs
Canonical source for formal AEON-family specifications, drafts, proposals, contracts, and conventions.
aeonite-ctsConformance suites, runner contracts, coverage mapping, and verification-facing CTS material.