architecture / public reference

Architecture and contract boundaries

Intent → Verify → Authorize → Execute → Observe → Record; decision, enforcement and evidence are separate.

Status: design. This describes public 2ok capabilities or proposals, not executable authority.

The generic lifecycle is Intent → Verify → Authorize → Execute → Observe → Record. Each consequential request should bind actor, action, resource, artifact revision and narrowly scoped permission. Immutable proposals are not approvals; policy decisions are not enforcement; observation is not authorization.

Generic interfaces are proposed for SpecRevision, ChangeProposal, PolicyDecision, ApprovalStatement, ExecutionLease, ExecutionReceipt and TaskCheckpoint. These contracts are planned, not currently exposed as a production service. Strong claims require independently administered resource enforcement and negative replay/mismatch tests.

Updated 2026-10-25 · Public reference, not an operational service