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

RPF-WP-0064-T07/T08: original OpenBao restored in isolation and verified; evidence handed off
All checks were successful
CCR intake gate / gate (push) Successful in 1m11s
Details
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4384@bnt-lap001
Assistant-Session: 80d1f3da-7a91-4519-9737-9ba128b4da64
This commit is contained in:
codex 2026-10-24 11:41:45 +02:00
parent 7084b57d57
commit bab4f2ca6a
2 changed files with 17 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

19
workplans/RPF-WP-0064-isolated-original-openbao-restore.md
View file

@ -369,11 +369,10 @@ rather than repair. rapp-openbao was informed and may object; no rapp-openbao ch
```task
id: RPF-WP-0064-T07
status: wait
status: done
priority: high
needs_human: true
depends_on: [RPF-WP-0064-T05, RPF-WP-0064-T06]
blocking_reason: "Requires the founder in attendance holding the offline railiance-backup.key, 2 of 3 original Shamir shares and the encrypted snapshot from railiance-backups/openbao/, inside the T05-signed window. No agent handles custody material."
state_hub_task_id: "96e88167-c484-527c-84aa-0464dd0f5597"
```
@ -402,6 +401,19 @@ source now carries production's file audit device, and a native regression case
reseal (`leader_not_elected`, `sealed: true`), while the full restore passes with it. Offline 19 and native 13 pass.
A `-03` admission is needed for the new adapter commit.
2026-10-24 attempt `-03` (admission `3ef17fd1…4cc9`, adapter `7084b57`, founder attended): **`restored`,
`all_required_objects_match`** in 46 s. Independently verified from a clean clone at `7084b57`: receipt
`sha256:4e048deedda21aa35ea4ff811e437f9c0e546fbefe4eb8a2025a74bf65e2579d`, retained outside Git on the founder
workstation (mode 0400). Original cluster id `fd28df5d…` matched, applied index 6040604 (not behind 6040594),
leader elected in 2 s, the throwaway init was invalidated, the original shares unsealed, and all nine required
objects were present and equal to the committed sources: auth mounts, secrets mounts, `keycape-services` JWT
config and role `secrets-engine-openbao`, `netkingdom` OIDC config and role `platform-admin`, policy
`secrets-engine-login-self`, and KV metadata `platform/workloads/keycape/secrets-engine-openbao` (no KV data read).
The readback credential was revoked; networkless (`lo` only), no volumes, full teardown. Claims not made: consumer
continuity, live JWT login, phase B network, owner acceptance, recurring restore assurance.
T08 handoff: recorded in secrets-engine SECRETS-WP-0015-T04 and net-kingdom NK-WP-0049-T18 the same day.
RPF-WP-0036-T03 may point to this receipt as a one-off; it is not recurring assurance.
Run the admitted adapter once. The outcome is a T03 receipt verified
independently. The receipt is kept outside Git and referenced by its hash. A
missing object or failed check is a valid `refused` outcome; it is not repaired
@ -411,10 +423,9 @@ in this attempt.
```task
id: RPF-WP-0064-T08
status: wait
status: done
priority: medium
depends_on: [RPF-WP-0064-T07]
blocking_reason: "Needs the verified T07 receipt."
state_hub_task_id: "94139cb1-037a-58ef-883c-dde71fe6bfde"
```