From a86d92e583ba2b9892a2b596eb41553a65b9c93a Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 8 Oct 2026 22:41:21 +0200 Subject: [PATCH] Record that the backup pair writer is installed and the keys are still absent. Assistant: grok Assistant-Session: 01a11cdb-f9fe-7011-947c-936e72007e54 --- workplans/EMAIL-WP-0007-ledger-backup-recovery.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/workplans/EMAIL-WP-0007-ledger-backup-recovery.md b/workplans/EMAIL-WP-0007-ledger-backup-recovery.md index e817804..d6fc119 100644 --- a/workplans/EMAIL-WP-0007-ledger-backup-recovery.md +++ b/workplans/EMAIL-WP-0007-ledger-backup-recovery.md @@ -126,9 +126,10 @@ monitoring stay waiting. CSOC-WP-0015-T03 is the product acceptance follow-up. ## Pair-custody preview — 2026-10-08 -Founder asked to start platform custody and stop before keys. railiance-platform -`scripts/application_backup_pair_custody.py` previews CCR-2026-0037: one future -CAS=0 write of both AWS fields, writer policy `backup-pair-writer` not admitted, -no OpenBao call and no Scaleway key. The delivery reader remains unable to -create the pair. T03/T04 stay wait. No receiver pause, upload, primary.env or -timer. Review: railiance-platform/docs/credential-lane-designs/application-backup-pair-custody-2026-10-08.md. +Founder admitted `backup-pair-writer` on 2026-10-08. The OpenBao policy is +installed and matches its source file. Both backup-primary KV paths are still +absent: the bootstrap key cannot create IAM applications (403), and the live +bucket policy still allows only the existing resource-control application +under `platform-pg/*`. No Scaleway key, primary.env, receiver pause, upload +or timer. T03/T04 stay wait. Review: +railiance-platform/docs/credential-lane-designs/application-backup-pair-custody-2026-10-08.md.