the-custodian/docs/changes/netkingdom-target-2026-10-18/forgejo-current-token-r1/profile-decision-request.json

11 lines
1.1 KiB
JSON

{
"id": "b96ef564-c713-4a48-9ab2-849958cec681",
"workplan_id": "dfadb19b-445e-59c6-bcd6-48e87b912c52",
"title": "Require current KeyCape checks for ongoing NetKingdom-linked Forgejo access",
"description": "User selected \"Require current KeyCape checks (Recommended)\" in the explicit profile question. NetKingdom-linked Forgejo accounts must pass current KeyCape checks on each API and Git/SSH operation; the separate local break-glass account retains its existing path. This implementation profile selection is not a live rollout, new credential, package/trust/policy admission, or independent owner assent. Actual route/resource/action and native acceptance remain required in existing RAPPS16-T09/NK48-T43.",
"decision_type": "made",
"status": "resolved",
"rationale": "Browser session, API-token and SSH-key paths are distinct; callback checks alone cannot cover ongoing identity/revocation. Source work must retain those full entry-path obligations and current owner bindings.",
"decided_by": "user (conversation profile selection; no per-change runtime approval)",
"decided_at": "2026-10-18T10:09:17.766995+00:00"
}