Architecture Decision Records
This directory contains Architecture Decision Records (ADRs) for Sprout.
What is an ADR?
An ADR is a document that captures an important architectural decision along with its context and consequences. ADRs
help maintain a historical record of technical decisions, making it easier for contributors to understand why things are
built the way they are.
When to write an ADR
Write an ADR when you make a decision that:
- Affects the structure of the codebase
- Has long-term implications
- Was difficult to make or involved significant trade-offs
- Future developers might question or want to revisit
Examples include:
- Choosing a particular design pattern
- Deciding how to handle a cross-cutting concern
- Selecting between different implementation approaches
- Establishing coding conventions for a specific area
ADR Lifecycle
- Proposed — The decision is being considered
- Accepted — The decision has been made and is in effect
- Deprecated — The decision is no longer relevant but kept for historical context
- Superseded — The decision has been replaced by a newer ADR
Index
| ADR |
Title |
Status |
Date |
| 0000 |
Template |
— |
— |
| 0001 |
Monorepo v2 |
Accepted |
2026-02-04 |