Architecture Decision Records
Each ADR records one significant decision: its context, the decision, and its consequences. ADRs are immutable once accepted; a change of direction is a new ADR that supersedes the old one.
| ADR | Title | Status |
|---|---|---|
| 0001 | Electron process model and security boundaries | Accepted |
| 0002 | Toolchain and resolved versions | Accepted |
| 0003 | Packaging and update channels | Accepted |
| 0004 | Extension isolation and trust model | Accepted |
| 0005 | Test strategy | Accepted |
| 0006 | Settings schema and migrations | Accepted |
| 0007 | Git and merge strategy | Accepted |
| 0008 | Requirement conflicts and resolutions (living log) | Accepted |
| 0009 | Performance budgets | Accepted |
| 0010 | Static analysis with SonarQube Cloud | Accepted |
| 0011 | WhatsApp notifications | Accepted |
| 0012 | Translations | Accepted |
| 0013 | The in-chat assistant bar | Accepted |
| 0014 | The extension marketplace | Accepted |
| 0015 | Call recording | Accepted |
| 0016 | Extensions, not plugins | Accepted |
New ADRs copy template.md and take the next free number.