DUE DILIGENCE · TECHNICAL
Technical Due Diligence
Architecture. Benchmark methodology. Integration surface. Performance overhead. The complete technical package for Cisco, Microsoft, Google, Amazon, and every engineering team that needs to evaluate the governing law.
The Omni-Compass technical due diligence package covers five areas: architecture, benchmark methodology, integration surface, performance overhead, and the kill-switch protocol. Each area is documented to the level required for an independent engineering evaluation. All source code, benchmark harnesses, and result files are on GitHub.
Architecture — The Four Layers
The Omni-Compass governing law operates at four layers simultaneously: silicon (CPU, GPU, memory), operating system (kernel scheduler, memory manager, I/O subsystem), orchestration (Kubernetes, service mesh, autoscaler), and application (request routing, connection pooling, cache management). The governor sits above all four layers — at the supervisory layer — and enforces the admissibility envelope across all of them simultaneously. No existing product operates at this layer. The supervisory layer is above the application, above the orchestrator, above the kernel. It is the layer where the physics of the system actually lives.
The Five Operations
The governing law is implemented as five operations executed in sequence at each control cycle: (1) Observe — measure the complete system state across all four layers; (2) Classify — identify the current operating regime and the admissibility envelope for that regime; (3) Constrain — evaluate every pending transition against the admissibility envelope; (4) Actuate — commit only admissible transitions; (5) Verify — confirm convergence by evaluating the Lyapunov function and updating the system state. The cycle repeats at the control frequency, which is configurable from milliseconds to seconds depending on the workload characteristics.
Integration Surface
The Omni-Compass engine integrates with existing infrastructure through three interfaces: the Kubernetes operator interface (for orchestration-layer governance), the eBPF interface (for OS-layer governance), and the CUDA/ROCm interface (for GPU-layer governance). The engine does not require modification of existing application code. It does not require modification of existing infrastructure configuration. It operates as a supervisory layer that observes and constrains the existing system without replacing it. The integration is additive, not disruptive.
Performance Overhead
The governing engine adds overhead at the supervisory layer. The overhead is documented in the benchmark receipts. For the omni-v26 cloud runs: mean response time overhead is +2.7% (inside the noise margin). 99th-percentile response time gain is −11.0% (beyond noise — a gain, not a cost). CPU overhead at the governor process is less than 0.5% of total cluster CPU. Memory overhead at the governor process is less than 200MB per cluster. The overhead is bounded, documented, and receipted. It is not estimated. It is measured.
The Kill Switch
The Omni-Compass engine includes a kill switch: a single command that disables the governor and returns the system to its pre-governed state. The kill switch is instantaneous — the governor stops enforcing the admissibility envelope immediately. The system continues to operate without the governor. No data is lost. No configuration is changed. No infrastructure is modified. The kill switch is documented in the deployment guide and tested in the benchmark harness. There is no lock-in. The governing law is additive. Removing it leaves the system exactly as it was before.
Security Architecture
The admissibility envelope is a security boundary. An adversary who compromises a node in a governed stack cannot execute lateral movement without violating the admissibility envelope. The governor observes the deviation — the Lyapunov function increases — and rejects the transition before it is committed. The security perimeter is enforced at the supervisory layer, above the application, above the orchestrator, above the kernel. This is not a firewall. It is a stability boundary. It holds regardless of the attack vector because it operates on the physics of the system, not on the signatures of known attacks.
All benchmark data, sealed run receipts, SHA-256 fingerprints, and the complete benchmark harness are publicly available on GitHub for open evaluation and independent replication by any engineer, institution, or evaluator worldwide. No license is required to verify. A license is required to monetize or commercialize.
GitHub