coulomb/ops-warden
4
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

docs: record recovery preparation boundaries
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: 01a0290b-3241-74c3-b868-6049545af836
This commit is contained in:
tegwick 2026-08-22 22:12:52 +02:00
parent 5ac47520b1
commit 7fa6985f72
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/evidence/WARDEN-WP-0027-T02-drill-scenario-2026-08-22.md
View file

@ -47,6 +47,20 @@ reported:
This baseline is not reusable as the final hold-point result. The platform This baseline is not reusable as the final hold-point result. The platform
owner must rerun it against the current state and fresh snapshot receipt. owner must rerun it against the current state and fresh snapshot receipt.
## Fail-closed preparation probes
- The OpenBao pod token helper and the current workstation caller token both
receive `403 permission denied` for a capabilities check on
`sys/storage/raft/snapshot`. No snapshot command was attempted after that
denial. The platform driver must use its attended owner identity; the agent
will not widen a workload token or substitute root.
- Warden has no autonomous provider-console catalog lane. Independent console
access therefore remains an explicit `railiance-infra` owner attestation,
not an inferred result from SSH reachability.
- The live barrier reports three shares and threshold two, but state metadata
cannot prove two custodians are currently present. Availability must arrive
through the out-of-band custody authority without identities or values.
## Pending receipts ## Pending receipts
- [ ] `railiance-platform`: fresh encrypted, verified, off-host OpenBao Raft - [ ] `railiance-platform`: fresh encrypted, verified, off-host OpenBao Raft