fix: route OpenBao recovery ceremonies safely

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0290b-3241-74c3-b868-6049545af836
This commit is contained in:
tegwick 2026-08-22 20:54:45 +02:00
parent fff76ef089
commit e3b9b1620c
10 changed files with 131 additions and 4 deletions

View file

@ -37,6 +37,11 @@ Hard lockdown is not an agent command. The irreversible hold point is the
platform owner's attended seal action. All prerequisites below must be true
before that hold point; repository access alone grants no authority to cross it.
Route planning must select `openbao-shamir-recovery-ceremony` and return one
`founder_required` approval act. A result that selects `openbao-api-key`, asks
for paste-once provisioning, or offers any raw-value transport is a routing
failure and must not be executed.
## Pre-seal hold point
- An approved, bounded window names the accountable platform driver and a