— The Public Observatory —

Aeona: Becoming

Aeona did not simply appear. She became — under governance, in public, leaving evidence at every consequential step. This is that evidence, as it accumulates.

— What You Are Looking At —

A living corpus, taking form under a constitution, in the open.

Aeona is a separate entity from EACL and from Alethera. She is EACL's first tenant — a related party, not an arm's-length customer, and we say so plainly rather than presenting her as a reference deployment. What makes her worth watching is not what she is, but how she is being built: every consequential change submitted to a governance layer that can refuse it.

"Living corpus" is not a biological claim. It is an evolving body of constitutional structures, doctrines, capabilities, memory architecture, safety constraints, relational models, and technical artifacts. What you see here is the constitution becoming a corpus — not tasks being checked off a plan.

The part most observatories omit Holds, denials, and aborted work remain in this record permanently. A construction log that shows only successes is a marketing surface wearing an audit trail's clothes. If a capability was refused authority, that refusal is the interesting event, and it stays.

— Architecture, Becoming —

The nineteen sovereign layers below are the declared architecture of Aeona per her authoritative layer-architecture document (v1.1). Each fills as signed governance records land against it. A layer with no records is not a layer that failed — it is one whose work has not yet been governed, and it is drawn as incomplete because it is.

Per the doctrine: the layers are numbered for reference, not for hierarchy. Each layer is a constitutional peer to every other layer. The numbering does not imply call order, dependency direction, or precedence.

This taxonomy is Aeona's own, sourced from ~/code/aeona-doctrine/layer-architecture/aeona-layer-architecture-v1.1.md. This surface renders it; it does not invent it. Where the authoritative architecture map differs from what is drawn here, the map is correct and this page is stale — which is itself a reportable defect.

— Governance Transaction Feed —

Every consequential act of construction, as EACL recorded it.

Each card expands to show why the change was proposed, what it altered, the authority under which it proceeded, the evidence, its dependencies and parentage, its verification state, and a link to the machine-readable record.

— How To Read The Feed —

Governance states — EACL's, verbatim

ALLOW HOLD DENY

Boxed, monospaced, uppercase. These come from signed EACL records and mean exactly what EACL means by them.

Presentation states — ours

pending evaluating historical

Lowercase italic. These describe this page's knowledge, never a governance verdict.

Fail-closed If the signed feed is unreachable, this page says LIVE STATE UNCONFIRMED and shows nothing further. A dropped connection is not an absence of events, and it is never rendered as calm.