Skip to content
Download

ADR 0001 — Record significant decisions

  • Status: Accepted
  • Date: 2026-10-23
  • Restructured: 2026-10-25

Requested by the repository owner during repository analysis and packaging work. The repository already has subsystem documentation, but no indexed decision history or root contribution rule requiring it. Product, integration and installer behavior has diverged from some documentation. Chat history and assistant memories are insufficient as the only record available to future contributors.

Keep engineering documentation in docs/, publish an index, maintain numbered ADRs for significant choices, and require updates through root AGENTS.md and CONTRIBUTING.md. Record context, alternatives, consequences and validation. Preserve prior rationale when superseding a record. Use existing ADRs for routine fixes.

Chat-only decisions are difficult to discover and review. An external wiki splits source and operational knowledge. A full RFC process for every correction creates unnecessary overhead.

Architecture, supported platforms, storage/schema, integrations, dependency policy, security boundaries and releases now have a durable reviewable record. Authors must keep docs consistent. These files are also read by the Astro documentation site and therefore include front matter.

  • If decision records stop being reviewed in the same pull request as the changes they describe, for example because most decisions move to a system outside the repository, revisit keeping them in docs/; an external wiki was rejected for splitting source from operational knowledge.
  • If routine corrections start needing records of their own, the overhead this record rejected for a full RFC process has returned: narrow the triggers in AGENTS.md rather than drop the record.

Review the new index/template, contribution instructions and documentation site build. This record documents the policy beginning now; it does not assert that earlier choices were formally approved under it.