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

Record the rollout-precondition handoff to railiance-platform

Browse source 
Sends the issuer-pinning precondition to the deployment owner with the exact
check, the config keys to pin and the error_type to watch for, and confirms by
inspection that the two approval clients are still unprovisioned.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NV9oijZukGyGbRQGGKnK4P

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 713576@bnt-lap001
Assistant-Session: 384c511d-9bce-4cb8-a676-2aef6c0c8df6
This commit is contained in:
tegwick 2026-09-08 14:02:37 +02:00
parent 044830da79
commit 54b7687903
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
workplans/KEY-WP-0027-rollout-readiness-and-live-state.md
View file

@ -113,5 +113,9 @@ state_hub_task_id: "7ba84b61-0458-5820-8ded-c6f59d820303"
G10's status now names the live state, the outstanding requests with their
receipt ids, and the issuer precondition that must be checked before main is
deployed. G10 stays open: nothing here admits custody, registers the human
deployed. The precondition was also sent to railiance-platform as the deployment
owner (message c8b1ad10), with the exact `curl` to settle it, the config keys to
pin, and the `error_type` to look for if it bites — plus a note that the two
approval clients remain unprovisioned, confirmed by inspection rather than
asserted. G10 stays open: nothing here admits custody, registers the human
callback, or reconciles the OpenBao-token boundary, and no repo-local change can.