Skip to content

Latest commit

 

History

History
23 lines (18 loc) · 955 Bytes

File metadata and controls

23 lines (18 loc) · 955 Bytes

Architecture decision records

ADRs preserve context for decisions that affect several modules. A change that invalidates a decision creates a new ADR and marks the previous one superseded.

ADR Status Decision
0001 Accepted The vault is primary
0002 Accepted Optional local model daemon
0003 Accepted One YAML example aligned with the schema
0004 Accepted Numeric benchmarks require a manifest

When to create an ADR

  • trust-boundary changes;
  • new storage or persistent formats;
  • MCP compatibility changes;
  • central dependency decisions;
  • migration or concurrency strategy;
  • performance or privacy policy.

An ADR contains context, decision, consequences, and considered alternatives. Transient implementation detail belongs near the code.