adr

Architecture Decision Records

ADRs record accepted project decisions that future contributors should not have to rediscover from pull request threads.

Use an ADR when a decision affects:

• project scope
• module boundaries
• public contracts
• storage source of truth
• security model
• compatibility policy
• adapter architecture
• operational behavior

ADRs should be short, factual, and durable. They should explain context, decision, consequences, and tradeoffs.

Naming

Use:

NNNN-short-title.md

Example:

0001-openagentsgate-is-a-policy-control-plane.md