AEON Quick Mental Model
AEON is a structured data format designed for deterministic meaning, extensibility, and verifiable documents.
It separates four concerns:
| Layer | Responsibility |
|---|---|
| AEON Core | defines structure |
| Conventions | define meaning |
| Profiles | define policy |
| Processors | define behavior |
1. What AEON Actually Is
At its core, AEON is a system of deterministic assignments.
Example:
This produces a canonical structural state.
AEON focuses on how data is structured, not what the data means.
Meaning is added by conventions.
2. The Three Parts of an AEON Document
Most AEON documents follow this conceptual layout:
Example:
Header
Processing metadata.
Body
The actual structured data.
Envelope
Security closure (optional).
3. AEON Is Not Just a Data Format
Most formats stop here:
AEON goes further:
This allows AEON to support things like:
- signed documents
- structured metadata
- contextual interpretation
- verifiable datasets
without making the core language complex.
4. Conventions Add Meaning
AEON core does not interpret fields.
Instead, documents declare conventions.
Example:
The convention tells consumers how to interpret certain fields.
Example:
The unit meaning is defined by a convention, not the language.
5. Profiles Add Policy
Profiles define safe usage bundles.
Example:
Profiles may define:
- required conventions
- allowed algorithms
- processing constraints
Profiles exist so independent implementations can interoperate safely.
6. Canonicalization Matters
AEON guarantees that documents have a deterministic canonical structure.
Example:
Canonical ordering becomes:
This property enables:
- reproducible hashing
- cryptographic signatures
- deterministic processing
7. Security Is Layered
Security is not built into the syntax.
Instead AEON defines conventions:
| Convention | Purpose |
|---|---|
aeon.gp.security.v1 |
envelope structure |
aeon.gp.integrity.v1 |
canonical hashing |
aeon.gp.signature.v1 |
signatures |
aeon.gp.encryption.v1 |
encryption |
Example envelope:
This makes AEON documents self-verifying.
8. AEON Supports Advanced Integrity
Because of canonical paths and deterministic structure, AEON naturally supports:
- Merkle subtree verification
- tamper-evident event logs
- verifiable datasets
These patterns can be built without modifying the core language.
9. What AEON Is Not
AEON deliberately avoids becoming:
- a programming language
- a computation system
- a schema engine
- a policy engine
Instead AEON focuses on deterministic structured representation.
Other systems can build on top of it.
10. Simple Mental Model
If you remember only one thing:
11. Typical Processing Pipeline
12. A Small Example
This document:
- contains structured data
- declares interpretation conventions
- includes integrity protection
All without expanding the core language.
Final Summary
AEON is designed to provide:
- deterministic structured data
- extensible interpretation layers
- secure and verifiable documents
- long-term ecosystem growth
while keeping the core language minimal and stable.
If you'd like, the next thing we could do (and it’s actually useful before publishing a spec) is write the AEON “design philosophy” page — the one that explains why AEON exists and what problems it solves. That’s often what convinces people to adopt a format.