ADR catalog
Architecture Decision Records — chronological, each with Context, Decision, Consequences, Rejected alternatives, and Exit cost.
Use this when
You want to understand why a specific architectural choice landed the way it did, or you are evaluating whether bassclef makes design decisions you can defend to your reviewer.
Skip this when
You are implementing a feature and just need the API. ADRs are for the "why" — implementation detail lives on the concept pages.
The catalog
Chronological. Newest first.
- ADR-001 — Fumadocs as the docs framework for docs.bassclef.dev. Accepted 2026-07-27.
More ADRs land as they are authored. Each one carries the five-part shape: Context, Decision, Consequences, Rejected alternatives, and Exit cost.
Why the five-part shape
Michael Nygard's original ADR template covered Context / Decision / Consequences. bassclef adds two:
-
Rejected alternatives — what we considered and did not pick, and why. Prevents the "did anyone think about X?" review question by putting the answer inline.
-
Exit cost — what it would take to reverse this decision. Forces the author to think about lock-in at the moment of the decision, not months later when the cost is realized.
The composite pattern makes every ADR readable in the same shape. Reader knows exactly where to look for each concern.