An address for a moment in spacetime.
The same place can hold different events. AEA explores how to describe where something happened, when it happened, and the reference frame that makes those coordinates meaningful.
Explore how it works ↓Explore the project
Read the project notes and follow the source material for more detail.
Explore the concept
An illustrative model of event context, alongside a separate public repository and browser inspector for the published record format.
The design, in more detail
Definition
A proposed event-record format combining coordinates, a declared time scale, a reference frame, and an integrity check in one inspectable record.
The problem
Coordinates and timestamps become ambiguous when systems omit the frame, units, or clock conventions behind them. A record should carry enough context for another system to interpret it.
The approach
AEA explores an explicit, portable event record. Its published AEA-STATE/1 implementation carries spatial and temporal context with a SHA-256 digest, while the surrounding research investigates how that context should be represented and exchanged.
How it works
- Declare the central body, reference frame, and time scale alongside the coordinates.
- Represent position, velocity, and orientation in the published AEA-STATE/1 record.
- Serialize a defined byte layout and compute a SHA-256 digest over its prefix.
- Use the reference CLI or browser inspector to decode a record and check its digest.
- Keep measured inputs and their provenance separate from the integrity check: a valid digest alone does not establish that an event happened.
Project notes
- Wire Standard
- AEA-STATE/1 (136 Bytes)
- Memory Model
- Zero Heap (#![no_std])
- Time Standard
- TAI Continuous Atomic Time
- Central Bodies
- NAIF 399 Earth · 301 Moon · 499 Mars
Development history & next steps
Event-address research
Explored how spatial coordinates, time, and reference frames could travel together.
AEA-STATE/1 publication
Published the reference record format, Rust implementation, C interface, test vectors, Python CLI, and browser inspector.
What comes next
Develop integration examples and invite review of the record format, test vectors, and reference-frame conventions.
Source material & related links
Follow the available source material and related sites for this project.
Zero-heap #![no_std] Rust library, C-ABI include/aea.h, and wire specification (ICD.md).
Browser verification tool executing Bowring geodesy inverse and SHA-256 seal verification via WebCrypto.
A plain-language introduction, illustrative event model, and research notes.
An introduction to the proposed format, its implementation, and its scope.
Engineering dossier, verification matrix, C-ABI state record details, and integration notes.
Topics: Spacetime · Coordinate Systems · Cryptography · Invention · Algorithms · Embedded C-ABI · Telemetry