Ca Adr

Status mode — read-only report

Read-only. For each ADR (or the --adr N target), report: stem, title, stored governance status, derived delivery state, date, and supersession state. Read adr-lifecycle.jsonl when present. Display stored accepted as Accepted/Planned. Draft or proposed records without an acceptance binding remain unaccepted; report no accepted binding, never promote them. Display Implemented or Verified only when every obligation in a sealed binding has the required current, input-bound evidence; otherwise name the narrow reason (unsealed, incomplete, stale, expired, or mismatched) and do not promote the ADR. Repository evidence never implies live-host, publication, support, legal, or other external truth. Find supersession by scanning forward for any later ADR whose supersedes: resolves to it.

Resolve a supersedes: value like this, and never guess:

• The value is a stem → it names that ADR. Done.
• The value is a bare number → collect every stem with that number. Exactly one → it names that ADR. More than one → ambiguous: report it as an error and resolve nothing. Zero → a dangling reference; report that too.
• none (or empty) → no predecessor.

The CI-only checker .github/scripts/check_adr_identity.py enforces this rule in the codeArbiter source repository. It is not shipped to consumer repositories; do not invent or require an installed copy. Follow the same full-stem rule there.

If a supersession candidate contradicts an accepted ADR with no clear direction, do not pick one — flag it for /conflict.

## ADR Status — YYYY-MM-DD

### Active
- ADR-NNNN-<slug> — <title> — governance: <status>; delivery: <no accepted binding | Accepted/Planned | Implemented | Verified> (<date>)

### Superseded
- ADR-NNNN-<slug> — <title> — superseded by ADR-MMMM-<slug>

### Ambiguous supersession
- ADR-NNNN-<slug> — supersedes: <value> names <N> ADRs (<stems>) — unresolved

### Unresolved CONFIRM-NN
- ADR-NNNN-<slug> — [CONFIRM-NN]: <text>

Every ADR is named by its stem, so a shared number never collapses two rows into one. An empty section is marked "None" — not omitted. MAY dispatch decision-challenger (<plugin-root>/agents/decision-challenger.md) to stress-test an ADR; optional, never forced.

Gate: every selected ADR appears with its current status and supersession state; no [CONFIRM-NN] resolved; no file modified.

Authoring mode — on-demand procedure

Only after selecting explicitly authorized authoring or a stored status transition, load <plugin-root>/routines/decision-lifecycle/references/authoring.md and follow that procedure. It owns indexing for numbering, confirmed content, marker lifetime, the shared ADR template, append-only logs and exact acceptance/delivery binding. Do not return through a command wrapper or load it again. A status report returns to its caller and never continues into this authoring path.

Hard rules

• Read-only status never modifies a file, index, marker or ledger, even to repair evidence or resolve a [CONFIRM-NN]. Surface unresolved questions and stop.
• Every authored decision is explicitly user-attributed, never an inferred disposition of a routine finding. Explicit status changes are separate authority.
• Stored accepted means Accepted/Planned, not Implemented or Verified. Delivery claims need complete, sealed, current input-bound lifecycle evidence.
• Preserve full-stem identity and forward-only supersession. Report ambiguous or dangling references; never collapse records sharing a number or repair a fork.
• Optional challenge is MAY, not another mandatory approval or authoring step.