the-custodian/docs/changes/netkingdom-target-2026-10-18/keycape-current-client-r1/source-decision-request.json
codex 7c682d9c66
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Reject generated-only commits / generated-commit-guard (push) Successful in 9s
Publish shared current-token client and fresh-session inverse source evidence
2026-10-18 11:43:13 +02:00

11 lines
1.3 KiB
JSON

{
"id": "837e88ff-a896-4b47-82af-b838fc158da0",
"workplan_id": "dfadb19b-445e-59c6-bcd6-48e87b912c52",
"title": "Share issuer current-status code and keep original execution provenance separate from current authentication",
"description": "Publish one producer-owned current-token client through KeyCape CLI and a generated byte-parity-checked Go adapter. Warden fresh-session readmission retains an exact existing journal intent and original pins while independently revalidating the fresh caller before writes/callbacks. Immutable provenance never supplies current authority. Inactive status is client-scoped and needs prior independent ownership before it can support cleanup. No native issuer/profile, policy, catalog lane, credential, package or effect admission is granted.",
"decision_type": "made",
"status": "resolved",
"rationale": "Actual cross-owner composition exposed the original-session journal pin conflict. A shared producer implementation avoids app-local token registries and verifier forks. Source race/unit, fresh-process HTTPS integration, exact archive replay and controlled export drift checks support the bounded source result. Native operation/inverse/resource-path acceptance and independent owner review remain open.",
"decided_by": "codex (authorized source implementation only)",
"decided_at": "2026-10-18T09:39:19.723007+00:00"
}