ADRS

Architecture Decision Records

Tracking significant architectural decisions for the workstation platform.

---

What are ADRs?

Architecture Decision Records document the context, decision, and consequences of significant technical choices. They provide a historical record of why things are the way they are.

---

Current ADRs

ADR	Title	Status
001	Use home/ as chezmoi source state	Accepted
002	Profile-driven tooling model	Accepted
003	AI and MCP baseline in shared local paths	Accepted
004	Skills system with per-tool compatibility matrix	Accepted
005	LLM provider abstraction for dev companion runner	Accepted
006	Multi-tool portability via symlinks and thin adapters	Accepted
007	Agentic harness with three-layer architecture	Accepted

---

Format

Each ADR follows this structure:

1. Title — short descriptive name
2. Status — Proposed / Accepted / Deprecated / Superseded
3. Context — why the decision was needed
4. Decision — what was decided
5. Consequences — positive and negative outcomes

---

When to write an ADR

• Adding a new major component or tool
• Changing a fundamental architecture pattern
• Making a decision that's hard to reverse
• Choosing between significant alternatives

---

Canonical doc: docs/adrs/README.md