From c90d37e27fa32c2a8efb0d19e846a1f39313e29e Mon Sep 17 00:00:00 2001 From: codex Date: Tue, 3 Nov 2026 22:08:35 +0100 Subject: [PATCH] Record round 13: released audit-core receiver pin reviewed by all five owners. Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 236506@bnt-lap001 Assistant-Session: 09087018-91e1-48c5-ab2f-acfbb62c92e4 --- ...015-audit-core-custody-and-recovery-coordination.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md b/workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md index 358d800..50f1617 100644 --- a/workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md +++ b/workplans/RPF-WP-0015-audit-core-custody-and-recovery-coordination.md @@ -613,3 +613,13 @@ Follow-ups, not part of this plan: - The window could create its evidence directory, or record an early failure somewhere else. That needs a pinned-artifact change and a new owner round. + +Round 13 (contract `97e69f9d`, base `3ddef4c`), after RPF-WP-0015 closed. +AUDIT-WP-0013-T07 released receiver `sha256:304cfb83…` (audit-core `b365525`, +built from `8185893`, which contains `d46e89e`). The preflight pin follows it, +so future attended windows (T02/T03 class) start from current approvals. All +five owner reviews approve. audit-core diffed `5227fb1..8185893`: health and +readiness, the accept/duplicate path and lease/readiness behaviour are +unchanged. The scope-file `secret_policy` tightening and the independent-reader +reconciliation do not touch the reviewed procedures. The founder posts the +hash-bound receipts with the usual `approve` loop under `AUDIT_KUBECONFIG`.