Architecture Decision Records (ADRs)¶
Architecture Decision Records capture significant technical, structural, and architectural choices made throughout the lifecycle of Debug Dojo.
Zenith pairs automated architectural boundary enforcement using Tach with ADRs to preserve the rationale, trade-offs, and invariants behind our codebase design.
Decision Lifecycle¶
Every record follows a defined status model:
| Status | Badge | Description |
|---|---|---|
| Proposed |  |
Under maintainer and community review; not yet accepted. |
| Accepted |  |
Formally approved; actively governs codebase architecture. |
| Rejected |  |
Evaluated and declined; retained to document why an alternative was avoided. |
| Superseded |  |
Replaced by a subsequent architectural decision. |
| Deprecated |  |
No longer relevant due to structural changes. |
Architectural Decision Log¶
| Number | Title | Status | Date |
|---|---|---|---|
| ADR-0001 | Record Architecture Decisions | Accepted |
2026-01-01 |
Proposing a New ADR¶
To propose a new decision:
- Review the ADR skill for workflow instructions.
- Copy template.md to
docs/adr/000X-<kebab-case-title>.md. - Submit a pull request detailing Context, Decision Drivers, Evaluated Options, and Consequences.