Architecture decision records¶
Each ADR records one architectural decision: its context, the decision, its consequences and the alternatives considered. All ADRs use the same template.
| ADR | Title | Status | PLAN.md |
|---|---|---|---|
| 0001 | Pipelines, not agent loops | Accepted | §2.1, §3.2 |
| 0002 | Plugins return intents; the core applies them | Accepted | §2.1, §3.3 |
| 0003 | MCP as the plugin protocol | Accepted | §3.3 |
| 0004 | Git marketplace with commit-SHA pinning | Accepted | §4 |
| 0005 | The claude-cli backend and its terms |
Accepted | §3.4 |
| 0006 | SQLite as the store | Accepted | §3.1, §2.1 |
Process¶
- Copy
0000-template.mdtoNNNN-short-title.mdwith the next free number, and add a row here. - A new ADR starts as Proposed. The maintainer sets it to Accepted when merging the review.
- An accepted ADR is not rewritten. To change a decision, write a new ADR that supersedes it and set the old one to Superseded by ADR NNNN, linking the new ADR.
- Deprecated means the decision no longer applies and nothing replaces it (for example the feature was removed); the ADR is kept for history.
- The contracts in
src/horae/contracts/(exported toschemas/) are the normative form of many of these decisions. When an ADR and a contract disagree, that is a bug in one of them: fix it in the same PR or open an issue.