Publish and pin the verified schema-v5 approval candidate

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a07ff8-19d0-7820-b4d0-1353833cb7fc
This commit is contained in:
tegwick 2026-09-10 19:35:05 +02:00
parent be1a388a84
commit c8f85c6d76
6 changed files with 172 additions and 33 deletions

View file

@ -458,6 +458,25 @@ the v4 section (additive `ALTER TABLE`, legacy entries stay `NULL` and are never
back-filled to `human`, downgrade unsupported). T03 stays `wait`: gates 1 and 2
are unchanged and nothing is deployed. 125 tests pass.
### Schema-v5 release candidate — 2026-09-10
The earlier schema drift is resolved in the published candidate, source
`be1a388a848cf59e9ff3a5420f88a70ca0a52e7e`, registry tag
`0.1.0-hfact-be1a388`, immutable digest
`sha256:251941a5cb2724b57cc32cff6b693b1ab0be695bee4f56f02d51961189c0fa49`.
Both migration and serving references now pin it. The sanctioned HIGH/CRITICAL
scan passes with zero findings. Disposable container checks prove schema v5,
v4 migration without inferred human declaration, nonhuman bind refusal,
human bind/claim/consume and restart persistence; packaged store bytes match
committed source. These checks use synthetic local identities and no network.
See `docs/evidence/2026-09-10-human-control-image.json` for the exact evidence.
T03 remains `wait`: native KeyCape requester/approver registration and audit
sender custody still precede rollout, live persistence/outbox/restore proof.
The factory requester and PEP must explicitly declare/require human_control in
T05 with SECRETS-WP-0009-T03 and INFD-WP-0001-T08. No production database was
migrated, no workload deployed and no factory/model request admitted.
## Wire outbox delivery and reconciliation
```task