Receipts are the operator-facing evidence layer for Mission Contracts. They bind authority, capability, policy decision, approval evidence, redaction, cost, result, failure, recovery, and hash-chain continuity.
This shell inherits authenticated page-route posture and is not exposed as a public marketing surface.
Runner registration and connector mutation stay blocked; signed Mission approval issuing, sandbox eval summaries, cost visibility, and operator sandbox interrupts are live.
Published /api/v2/os9 fleets, runners, approvals, and mission contracts use route-level auth and explicit OpenAPI registration; broader OS9 APIs remain closed.
3 curated, 0 live.
Durable Maestro runs with persisted Agent Receipts.
Sensitive actions stopped before execution.
Receipts carrying signed approval lineage.
3 receipts, 0 integrity issues.
OS9 verifies hash continuity before presenting receipts as evidence.
4a0b8bacb3fea25e75425c3633fd2d4fb178964cef5e22c32789cbfdf121c132
e97fc1b857fca964bcb6f44d696825ee8167be1d460bfdeb5ca6b5101863c259
1 receipt proofs
Research context completed with redacted source evidence.
External send stopped until operator approval was issued.
External send completed with signed approval evidence attached.