coulomb/email-connect
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record the empty backup-primary slots waiting for founder key versions.
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Assistant: grok
Assistant-Session: 01a11cdb-f9fe-7011-947c-936e72007e54
This commit is contained in:
tegwick 2026-10-08 23:13:17 +02:00
parent a86d92e583
commit c79d53c8e0
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
workplans/EMAIL-WP-0007-ledger-backup-recovery.md
View file

@ -127,9 +127,9 @@ monitoring stay waiting. CSOC-WP-0015-T03 is the product acceptance follow-up.
## Pair-custody preview — 2026-10-08
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:
installed and matches its source file. Version 1 of both backup-primary KV paths now exists, with both field names
set to a non-credential placeholder. The founder will enter the real pairs
as a new OpenBao UI version. The live bucket policy still allows only the
existing resource-control application under `platform-pg/*`. No real 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.