Architecture decision records¶
Each record captures one decision: the context that forced it, the options considered, and the consequences we accepted. Records are immutable once accepted; a changed decision gets a new record that amends or supersedes the old one. Proposals that precede decisions live in ../rfcs/.
| ADR | Title | Status |
|---|---|---|
| 0001 | Docker Compose first, with profiles | Accepted |
| 0002 | Local Supabase, through its CLI | Accepted |
| 0003 | The observability and gateway services | Accepted |
| 0004 | The application template | Accepted |
| 0005 | Ports and adapters for the stack | Accepted |
| 0006 | Networks and published ports | Accepted |
| 0007 | How telemetry reaches the backends | Accepted |
| 0008 | Langfuse and its services | Accepted |
| 0009 | Local Supabase as the database adapter | Accepted |
| 0010 | The LLM gateway | Accepted |
| 0011 | The application template, in detail | Accepted; partly superseded by 0013 and 0015 |
| 0012 | The documentation site, and publishing it from main | Accepted; amended by 0014 |
| 0013 | How the template pins the libraries | Accepted |
| 0014 | One docs build | Accepted |
| 0015 | Telemetry, mirrors, shutdown and namespaces in the template | Accepted |
To add a record, copy template.md to the next number and add a row above.