How the Layers Connect
The layers are joined by explicit interfaces and two directions of flow — telemetry rising and authority descending — never by hidden shortcuts.
Two flows, many interfaces
The stack is held together by two opposing flows. Telemetry rises from L2 through L3 to the copilots and humans above; authority descends from L7 strategy down through orchestration and control to L1's actuators. Every crossing between layers is an explicit interface, and there are no diagonal shortcuts that skip a layer's checks.
The upward path
- L2 validates and normalizes 60+ channels of diagnostics into features.
- L3 turns features into predictions — equilibria, stability, anomaly scores — over the twin.
- L4 routes events and predictions; L5 copilots reason; L6 presents to operators.
- L7 aggregates plant state into ecosystem-level intent.
The downward path
- L7 sets intent; L5 turns it into engineering goals.
- L4 checks goals against rules and safety bounds.
- L3 computes a bounded actuation trajectory via MPC over the twin.
- L1 executes deterministically; L0 supplies retrained models offline.
No shortcuts
The architecture forbids a high layer from reaching past its neighbor to a low one. Strategy cannot command an actuator; a model cannot bypass safety bounds; telemetry cannot actuate. Each layer must go through the next, so that every command is validated and every observation is curated. This is the discipline that makes the stack auditable end to end.
The interfaces are specified in layer interfaces, and the descent of authority in the stepped hierarchy.