Decisions (ADRs)¶

Hard-to-reverse or cross-cutting choices are recorded as Architecture Decision Records (ADRs). In a managed product repo, ADRs live in the /spec spine; for the plugin itself, decisions are captured in CHANGELOG.md and PRs.

When to write an ADR¶

Use /steer:adr for any hard-to-reverse or cross-cutting choice — stack, database, auth, deployment, a new pattern — or when asked to record a decision.

flowchart TD
    Q{Hard to reverse<br/>or cross-cutting?} -->|No| SKIP[No ADR needed]
    Q -->|Yes| PROPOSED[ADR: Proposed]
    PROPOSED --> REVIEW{Ratified by a human?}
    REVIEW -->|Yes| ACCEPTED[ADR: Accepted]
    REVIEW -->|Superseded later| SUPERSEDED[ADR: Superseded]

ADR status¶

New ADRs default to Proposed — the fixture suite asserts this. An ADR becomes Accepted only on an explicit human decision.

Plugin-level decisions¶

Changes to the plugin's own behavior are recorded in CHANGELOG.md under ## steer → ### [Unreleased], and the rationale lives in the PR. See Release process.