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`.