AES v1

Scope: portable Assignment Event Stream architecture, ownership boundaries, encodings, shared semantics, and conformance publication.

AES is the shared Assignment Event Stream layer of the Aeonite ecosystem. It provides a portable event model between source-language producers and validators, query systems, processors, storage engines, relays, and other consumers.

Architecture

AES separates one transport-neutral event contract from the encodings that carry it:

Relationships: Connection from AEON and Other Producers to Portable AES Events; Connection from Portable AES Events to telex.aes Text; Connection from Portable AES Events to film.aes Binary.

Figure 1: Portable AES architecture

The event contract owns record meaning. An encoding owns only its physical framing and canonical bytes. A source language owns its grammar and the projection from source constructs into AES events.

Current documents

The v1 index, portable event contract, compatibility contract, and Telex encoding are published conformance targets. The integrity and Assignment Event Transaction contracts are normative drafts for implementation and interoperability review. The Aeonic Semantic Language remains a proposal, and Film and Tape remain planned work.

Portable AES Event Contract defines aes.events.v1, including flat records, representation kinds, paths, profiles, projections, provenance, fidelity, and semantic diagnostics.
telex.aes v1 defines the first textual encoding of that event contract.
Portable AES Integrity Contract defines encoding-neutral logical bytes, ordering and coverage policies, digests, and domain-separated signature inputs over portable records.
Assignment Event Transaction Contract defines a support-gated prepared-application envelope, exact-order transaction integrity, and the initial narrow ASP scalar replacement.
Portable AES Compatibility Contract defines explicit legacy adapters and the reader-before-writer deployment barrier.
Aeonic Semantic Language defines shared behavior over represented values after a valid AES representation exists.

Boundaries

AES is not an object tree, a source-language AST, a schema language, a query language, or a persistence engine. It does not infer datatype meaning, resolve references, or grant mutation authority.

AEON owns source syntax and source legality. AEOS owns schema validation. SANSA owns semantic addressing, resolution, query, and mutation planning. Tonics own materialization. ASP, AES-DB, ledger protocols, and hosts own persistence and history.

Fidelity

Portable AES can be semantically lossless relative to a selected event profile and projection. It does not preserve exact source spelling or layout. Exact source reconstruction requires the separately retained source artifact identified by provenance.

Planned work

film.aes is planned as a binary encoding of the same event model. Tape is reserved for later stream or history work. Neither has a normative format in v1.

Conformance

Repository-local Telex vectors remain a mutable v1 candidate. Stable shared conformance is published as aes-events-cts-v1-snapshot-0.1 for 38 transport-neutral event/profile vectors and telex-cts-v1-snapshot-0.1 for 50 encoding and format-limit vectors. Both snapshots pin suite digests and pass in the independent JavaScript and Rust implementations. Future changes require a new snapshot identifier.