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

NK-WP-0048-T05: done; oidc-browser-relying-party 1.0 acknowledged (memo r4)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details

Browse source 
The founder accepted memo r4 in informed-decision. Its hub write-back is off
in production, so hub decision e418263e was resolved from the founder's report.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 469893@bnt-lap001
Assistant-Session: 49296f15-2171-4137-b972-2443bab95edb
This commit is contained in:
tegwick 2026-10-09 12:15:50 +02:00
parent 257c810709
commit eb8d7b2edc
3 changed files with 12 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

6
security-case-types/oidc-browser-relying-party/README.md
View file

@ -6,8 +6,10 @@ registration, the LLDAP groups that gate sign-in, and, for confidential
clients, the client secret, minted straight into OpenBao custody and readable
only by KeyCape and the consuming service.
Canon: `canon/standards/security-case-types_v0.1.md`. Status: **proposed**; it
awaits acknowledgment through informed-decision (NK-WP-0048-T05).
Canon: `canon/standards/security-case-types_v0.1.md`. Status: **acknowledged**
(2026-10-09, informed-decision memo `nk-wp-0048-t05-oidc-browser-relying-party-r4`,
hub decision `e418263e`). It becomes `implemented` once its first case, Forgejo,
is live and verified (NK-WP-0048-T06).
## Purpose

2
security-case-types/oidc-browser-relying-party/type.yaml
View file

@ -3,7 +3,7 @@ kind: SecurityCaseType
spec:
id: oidc-browser-relying-party
version: "1.0"
status: proposed
status: acknowledged
title: "Browser OIDC relying party for an internal service"
purpose: >-
Let an internal web service sign its human users in through NetKingdom

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

@ -172,10 +172,8 @@ review them in MASON-WP-0010-T01 and WARDEN-WP-0044-T01 before acknowledgment
```task
id: NK-WP-0048-T05
status: wait
status: done
depends_on: [NK-WP-0048-T04, MASON-WP-0010-T01, WARDEN-WP-0044-T01]
needs_human: true
blocking_reason: "A new SecurityCaseType is acknowledged as an informed-decision by the founder."
priority: high
state_hub_task_id: "3d987d3d-0797-538b-86e4-51185a327ae2"
```
@ -316,6 +314,12 @@ Prerequisites for T06 are now: lane `keycape-client-secret-generate`
(railiance-platform), and a founder-approved rollout of an identity-provisioner
image containing 630ebfd.
2026-10-09: done. The founder queued r4 (`pending`, `queued`), returned r3 as
superseded and accepted r4 in informed-decision. informed-decision's hub
write-back is off in production (`INFD_HUB_WRITEBACK` unset), so net-kingdom
resolved hub decision `e418263e` from the founder's report, naming memo r4 in
the rationale. The type is `acknowledged`; it becomes `implemented` with T06.
```task
id: NK-WP-0048-T06
status: wait