Frequently Asked Questions
Institutional answers to the questions evaluators ask most.
Why three states? Why not just ALLOW or DENY?
Most decision systems force a binary outcome even when evidence is insufficient. OmegaOS treats INDETERMINATE as a first-class result — the system’s honest answer when it cannot conclude. This prevents false confidence and creates a clear signal for human review. INDETERMINATE is the default state; ALLOW and DENY can only emerge through the resolution process with sufficient evidence and governance thresholds.
How does deterministic replay help regulators?
A regulator can request any historical decision and receive an exact re-execution with the same inputs, policy, and logic. The result is identical to the original — provably. This eliminates the need for log reconstruction, narrative explanations, or trust assertions. The replay itself is the evidence.
Is OmegaOS a SaaS product?
No. OmegaOS is deployed on-premise, under the operator’s full control. There is no cloud dependency, no phone-home mechanism, and no vendor access to production data. The licence is verified offline. Deployment architecture and jurisdiction remain entirely in the operator’s hands.
Can it run air-gapped?
Yes. OmegaOS is designed for air-gapped deployment. Licence verification is offline. Cryptographic proof chains are self-contained. Evidence packs can be verified without network access. Air-gapped deployment support is available as part of the Sovereign edition.
How does Shadow mode work?
In Shadow mode, OmegaOS evaluates every decision in parallel with the operator’s existing system but does not enforce outcomes. Mismatches between the operator’s PDP and OmegaOS’s evaluation are logged and analysed. This allows progressive validation before switching to Enforce mode.
What does the verifier see?
The verifier receives a signed evidence pack containing: the decision record, replay confirmation, structured explanation, proof chain (Merkle inclusion proof, content hashes, timestamps), and cryptographic signatures. Verification can be performed offline without access to the running system.
What is not exposed publicly?
Internal algorithms, implementation details, architecture topology, data schemas, and integration specifications are not publicly documented. These are available under NDA as part of a guided pilot engagement. The public surface focuses on verifiable properties and outcomes, not implementation mechanics.
What requires NDA access?
Detailed technical specifications, integration guides, deployment architectures, operator CLI documentation, and custom configuration options are available under NDA. The pilot engagement includes hands-on access to the full system in a controlled environment.
What does OmegaOS replace?
OmegaOS does not replace existing decision systems. It operates as a governance overlay that evaluates, monitors, and audits decisions made by the operator’s existing infrastructure. It adds a verifiable proof layer without requiring replacement of upstream systems.
What happens when the system cannot conclude?
The system returns INDETERMINATE — a structured, documented result indicating that evidence or governance thresholds were not met. This triggers the operator’s human review workflow. The system never forces a conclusion and never acts autonomously. Human-in-the-loop is mandatory for all final actions.
How is human review integrated?
OmegaOS produces decisions and evidence. It does not execute actions. Every outcome — ALLOW, DENY, or INDETERMINATE — is presented to the operator for review before any downstream action. The maker-checker pattern ensures no single actor can approve an irreversible decision. The system is advisory by design.