coulomb/railiance-platform
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record WP0027 platform snapshot receipt
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: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02669-87ee-7a31-b111-edc95a16e0fa
This commit is contained in:
codex 2026-08-23 00:32:20 +02:00
parent d7dae015df
commit f87a4aa1f4
3 changed files with 82 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
workplans/RAILIANCE-WP-0024-audit-core-custody-and-recovery-coordination.md
View file

@ -231,6 +231,20 @@ waits on procedure review. Its remaining gates are the approved outage window,
fresh encrypted off-host OpenBao snapshot receipt, provider-console access,
2-of-3 Shamir quorum, and named abort operator.
**WP0027 preparation gate (2026-08-23):** under preparation-only scenario
`WARDEN-WP-0027-T02-DRILL-20260822-01`, platform-admin OIDC/MFA created a
fresh Raft snapshot, encrypted it to the established age recovery recipient,
verified a decrypt stream against the plaintext digest, and uploaded only the
ciphertext through the approved write-only off-host lane. The platform
validator accepted metadata receipt
`reviews/WARDEN-WP-0027-T02-DRILL-20260822-01-openbao-snapshot-receipt.json`
against the live cluster id and a possible applied index; automated recovery
checks remained green and no secret value was observed. Both local snapshot
files were securely deleted. The platform accepts the exact attended driver
role, but this receipt authorizes no seal, unseal, restore, reboot, or other
live execution; the final scenario still requires the independent quorum gate,
fully parameterized green preflight, and an exact human GO.
## T04 — Route the contracts and approval gates
```task