Overview of what conventions are, how they relate to core syntax, and how documents declare them.
Status: Draft guidance
AEON Conventions
Conventions define shared interpretation rules layered on top of AEON Core. They do not change core syntax, but they give cooperating systems a way to agree on document metadata, context labels, security envelopes, and related semantic handshakes.
This section includes both general guidance and draft convention definitions. Draft items are labeled explicitly in their titles.
Start here
Read the conventions overview first, then the general-purpose convention documents if you need shared metadata or context rules. Use the security documents when you need envelopes, hashing, signatures, or secure document flows.
Convention Overview
AEON Quick Mental Model
DraftHigh-level mental model of the AEON stack across structure, meaning, policy, and processing behavior.
Status: Draft guidance
General-Purpose Conventions
AEON GP Convention v1
DraftDraft general-purpose convention for shared semantic labels such as units, currency, namespaces, and separator-encoded values.
Status: Draft interoperability convention
AEON GP Document v1
DraftDraft document metadata convention for identity, authorship, lifecycle, classification, and handling hints in the AEON header.
Status: Draft document metadata convention
AEON GP Temporal v1
DraftDraft temporal convention for interpreting temporal literals with explicit timezone, timezone database version, calendar, and ambiguity metadata.
Status: Draft temporal convention
AEON Context v1
DraftDraft context-label convention for descriptive metadata such as domain, role, audience, intent, source, confidence, sensitivity, and advisory instruction comments.
Status: Draft interoperability convention
Security Conventions
Draft security-envelope convention defining placement, sections, and field structure for secure AEON documents.
Status: Draft interoperability convention
Architecture-level explanation of integrity, signatures, encryption, and the role of conventions in secure AEON documents.
Status: Draft
Walkthrough of authoring, hashing, signing, encryption, transport, verification, and decryption for secured AEON documents.
Status: Draft
Guidance on subtree hashing, tamper-evident histories, and related integrity patterns built on AEON structure.
Status: Informative guidance for implementers.
Informative Convention Appendices
Compound Unit Labels
DraftInformative note on using compound unit labels such as `m/s` and `kg/m^3` as opaque identifiers in conventions.
Status: Draft guidance
Informative reference for common unit and measurement-system labels used alongside convention attributes.
Status: Draft guidance