Kill Switch
Halt the engine and return full control to the underlying system in under one second. Three activation paths. No network dependency. Cryptographic audit trail.
< 1 s
Halt time
No
Network required
Always
Audit logged
Activation Paths
Three paths. All produce the same result. The hardware signal path requires no network connectivity.
API
POST /api/v1/haltAuthenticated request. Requires operator role. Audit-logged. Returns halt receipt.
CLI
omnictl haltAvailable on any node with engine access. Requires local credentials. Audit-logged.
Hardware Signal
No networkSIGTERM / GPIO pinNo network required. Works on bare metal and in containers. Unconditional halt.
Halt Sequence
Four steps. Total time under one second. The governed system resumes autonomous control at step two.
Stop corrections
Engine immediately stops issuing correction signals to the governed system.
Notify governed system
Engine sends a handback signal through the control interface. Governed system resumes autonomous operation.
Write audit entry
Final audit log entry written: halt reason, operator identity, final Lyapunov value, timestamp.
Clean exit
Engine process exits cleanly. All file handles closed. Metrics socket released.
Post-Halt Validation
Automatic validation after every halt. Confirms the governed system is operating normally without engine corrections.
Supervisory Override
The supervisory governor is the engine's internal safety layer. It is distinct from the kill switch. The kill switch halts the engine unconditionally. The supervisory governor drives the system back inside the admissibility envelope without halting.
Supervisory governor design based on Lyapunov stability theory (Khalil, 2002). Formal proof of convergence available at /science/stability.
Platform overview
Module Registry