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

Consolidate platform workplans and assess intent gaps

Browse source 
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a06ecb-456a-71c2-b41e-0755d336e883
This commit is contained in:
codex 2026-09-05 11:14:42 +02:00
parent 9d958f8e09
commit 9f83e426c7
40 changed files with 2985 additions and 295 deletions
Download patch file Download diff file Expand all files Collapse all files

41
workplans/RPF-WP-0027-keycape-live-secret-exposure-recovery.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Coordinate KeyCape live Secret exposure recovery"
domain: financials
repo: railiance-platform
status: active
status: blocked
owner: codex
topic_slug: railiance
created: "2026-08-23"
updated: "2026-08-23"
updated: "2026-09-05"
related:
- KEY-WP-0011
origin: routed
@ -56,7 +56,7 @@ predecessor revocation, and sanitized evidence.
```task
id: RPF-WP-0027-T03
status: progress
status: wait
priority: high
state_hub_task_id: "714ae011-903d-55e2-ac47-801b8ef879d1"
```
@ -96,7 +96,7 @@ lane remains unresolved and no credential fetch or retry is authorized.
```task
id: RPF-WP-0027-T04
status: wait
status: done
priority: high
state_hub_task_id: "28b31e57-7a76-5100-8a61-9aa87339c5d7"
```
@ -123,7 +123,7 @@ status, timestamps, and cleanup receipts.
```task
id: RPF-WP-0027-T06
status: progress
status: wait
priority: high
state_hub_task_id: "3b9748c4-2906-5ba7-9d34-0a7067a59283"
```
@ -135,3 +135,34 @@ attended handoff identifier. Do not infer or invent any of these values. After
publication, update `docs/net-kingdom-credential-custody-contract.md`, ask
ops-warden to refresh lane resolvability, and pass only protected inputs to
NetKingdom's minimal resolver reconciliation flow.
## Portfolio review — 2026-09-05
INTENT binding: secure custody and incident closure. The goal above is historical;
the remaining platform scope is custody and acceptance of owner evidence.
**T04 is complete by existing owner evidence, not by a new action here.**
`key-cape/workplans/KEY-WP-0011-live-secret-exposure-recovery.md` T02/T03 and
`net-kingdom/workplans/NK-WP-0033-keycape-secret-exposure-rotation.md` T04
record the approved 2026-08-23 bundle replacement. Do not repeat that rotation
merely because this platform task previously remained `wait`.
The 2026-08-27 NK-WP-0033-T05 update is newer than the earlier notes above:
the resolver binding was reconciled, but there is no complete green receipt.
The predecessor value is unavailable; manual observations are not a recorded
negative proof. No one should recover or fabricate a predecessor just to make
a test pass. The incident owner must rule explicitly on the residual evidence
and acceptable disposition. Overall incident closure remains open.
- T03 waits for current NetKingdom/provider evidence disposition and the exact
platform custody acknowledgements; old procedure acknowledgements exist.
- T05 waits for the repaired owner command's sanitized receipt and the
incident owner's explicit disposition of the unavailable predecessor.
NetKingdom owns resolver/MFA execution (NK-WP-0033-T03/T05); this repo accepts
custody-related results without taking over the identity provider.
- T06 waits for confirmed mount/path/fields, writer/reader authority and the
operator handoff. The existing draft leaves those facts intentionally blank.
No new owner acceptance or coordination message is asserted by this review.
Keep this incident separate from the new-lane queue; broad lane approval cannot
close an exposure.