OAKENMAILGenerated
Architecture decisions
The significant design decisions behind Oaken Mail, in the order made.
1
Decisions
An architecture decision record (ADR) captures one significant decision, why it was made, and what follows from it. Records are never rewritten; a later record supersedes an earlier one.
| # | Decision | Status | Date |
|---|---|---|---|
| 0001 | Record architecture decisions | accepted | 2026-10-20 |
| 0002 | One core daemon with thin clients | accepted (the MCP part is superseded by ADR 0004) | 2026-10-20 |
| 0003 | SQLite access: aiosqlite with a write broker and a read pool | accepted | 2026-10-20 |
| 0004 | The MCP server is part of core | accepted | 2026-10-20 |
| 0005 | The HTTP stack and how the local API defends itself | accepted | 2026-10-20 |
| 0006 | Clients live in apps/, each its own package | accepted | 2026-10-20 |
| 0007 | The web UI is a separate client; core stays headless | accepted | 2026-10-20 |