[adrianwebb]

Outcome

Criterion 181 is proposed for binding to the existing normal SDK campaign, exact-profile, API clean-schema and canonical-record verifiers. Every observed assignment must preserve the original simulation workday, immutable issued authority and at most one mutable workspace. The existing live inspector also gains independent graph, allocation, runtime, predecessor, frozen source, branch and context checks; broader criterion 164 remains unbound.

Work authority

• Work item / Issue: Continue strict acceptance bindings: exact remaining checklist and installed delivery sdk#408 and Complete capacity-provider and Agent acceptance — continuation of #339 #368.
• Proposal / decision: Direct human authorization of the strict capacity-provider and agent-execution acceptance implementation plan.
• Assignment / checkpoint: Integrator; criterion 181 delivery and existing live-monitor support for criterion 164.
• Actor: Codex through provider-authenticated adrianwebb.
• Human authority: adrianwebb.
• Agent / capacity provider: Codex desktop.
• Exact base ref: staging 821f0bd.
• Exact head ref: codex/agent-live-custody-408 c18df7b; tree b9586499897448d2b88fe1cd7db7f8fbe08328e5.

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Follow the existing Issue -> remote PR branch -> exact-head Actions -> ordinary staging merge/read-back -> actual installed archive custody path. Fresh complete Agent and executing Reviewer suites must precede the component scene. Hold current dependent archives. No managed scene or campaign before all separate readiness gates. Criterion 181 is held for final staging read-back; criterion 164 remains open.

Changes and commits

Retain ordinary test-first lineage: graph RED 1adb656 before 62de73a; allocation f9bdc3f before ded3da6; runtime 43cdb33 before 7240782; predecessor cfc96b7 before 8875ce6; legitimate review revision 41444bc before 79c1c37; base/context c4a5c00 before 0dc77ce; branch/scope 838679b before 36738b3; later runtime publication f52f65c before e643d94; self-consistent foreign frozen source 5dababa before 6fdbf29. Reuse the original allocation, provider-history, exact Git input and classed Decision assertions rather than duplicate policy. Preserve valid older attempts after independently verified request-changes history. Add focused cases to the existing component registry/scene. One proposed criterion binding; existing 22 normal SDK steps remain unchanged.

Verification

Supplementary local focused run: 9 files / 77 tests passed on Node 24.12.0, including original configured Kernel/handler, native Git and public SDK transport plus source-backed classed Decision/review readiness. Retains malformed/foreign/missing authority, immutable grant mutation, dual mutable systems, second writable repository, read-only writes, interruption, denial, concurrent observations and unchanged retry. These controlled upstream inputs do not claim native API admission, actual model usage, managed TreeDX outcomes or physical teardown.

Exact local command: node node_modules/vitest/vitest.mjs run --config ./vitest.config.ts followed by the nine named files retained in Issue #408 evidence. npm run typecheck, npm run check:file-lengths and npm run build:dist passed. No scene invoked locally.

Source --plan: 72 mapped / 132 uncovered / 204 selected / 260 deferred / 464 full / 22 normal SDK steps; SHA256 a39ec515d84b5b814f7f144d5e37efc472b6fab32b9d52b9896ba6a64afd6e3a. All diagnostics are uncovered criteria. Fresh native Actions 38292257960 passed on source c18df7b / tested merge b5f60e7. Complete 1,014 Agent and 200 executing Reviewer assertions passed before 762 component steps; zero failed/skipped/todo. Official archive SHA256 3b0fee16be0ed4675bc588333c7cbdd7b7718af9d8cd7fd622563d5a3d54fcdf; report c47da57cee25c7bd4cb32b86ceda3b9bb269af4365f8d5318168b8f19579673b. All 121 native source digests and 22 selected archived assets match. Actual six-owner production-only/scripts-disabled installation: 8,450 archive files matched; retained guards passed, including 13 immutable grant/workday/workspace/live-custody denials, unchanged retry and installed bytes. Source and installed strict plans are byte-identical at the digest above. These installed checks are supplementary custody proof, not a managed campaign or reusable invocation prerequisites. Final staging read-back is the remaining delivery step.

Initial native Actions 38291312300 on source 6fdbf29 failed exactly one full-suite assertion: the complete expected-binding list omitted the newly proposed criterion 181; 1,013 tests passed, one failed. The component scene did not start. Commit c18df7b retains all prior exact bindings and adds only criterion 181 with its exact selected refs. Cheap focused reproduction failed before that repair and all 11 existing binding tests then passed. The original failure is retained; replacement complete prerequisites and component proof passed on c18df7b as recorded above.

Risk and rollback

Stricter evidence checks may expose unsupported/missing public context or history. They fail closed through the existing scoped stop; preserve failed observations. No product implementation, SDK src, selection lifetime, deadlines, allowances, credentials, services, releases or deployment settings change. Recover through an ordinary reviewed revert of this delivery's commits; preserve all RED commits, failed receipts, retained worktrees and source history.

Completion summary

Criterion 181 delivered by ordinary merge 3628096. Exact tested tree, six source/archive/staging owners and source/installed/final staging plan read-back passed. Temporary installed dependencies and this delivery’s remote branch removed; all retained history and failed evidence preserved. SDK #408 now checks 181: 44/133 original177, 70/134 semantic204. Criterion 164 remains unbound for its broader expected context/base obligations. SDK readiness and managed golden remain unproven.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.

Installed proof preserves two setup failures: the retained guard referenced the renamed private verifyApprovedWorkReview helper (updated to the current verifyWorkReview, retaining all assertions), then a retained controlled fixture was missing (copied unchanged). Both original failures remain retained; no owner source or installed asset was altered to pass. All final strict guard typechecks and replays passed.

Final delivery read-back 2026-10-12 23:18:35UTC: staging tree b9586499897448d2b88fe1cd7db7f8fbe08328e5, strict plan a39ec515d84b5b814f7f144d5e37efc472b6fab32b9d52b9896ba6a64afd6e3a. Criterion164 remains open/unbound; no managed acceptance launched.