Technical Brief
Short technical orientation for evaluators.
Canonical Reading Order
OmegaOS is the governance platform. OmegaOS Kernel is the deterministic runtime. The references below carry the public model used in technical review.
| Topic | Primary reference | Reason |
|---|---|---|
| Definitions and invariants | Technical Artifact | Owns OmegaOS, OmegaOS Kernel, decision states, evidence, replay, and ledger terminology. |
| Deployment modes | Integration | Owns observe, shadow, enforce, fail-closed behavior, and overlay deployment. |
| Regulatory mapping | Compliance | Owns regulatory scope, control mapping, and legal boundary. |
| Engagement scope | Pilot Scope | Owns prerequisites, deliverables, success criteria, and deployment boundary. |
Evaluation Path
1. Read the public references
Start with Product, Technical Artifact, Integration, and Compliance. Those references carry the public model.
2. Run a technical review
Review architecture, threat model, and operating boundary under NDA if deeper material is needed.
3. Scope one bounded flow
Pick one authorization flow, one evidence model, and one operating perimeter.
4. Validate replay and evidence
Check that the runtime, policy version, evidence set, and exported artifacts match your audit requirements.
If a short note diverges, Technical Artifact, Integration, and Compliance take precedence.
Request a technical review
Send the target flow, evidence sources, and operating constraints.
Contact Engineering