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

KEY-WP-0038-T02: register Forgejo as the first KnownSecurityCase

Browse source 
No hand-built rollout; depends on net-kingdom NK-WP-0048-T06.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 5457@bnt-lap001
Assistant-Session: 792bf84a-3783-4f5d-a811-cded61dd2012
This commit is contained in:
tegwick 2026-10-08 22:17:03 +02:00
parent 9645a0604d
commit d8f3668a18
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
workplans/KEY-WP-0038-forgejo-oidc-client.md
View file

@ -92,14 +92,24 @@ in the first two.
```task
id: KEY-WP-0038-T02
status: wait
depends_on: [KEY-WP-0038-T01]
blocking_reason: "Registration follows the accepted claim contract."
depends_on: [KEY-WP-0038-T01, NK-WP-0048-T06]
blocking_reason: "Registration runs as the first KnownSecurityCase of type oidc-browser-relying-party (NK-WP-0048-T06), not as a hand-built rollout."
priority: high
state_hub_task_id: "ddcfb482-8f33-5c81-9ce8-84be8fa5dc30"
```
### T02 — Register the client and hand over its secret
**Changed 2026-10-08 (founder direction):** no case-specific helper script.
Registration is the first case of the SecurityCaseType `oidc-browser-relying-party`
(net-kingdom NK-WP-0048, canon `security-case-types_v0.1`). The parameters
accepted in T01 become the case; ops-mason materializes it (MASON-WP-0010) and
ops-warden follows through (WARDEN-WP-0044). key-cape's part is to declare
client registration as a playbook capability that the type composes, and to
review the type's composition.
The original intent below still describes what must result.
Register `forgejo` from the packet. Mint the client secret straight into custody
(proposed OpenBao path `platform/workloads/forgejo/netkingdom-oidc-client`,
custody owner railiance-platform, consumer Forgejo). Record a receipt with no