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

Record that the backup pair writer is installed and the keys are still absent.
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
Assistant: grok
Assistant-Session: 01a11cdb-f9fe-7011-947c-936e72007e54
This commit is contained in:
tegwick 2026-10-08 22:41:21 +02:00
parent a60a729421
commit a86d92e583
1 changed files with 7 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

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

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