Architecture
Physics and mathematics at the foundation. C++ engine in the middle. Every governed system on top. The stack is not a metaphor — each layer has a formal proof obligation to the layer below it.
Four-Layer Stack
Each layer has a formal proof obligation to the layer below it.
Physics & Conservation Laws
Noether's theorem guarantees that every continuous symmetry of the system produces a conserved quantity. The engine's admissibility envelope is derived from these conserved quantities — not from heuristics.
Lyapunov Stability & Convergence
The closed-circle convergence law is a Lyapunov stability result. The engine maintains a candidate function V(x) and issues corrections only when V(x) is decreasing. Convergence is guaranteed by construction.
C++ Control Engine
The engine is a statically linked C++ binary. It runs a 1 kHz control loop, reads metrics through a zero-copy interface, and issues corrections through the governed system's existing control API. No runtime dependencies.
Governed Systems
Any system with a metrics interface and a control API can be governed. The engine does not require source access, does not modify the governed system's binary, and does not sit in the data path.
Admissibility Envelope
The admissibility envelope is the set of states the engine is permitted to drive the governed system into. It is computed at deployment time from the system's Lyapunov function and the conservation laws that apply to it.
| Property | Meaning | Consequence |
|---|---|---|
| V(x) ≤ V_max | Lyapunov value within bound | Correction permitted |
| V(x) > V_max | Lyapunov value exceeds bound | Supervisory governor activates |
| ∇V(x) · f(x) < 0 | Lyapunov derivative negative | System converging — no correction needed |
| ∇V(x) · f(x) ≥ 0 | Lyapunov derivative non-negative | Correction issued to restore convergence |
Admissibility envelope derived from Lyapunov stability theory (Khalil, 2002) and Noether's theorem (Noether, 1918). Formal proof available in the Stability and Conservation science pages.
Deployment Topology
The engine runs as a sidecar process alongside the governed system. It reads metrics through a local socket and issues corrections through the governed system's existing control API.
Sidecar
Runs as a container sidecar in Kubernetes. Reads metrics from the kubelet. Issues corrections through the Kubernetes API.
Operator
Runs as a Kubernetes operator. Manages governed deployments cluster-wide. Single engine instance per cluster.
Bare Metal
Runs as a systemd service. Reads metrics from the kernel. Issues corrections through the system's existing control interface.
Next in Platform
Integration Guide