Reality Boundary
Public claims sorted by proof level. No roadmap language hidden inside architecture language.
Reading rule: this page defines what the public site claims today, which artifacts support those claims, and where the public boundary stops.
Public Claim Matrix
| Area | Status | Public artifact | Boundary |
|---|---|---|---|
| Three-state deterministic runtime | Implemented now | Technical Artifact | Public description covers semantics and invariants, not a full source release. |
| Policy version + evidence + replay model | Implemented now | Technical Artifact | Replay is defined publicly as a model and review path. Tenant policies and live records remain private. |
| Offline verification of exported artifacts | Demonstrated now | Verify Offline | Public guidance describes verification logic. Production packs and tenant material remain controlled. |
| Verification pipeline: mutation, fuzzing, property-based, Kani, TLA+ | Auditable now | Technical Artifact | Published counts and pipeline shape are public. Full internal CI traces are not published on the site. |
| Inner-loop microbenchmarks | Benchmarked now | Performance | Published numbers are scoped to inner-loop benchmarks and exclude deployment I/O unless stated. |
| Deployment boundary and operating modes | Publicly defined | Integration | Topology details, runbooks, and tenant-specific hardening remain private. |
| Regulatory mapping | Public summary | Compliance | This is an architectural mapping surface, not a legal opinion and not automatic compliance. |
| Operator tooling, schemas, and export operations | Not public in full | Pilot Scope | Detailed interfaces, schemas, runbooks, and tenant procedures require technical review context. |
Public Today
- The semantic model of ALLOW / DENY / INDETERMINATE.
- The platform/runtime split between OmegaOS and OmegaOS Kernel.
- The replay model based on evidence set plus policy version.
- The existence and shape of the verification pipeline.
- The deployment boundary: on-prem, operator-controlled, no remote dependency in the critical path.
Not Public Today
- Tenant-specific policy bundles and evidence schemas.
- Detailed runbooks, topology notes, and operator procedures.
- Full benchmark harnesses for every deployment profile.
- Internal CLI surfaces and environment-specific export tooling.
Future Public Scope
- A smaller public evidence pack example with replay transcript.
- A benchmark appendix with hardware, commands, and variance details.
- Sharper article-by-article framework mapping artifacts.
Challenge the right surface
Use Technical Artifact for invariants, Performance for published measurement scope, and Non-Goals for the explicit boundary.