507
Pages
Deployment & operations
+20.0%
Whole-System GAIN
What you are deploying
+22.2%
K8s Throughput
Primary integration target
—
Core SHA-256
Nov 12, 2026
The Operator's Manual is the practical deployment and operations guide for The Omni-Compass. Where the Owner's Manual proves that the framework works, the Operator's Manual tells you how to deploy it, configure it, monitor it, and maintain it in production. It covers the full operational lifecycle: from first installation to day-2 operations, incident response, and upgrade procedures.
Installation
Step-by-step installation guides for bare-metal Kubernetes, cloud Kubernetes (EKS, GKE, AKS), and single-node deployments. Prerequisites, system requirements, and pre-flight checks. The installation procedure is the same for all environments — the configuration differs.
Configuration
Complete reference for governance-suite.yaml and all configuration parameters. Basin radius θ, convergence thresholds, arm routing, domain registration, and integration endpoints. Every parameter is documented with its type, default, valid range, and operational impact.
Monitoring & Alerting
Prometheus metrics exported by the governor, Grafana dashboard templates, and alert rule definitions. The convergence monitor exports basin distance, admissibility rate, and violation counts. Alert thresholds are set relative to the basin radius θ.
Day-2 Operations
Operational runbooks for common scenarios: scaling the cluster, adding a new domain, rotating the SHA-256 seal, upgrading the governor binary, and recovering from a convergence failure. Each runbook includes pre-conditions, steps, verification, and rollback.
Incident Response
Incident classification, escalation paths, and recovery procedures. Three incident levels: L1 (basin warning — distance approaching θ), L2 (admissibility degradation — rejection rate rising), L3 (convergence failure — system outside basin). Each level has a documented response procedure.
Upgrade Procedures
Zero-downtime upgrade procedure for the governor binary, the Python reference, and the governance-suite configuration. The upgrade procedure preserves the SHA-256 seal chain — every upgrade is sealed and logged. Rollback procedure documented for each upgrade type.
EXTERNAL REFERENCES