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

Link KEY-WP-0037-T03 to the in-bao custody design and approval decision

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 132360@bnt-lap001
Assistant-Session: 769b1afd-4330-4c86-96b2-e510e26db42b
This commit is contained in:
tegwick 2026-10-06 14:29:54 +02:00
parent 7d96ee4a43
commit e583988599
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
workplans/KEY-WP-0037-secrets-engine-openbao-registration-custody.md
View file

@ -90,7 +90,10 @@ Platform CCR-2026-0033 (`df24a77`, still proposed) holds the KV path
`platform/workloads/keycape/secrets-engine-openbao`, the sso-only ESO and the
attended custody script; its approval is RPF-WP-0035-T09. The live order is
custody run, then issuer Secret, env patch, this merge and a restart. Nothing
is live, and the image pin is still NK-WP-0046-T02.
is live. The founder keeps the deployed image (NK-WP-0046-T02, 2026-10-06).
Revised the same day: the value lives only in OpenBao (ops-mason MASON-WP-0009)
and has no consumer file. The custody approvals A1-A3 are decision
`2ab717e1-7881-491e-aed4-28946550c289`.
## Verify actual issuance and publish non-secret owner receipt