NK-WP-0055-T13: king-path drill passed; post-event review record
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 4515@bnt-lap001
Assistant-Session: 0bf96127-6e04-41be-bfda-d11717c3f354
This commit is contained in:
tegwick 2026-10-28 00:46:02 +01:00
parent 7e6b23d85b
commit e9928fa3d9
3 changed files with 52 additions and 1 deletions

View file

@ -326,6 +326,8 @@ root token against an isolated restored OpenBao (never production); use produces
2026-10-28: founder rolled out the loopback `generate-root` listener (RAPP-OPENBAO-WP-0003-T02): 200 on 8210 without a token, 405 on the main listener 8200. The break-glass ceremony can now run on production with SSO down. railiance-platform built and rehearsed the drill mode for part 2 (RPF-WP-0064-T10, `a2da408`: 34 offline tests, native rehearsal 16/16); its production read-only walk must be updated to expect 200 on 8210.
2026-10-28: crisis list item 5 now records the admission signing key's fingerprint and both public anchor lines, so a recovery workstation can re-create them; founder decision: the private key goes to the password safe kingpath entry, not the Storage Share bundle. Its file on the workstation is still being located.
2026-10-28 king-path drill part 2 (founder-run): RPF-WP-0064-T10 attempt `-20261027-01` `drilled` in 101 s, receipt `e4591346…8397` independently verified (PASS). Held initial root token valid as of the 2026-10-14 snapshot; fresh `generate-root` with re-entered shares, read-only action, revoke 204, lookup 403, cancel drilled, full teardown. Post-event record: [2026-10-28 king-path drill](../docs/evidence/2026-10-28-king-path-drill.md). Open: founder decision on the production root token, the read-only production SSO-down walk, the signing key copy in the safe.
## Policy import pipeline and platform/tenant package split
```task