From c2cb04ce94a61c804c3317cb0456a68eaaca0c2a Mon Sep 17 00:00:00 2001 From: tegwick Date: Thu, 8 Oct 2026 23:09:51 +0200 Subject: [PATCH] NK-WP-0048-T05: record the prepared memo and the attended enqueue step Co-Authored-By: Claude Opus 5.5 Assistant: claude-code Assistant-Model: opus Assistant-Process: 5457@bnt-lap001 Assistant-Session: 792bf84a-3783-4f5d-a811-cded61dd2012 --- workplans/NK-WP-0048-security-case-types.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/workplans/NK-WP-0048-security-case-types.md b/workplans/NK-WP-0048-security-case-types.md index fd0eaa3..acaac83 100644 --- a/workplans/NK-WP-0048-security-case-types.md +++ b/workplans/NK-WP-0048-security-case-types.md @@ -186,6 +186,21 @@ Prepare the Decision Memo from the type's README and `type.yaml` and submit it through informed-decision's production intake. On acknowledgment the type moves to `acknowledged`. +2026-10-08: Decision Memo prepared. Hub decision `e418263e-a71f-4f01-a970-c87c9e187c09`. +`security-case-types/oidc-browser-relying-party/decision/`: `packet.md` (question, +one act, what acknowledging does not do, the shape, alternatives, attended +steps, limits, evidence), `build_intake.py` and the built `intake.json` (memo +class `decision-record`, review group `net-kingdom-admins`, resolves the hub +decision on answer). The envelope passes informed-decision's own +`validate_submission`. Queuing it is an attended operator step, a write inside +the production dispatcher pod: + + kubectl -n state-hub exec -i deploy/state-hub-memo-dispatch -- \ + python -m api.services.memo_dispatch --queue /data/private enqueue --envelope /dev/stdin \ + < security-case-types/oidc-browser-relying-party/decision/intake.json + +The answer then appears for review in informed-decision. + ```task id: NK-WP-0048-T06 status: wait