ops-mason/builds/case-forgejo-netkingdom-oidc/catalog-proposal.yaml
tegwick 28386d3b4c Rebuild Forgejo bundle from type 1.1; draft fluid-telegram custody descriptions
Bundle validates; ESO policy identical to applied CCR-2026-0041. Four
fluid-telegram entries drafted from the approved plan; email-connect asked
for its new path.

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

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 327203@bnt-lap001
Assistant-Session: 55028ae3-4914-4bd1-8f5c-815f3527aef0
2026-10-10 15:12:56 +02:00

33 lines
1,005 B
YAML

proposal_for: ops-warden
security_case:
case: forgejo-netkingdom-oidc
type: oidc-browser-relying-party@1.1
render_digest: sha256:af1f4f81ef313f5e086e6e3de17197d9112dd40f00b4c20b52b5ca73c7a6d18a
acceptance_record: key-cape docs/forgejo-oidc-client-request.yaml (status accepted-2026-10-08, KEY-WP-0038-T01);
type acknowledged via informed-decision memo nk-wp-0048-t05-oidc-browser-relying-party-r4, hub decision e418263e
accepted_at: '2026-10-08'
accepted_by:
- owner
- founder
entry: 'id: forgejo-keycape-client
owner_repo: key-cape
warden_executes: false
risk: high
status: active once verification passes
workload_ref: applicable, name forgejo, declaration_ref of the consumer''s published declaration or the explicit
unknown form, never inferred
path_template: platform/workloads/keycape/forgejo
field: CLIENT_SECRET
delegation: native, intended_owner key-cape
rotation: mint-secret then verification; automatable false until a run has been proven
'