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

Block RPF-WP-0060 on the unacknowledged 1.3 SecurityCase type (NK-WP-0048-T16).
All checks were successful
CCR intake gate / gate (push) Successful in 13s
Details
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 236506@bnt-lap001
Assistant-Session: 09087018-91e1-48c5-ab2f-acfbb62c92e4
This commit is contained in:
codex 2026-11-03 21:27:47 +01:00
parent b0b6c0cf46
commit 2fb7f951eb
2 changed files with 23 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

8
WORK-RECORDS.md
View file

@ -40,7 +40,7 @@
| workplan | RPF-WP-0057 | finished | — | workplans/RPF-WP-0057-sign-in-diagnosis-caller-proof.md |
| workplan | RPF-WP-0058 | finished | — | workplans/RPF-WP-0058-reuse-private-source-reader.md |
| workplan | RPF-WP-0059 | active | — | workplans/RPF-WP-0059-hourly-cadence-receiver-custody.md |
| workplan | RPF-WP-0060 | active | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| workplan | RPF-WP-0060 | blocked | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| workplan | RPF-WP-0061 | active | — | workplans/RPF-WP-0061-self-service-ccr-intake.md |
| workplan | RPF-WP-0062 | finished | — | workplans/RPF-WP-0062-custodian-agent-observer-identity.md |
| workplan | RPF-WP-0063 | finished | — | workplans/RPF-WP-0063-wave2-resource-right-sizing.md |
@ -192,10 +192,10 @@
| task | RPF-WP-0059-T02 | done | — | workplans/RPF-WP-0059-hourly-cadence-receiver-custody.md |
| task | RPF-WP-0059-T03 | done | — | workplans/RPF-WP-0059-hourly-cadence-receiver-custody.md |
| task | RPF-WP-0059-T04 | progress | — | workplans/RPF-WP-0059-hourly-cadence-receiver-custody.md |
| task | RPF-WP-0060-T01 | progress | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0060-T01 | wait | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0060-T02 | done | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0060-T03 | todo | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0060-T04 | todo | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0060-T03 | wait | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0060-T04 | wait | — | workplans/RPF-WP-0060-browser-case-platform-bindings.md |
| task | RPF-WP-0061-T01 | done | — | workplans/RPF-WP-0061-self-service-ccr-intake.md |
| task | RPF-WP-0061-T02 | done | — | workplans/RPF-WP-0061-self-service-ccr-intake.md |
| task | RPF-WP-0061-T03 | done | — | workplans/RPF-WP-0061-self-service-ccr-intake.md |

24
workplans/RPF-WP-0060-browser-case-platform-bindings.md
View file

@ -4,11 +4,11 @@ type: workplan
title: "Implement Platform bindings for the browser SecurityCase successor"
domain: financials
repo: railiance-platform
status: active
status: blocked
owner: codex
topic_slug: netkingdom
created: "2026-10-17"
updated: "2026-10-17"
updated: "2026-11-03"
flavor: implementation
origin: cross-repo
origin_ref: NK-WP-0048-T16
@ -29,8 +29,9 @@ acceptance, owner acknowledgment, catalog activation or policy change.
```task
id: RPF-WP-0060-T01
status: progress
status: wait
priority: high
blocking_reason: "NK-WP-0048-T16: the 1.3 type is not acknowledged and is still changing (coordinator r6 rejected; awaiting re-freeze, coordinator r7 and owner re-check; NK-WP-0048 triaged blocked 2026-10-28)."
state_hub_task_id: "afec2053-1995-506d-a112-cda1de552c1c"
```
@ -73,8 +74,9 @@ credential or live configuration changes.
```task
id: RPF-WP-0060-T03
status: todo
status: wait
priority: high
blocking_reason: "NK-WP-0048-T16: the 1.3 type is not acknowledged and is still changing (coordinator r6 rejected; awaiting re-freeze, coordinator r7 and owner re-check; NK-WP-0048 triaged blocked 2026-10-28)."
state_hub_task_id: "b5d73ec6-c593-50a9-8367-f899edec6f5f"
```
@ -92,8 +94,9 @@ required native authority and actual execution receipts.
```task
id: RPF-WP-0060-T04
status: todo
status: wait
priority: high
blocking_reason: "NK-WP-0048-T16: the 1.3 type is not acknowledged and is still changing (coordinator r6 rejected; awaiting re-freeze, coordinator r7 and owner re-check; NK-WP-0048 triaged blocked 2026-10-28)."
state_hub_task_id: "84f8b0a4-8450-5623-8608-dc277978383b"
```
@ -116,3 +119,14 @@ acceptance. No routing handoff or native action is implied by this work record.
The parent stays active until these obligations and their required owner
acceptance are proved. Source tests do not complete native acceptance or
KEY-WP-0039's negative/expiry/cleanup exercise.
2026-11-03: the founder set this plan to blocked. T01, T03 and T04 all bind to
the 1.3 SecurityCase type, which is still not acknowledged and is still
changing. NK-WP-0048-T16 waits on the 1.3 re-freeze after the F3/T12
integration (net-kingdom `2a9d946`, 2026-10-23), then coordinator review r7
and the owner re-check, and NetKingdom triaged NK-WP-0048 as blocked on
2026-10-28. Implementing mint/destruction (T03) or the delivery lane (T04)
now would likely mean rework after the re-freeze. Resume when NK-WP-0048-T16
reopens the owner re-check. At that point, also confirm whether NetKingdom's
separate `oidc-service-client` 0.1 type (NK-WP-0056-T14) changes what Platform
must bind. T02 remains done.