MGOS does not ask for blind trust. Its assurance claims are backed by a self-contained evidence layer: manifests, SHA-256 verification, replayable decision artifacts, and audited validation suites.
Tamper-evident by design. No external anchoring by default.
It does not prove the formal kernel theorems -- that belongs to the /proof boundary. It proves something different: that the delivered artifact, the replayed decisions, and the validation outputs are internally consistent, reproducible, and auditable.
Every authorization outcome is paired with a cryptographic trace.
Every artifact in the bundle is listed, described, and accounted for.
Every file hash is checked against the declared manifest.
Same input, same output, same hash in the pinned environment.
Delivered under evaluation agreement / NDA when applicable.
The delivered evidence package is designed to be self-consistent and reproducible -- not to require trust in MGOS.
Audited suites, replay outputs, acceptance gates. This is what evidence directly supports.
Full-system certification. Hardware safety case. Cross-platform bitwise identity. Upstream AI truth.
| Gate | What it checks | Status |
|---|---|---|
| A0 | Bundle integrity -- MANIFEST / SHA / VERIFY offline | PASS |
| A5 | Replay determinism -- same input, same output, same hash | PASS |
| S1 / S2 | Conflict and fault no-go behavior -- zero ALLOW on conflict | PASS |
| G96 | Load stability -- decisions stable under CPU load | PASS |
| G97 | Dirty-input handling -- deterministic return, no crashes | PASS |
Statuses refer to audited suites in the pinned evaluation environment. Gate IDs correspond to the evidence bundle report.
Standard suite for expected runtime behavior under normal operating conditions.
Longer-run stability and drift detection under sustained operation.
Fail-close behavior under malformed, adversarial, or contradictory inputs.
Zero unsafe authorization in the audited suites. Explicit fail-close coverage is tracked separately where required.
Receipts are tamper-evident. They are not externally anchored by default. Receipt verification = hash-chain + bundle integrity (MANIFEST / SHA).
Full-system certification. Evidence supports certification workflows but does not substitute for them.
Hardware fault closure. Hardware redundancy remains a deployment obligation.
Upstream AI truth verification. MGOS authorizes execution; it does not evaluate semantic truth.
Cross-platform bitwise identity. Determinism is claimed within a pinned environment only.
Evidence bundle delivered under NDA within 24h. Offline-verifiable. MANIFEST / SHA / VERIFY.