NK-WP-0048-T05: done; oidc-browser-relying-party 1.0 acknowledged (memo r4)

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

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

@@ -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
 

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

@@ -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