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¶
| 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.
Org-level index¶
This is the org-level ADR index. As of now, the only ADRs on record are MPowerUP-specific and are catalogued under the MPowerUP project, not here:
| # | 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 |
See MPowerUP (migrating) for ADR-001 and ADR-002. Org-wide ADRs (decisions spanning multiple projects) will be recorded on this page as they are made.