Skip to content

[finding] ADR-0091 D1 still declares delegated_from on both grant tables after the #9730 removal ruling #9997

Description

@os-warren

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

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions