CORE ARCHITECTURE

The resilience runtime, engineered as a loop.

Æon orchestrates seven interdependent layers into a closed cybernetic cycle. Observability intelligence is logically separated from fault execution, so deterministic protection never waits on anything slow.

MON
Layers 1–3 observe and decide. Critical path.
COM
Layers 4–5 execute and contain. Acts on MON signals.
Feedback (L6–L7) closes the loop asynchronously, negative entropy refines the next cycle.
THE COM/MON PRINCIPLE

Detection and execution, deliberately decoupled

Borrowed from avionics command-and-monitor architecture: the part that watches is never the part that acts. That separation is what lets BLOCK fire in milliseconds, independent of anything downstream.

L3 · MONITOR

Observe & decide

Gray-failure detection over live telemetry. Computes the deviation integral and fires ALERT / LIMIT against the Safety Envelope, with zero coupling to execution.


decoupled
L4 · COMMAND

Execute & contain

Controlled fault injection and the deterministic kill-switch. On a LIMIT signal, BLOCK aborts within milliseconds and drives the agent to a Safe State.

aeon-axioms · L3→L4

The enforcement point between thought and action

Operational Deterministic Axioms sit exactly on the L3→L4 boundary: every composed action, the LLM reasoning plus the tool call it would trigger over REST APIs, MCP servers or A2A, passes through them before execution. This is where COM/MON becomes concrete, and the engine ships as a standalone module that composes with content filters and role-aware guardrails rather than replacing them.

What lives in each layer

Layer Subsystem Core purpose