ArchitectureAdrADR Policy

ADR Policy

ADR Policy

This is a meta-policy document, not an ADR. It defines how ADRs are managed.

Status: Accepted (via PR #145)

Lifecycle

Draft → Proposed → GO/PR → Accepted → Canonical
StageLocationRequirements
DraftAnywhere (local, artifacts)None
Proposeddocs/architecture/adr/Must have Status: Proposed header
Accepteddocs/architecture/adr/GO in GO_NO_GO.md + PR merged

Rules

  1. No canonical ADR without GO/PR — ADRs in docs/architecture/adr/ without explicit GO from Gatekeeper are considered drafts.

  2. ADR ≠ Task Spec — ADRs document decisions; task specs (INBOX/*.md) are implementation contracts.

  3. Status Header Required — Every ADR must have:

    ## Status
Proposed | Accepted | Deprecated

  4. Modifications — Accepted ADRs can only be modified via PR with Gatekeeper approval.

Naming

ADR_NNNN_short_description.md

Example: ADR_0010_forecast_node.md

Template

# ADR NNNN: Title

## Status
Proposed

## Context
Why this decision is needed.

## Decision
What was decided.

## Consequences
Trade-offs and implications.

## References
Links to related docs.