diff --git a/workplans/RPF-WP-0053-coulomb-paired-backup-admission.md b/workplans/RPF-WP-0053-coulomb-paired-backup-admission.md index 2f628e2..18d2af0 100644 --- a/workplans/RPF-WP-0053-coulomb-paired-backup-admission.md +++ b/workplans/RPF-WP-0053-coulomb-paired-backup-admission.md @@ -8,7 +8,7 @@ status: active owner: codex topic_slug: coulomb-social created: "2026-10-07" -updated: "2026-10-27" +updated: "2026-10-28" state_hub_workstream_id: "cb55e474-c7a5-5c6f-bd72-ce65f853e3e3" --- @@ -284,3 +284,25 @@ T02 remains progress for independent key/receipt/image recovery custody, capacity/lifecycle/retention. First capture/application recovery, monitored schedule and temporary app-pair copy disposition remain T03/T04. Earlier unadmitted/absent statements above are historical; no timer was enabled here. + +## Coulomb independent recovery custody approved — 2026-10-28 + +User approved the additional Coulomb-only recovery custody in decision +27bbc1ac-e275-42be-ba34-6cf16eae4e78. Consumer review packet: +coulomb-social/docs/release/recovery-custody-review-2026-10-28.md at source +17d0eb67f397e3d1f5b9b63880df5054aa263c5a. Platform-root is the proposed +attended recovery/failure owner; establish a dedicated Coulomb age identity, +separate read-only recovery caller and protected off-node/workstation kit/last +recovered point outside rolling expiry. Reconcile lifecycle/headroom and native +positive/negative proof before acceptance. The existing publisher/executor and +03:15 UTC schedule approvals persist. No sibling private identity/reader reuse, +retained-object deletion, production restore or premature timer activation. + +Current execution preflight: no SCW operator environment or standard local +operator config and no live local browser-debug session. Warden route +scaleway-bootstrap remains draft/unresolvable and explicitly has no owner-fronted +execution; do not fetch its broad bootstrap key or substitute publisher/sibling +credentials. Existing email recovery proves the isolated-project mechanism, not +a grant for Coulomb. Resource-specific grants and independent kit custody still +need native execution through an attended platform operator front door. Approval +is recorded; implementation/verification remain T02/T03/T04.