This log captures the significant architecture decisions behind the Demeter platform. Each ADR records the context, the decision, and its consequences, so future contributors understand why the system is shaped the way it is — not just what it does.
ADRs are immutable once accepted: to change a decision, add a new ADR that supersedes the old one (and link them) rather than editing history.
| ADR | Title | Status |
|---|---|---|
| 0001 | PostgreSQL + Drizzle for persistence (over in-memory stores) | Accepted |
| 0002 | Fastify 5 with a plugin/route-group architecture | Accepted |
| 0003 | OpenAPI-first API documentation via route schemas | Accepted |
| 0004 | JWT access + rotating refresh tokens with family reuse-detection | Accepted |
| 0005 | Injectable providers for external dependencies | Accepted |
| 0006 | Shared database with a demeter_ table namespace |
Accepted |
Format#
text
# ADR-NNNN: <title>
Status: Proposed | Accepted | Superseded by ADR-XXXX
## Context — the forces at play
## Decision — what we chose
## Consequences — what follows (good and bad)