Filed unassigned by the #9730 dev seat as an observation-class finding — recording only; no verdict asserted and no dispatch expected until the maintainer wants the ADR text amended (docs/adr is a governed surface, human-merge only).
The drift
docs/adr/0091-grant-lifecycle-and-recertification.md (D1, around lines 59–67) states that both sys_user_position and sys_user_permission_set gain the lifecycle columns, listing delegated_from among them. The maintainer ruling of 2026-08-18 on #9730 (ADR-0049 enforce-or-remove: REMOVE) retired delegated_from from sys_user_permission_set; the removal PR (branch claude/issue-9730-retire-delegated-from-ups) lands the code, docs (authorization.mdx) and the ADR-0087 semantic ledger entry (ups-delegated-from-column-retired) — but deliberately does not touch docs/adr/, which was outside its ruled surface.
Why a card
Prime Directive #13: a recorded decision is reversed by a new ADR or an amended status line on the old one, and AGENTS.md's corollary is that the next reader must be able to find the decision they are standing on. Today the ruling lives in #9730's comment thread and in the migration ledger; a reader of ADR-0091 D1 alone still sees the column promised on both tables. One amendment line on D1 (or a status-line note pointing at the ruling and the ledger entry) closes the gap.
Refs
Generated by Claude Code
Filed unassigned by the #9730 dev seat as an observation-class finding — recording only; no verdict asserted and no dispatch expected until the maintainer wants the ADR text amended (docs/adr is a governed surface, human-merge only).
The drift
docs/adr/0091-grant-lifecycle-and-recertification.md(D1, around lines 59–67) states that bothsys_user_positionandsys_user_permission_setgain the lifecycle columns, listingdelegated_fromamong them. The maintainer ruling of 2026-08-18 on #9730 (ADR-0049 enforce-or-remove: REMOVE) retireddelegated_fromfromsys_user_permission_set; the removal PR (branchclaude/issue-9730-retire-delegated-from-ups) lands the code, docs (authorization.mdx) and the ADR-0087 semantic ledger entry (ups-delegated-from-column-retired) — but deliberately does not touchdocs/adr/, which was outside its ruled surface.Why a card
Prime Directive #13: a recorded decision is reversed by a new ADR or an amended status line on the old one, and AGENTS.md's corollary is that the next reader must be able to find the decision they are standing on. Today the ruling lives in #9730's comment thread and in the migration ledger; a reader of ADR-0091 D1 alone still sees the column promised on both tables. One amendment line on D1 (or a status-line note pointing at the ruling and the ledger entry) closes the gap.
Refs
sys_user_permission_set.delegated_fromis declared and data-door-writable, but the runtime delegation gate structurally never reads it on this object #9730 (ruling comment, 2026-08-18) · ADR-0049 · ADR-0087 ledger entryups-delegated-from-column-retiredsys_user_positiondeclaration and all of D3's delegation semantics are untouched — this card is about one sentence of D1's declaration list, nothing behavioral.Generated by Claude Code