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

CUST-WP-0075-T03: route human gates to hub decisions

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 3775@bnt-lap001
Assistant-Session: cfacb6a5-ad5b-4f79-ac67-053e3b0d34a3
This commit is contained in:
codex 2026-10-03 03:33:11 +02:00
parent 57f0b8ba56
commit df5e72648c
1 changed files with 4 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

5
workplans/RMASTER-WP-0020-openbao-migration-to-reef-railiance.md
View file

@ -9,7 +9,7 @@ flavor: implementation
owner: codex
topic_slug: railiance
created: "2026-07-30"
updated: "2026-08-23"
updated: "2026-10-03"
depends_on:
- NK-WP-0022
related:
@ -244,6 +244,7 @@ post-retirement public probe returned HTTP 200 from railiance01 with valid TLS.
id: RMASTER-WP-0020-T08
status: wait
needs_human: true
decision_id: 5d8dcdb5-6d7b-463e-bb39-0a4737331403
blocking_reason: "Retention expiry, a successful railiance01 DR drill and new explicit approval for destructive deletion."
priority: medium
state_hub_task_id: "abf1b45e-2d6b-528e-8712-1575749f4657"
@ -284,6 +285,8 @@ T08 therefore remains `wait`; finishing the migration workplan is not itself
destructive-cleanup approval. The package-owner evidence request is State Hub
message `02ec17ef-14c2-4c91-9768-7e9ac8714325`.
2026-10-03: human gate routed to hub decision 5d8dcdb5-6d7b-463e-bb39-0a4737331403 (D4: Destructive cleanup after retention expiry: CoulombCore remnants, railiance-master retention, live recipient removal) by CUST-WP-0075; resolving that decision raises C-40 here.
## T09 - Retract public OpenBao listener
```task