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

NK-WP-0048-T16: wait on 1.3 re-freeze and coordinator r6 (r5 findings changed type.yaml)

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 696317@bnt-lap001
Assistant-Session: bab9e511-0915-45b3-926a-2fab552edff6
This commit is contained in:
tegwick 2026-10-23 00:08:26 +02:00
parent 35ce5776bc
commit 579d2e367e
2 changed files with 15 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
WORK-RECORDS.md
View file

@ -220,7 +220,7 @@
| task | NK-WP-0048-T13 | done | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T14 | progress | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T15 | wait | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T16 | todo | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T16 | wait | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T17 | done | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T18 | done | — | workplans/NK-WP-0048-security-case-types.md |
| task | NK-WP-0048-T19 | done | — | workplans/NK-WP-0048-security-case-types.md |

15
workplans/NK-WP-0048-security-case-types.md
View file

@ -836,9 +836,10 @@ are unchanged.
```task
id: NK-WP-0048-T16
status: todo
status: wait
depends_on: [NK-WP-0048-T24, NK-WP-0048-T25, NK-WP-0048-T26, NK-WP-0048-T27, NK-WP-0048-T28, NK-WP-0048-T29, NK-WP-0048-T30]
priority: high
blocking_reason: "Owner re-check of the 1.3 candidate cannot start: coordinator r5 (001a38c) left NK48-R5-F1..F3 open and their fixes changed 1.3 type.yaml (now ef02dd.., re-check froze e75fe9..). Needs re-freeze + coordinator r6 with no open findings; kernel review r2 is clean."
state_hub_task_id: "200bf500-5084-5ae7-be26-3033fe1f296e"
```
@ -927,6 +928,18 @@ its own KR1-F1/F2 admission/dispatch corrections and independent review under
WARDEN-WP-0044-T03 before any 1.3 pin. Historical r4 acceptance does not supersede
r5's findings or establish native readiness.
2026-10-23 checkpoint. The Warden kernel review r2 is clean: KR1-F1..F4 are
resolved in source. The owner re-check (Custodian `nk48-1.3-owner-review/README-recheck.md`)
can start only once coordinator r5 and the kernel review both approve with no
open findings. Coordinator r5 left NK48-R5-F1..F3 open. Their implementations
(Custodian `nk48-r5-f1..f3-*`) changed the 1.3 type: `type.yaml` at HEAD is
sha256 `ef02ddae…684f`, not the re-frozen `e75fe941…5d0a`. The
descriptor digests in the re-check table are therefore stale. Next steps: the
coordinator re-freezes the 1.3 candidate at current HEAD and runs r6. After that,
net-kingdom answers NK-1.3-C1/C2 and accepts register-client, ensure-groups and
bind-env at the new digests. T16 moves to **wait**. No pin, no admission, and
1.1 stays default.
## T17 — Build and exercise the exact offline config-checker artifact
```task