Orion

The control plane owns typed mutations, IDs, protocol versions, canonical revisions, persisted snapshots, and observations. A successful network response records accepted intent; the runtime still has to compare desired and observed state, plan concrete work, and report whether the node converged.

IPC and HTTP can serve local or remote control, while TCP and QUIC serve data-plane exchange. Transport adapters own listeners, codecs, TLS, and connection behavior at the edge. Authorization, desired state, revision semantics, and provider execution remain common regardless of how a request arrived.

Persistence stores desired revisions and operational records; the reconcile layer compares them with observations and produces a plan; providers and executors perform target-specific actions. This lets alternative providers and storage choices change without teaching transport handlers how to manage workloads.

The node daemon composes authentication, transports, persistence, reconcile work, metrics, and lifecycle behavior. Health and readiness remain distinct, audit records attach to accepted mutation boundaries, structured failure classes reach clients, and release checks validate package contents rather than only a workspace checkout.