Architecture Decision Records¶
Architecture Decision Records (ADRs) document significant technical choices — what was decided, why, what alternatives were considered, and what trade-offs were accepted. They are written at decision time and kept permanently, even when superseded, so the reasoning behind the codebase remains readable.
How to read an ADR¶
Each ADR has a status:
| Status | Meaning |
|---|---|
| Proposed | Under discussion — not yet binding |
| Accepted | The current decision — in effect |
| Superseded | Replaced by a later ADR (link provided) |
| Deprecated | No longer applicable; context has changed |
ADRs are numbered sequentially and never deleted. A bad decision that was later reversed is still worth understanding.
Index¶
| # | Title | Project | Status | Date |
|---|---|---|---|---|
| 001 | Circle graph data model and database selection | MPowerUP | Accepted | 2026-04-30 |
| 002 | Cross-platform framework selection (React Native + Expo) | MPowerUP | Accepted | 2026-05-22 |