Architecture decisions

Every decision that is expensive to reverse, and the reasoning behind it. These are published rather than kept internal: a plugin author asking why the API is shaped a particular way should be able to read the answer.

Records are append-only. A reversed decision is superseded by a new record rather than edited, because the history of a decision we later changed is more useful than a tidy directory.

Decision	Status
0001 — Record architecture decisions	Accepted
0002 — Application shell: Tauri v2 over Electron and pure-Rust GUI	Accepted
0003 — Frontend framework: Svelte 5 + TypeScript	Accepted
0004 — Editor core: CodeMirror 6 with a single-buffer visual mode	Accepted
0005 — Extensibility tiers: core, core plugins, community plugins	Accepted
0006 — Plugin runtime and capability-based security	Accepted
0007 — LaTeX compilation: Tectonic by default, system TeX as a peer	Accepted
0008 — Zotero integration strategy	Accepted
0009 — Obsidian integration strategy	Accepted
0010 — Theming via CSS custom properties and user theme files	Accepted
0011 — Localisation from the first commit	Accepted
0012 — Semantic versioning and changelog automation	Accepted
0013 — Update distribution for app and plugins, and dev-mode behaviour	Accepted
0014 — Target platforms and the native ARM64 policy	Accepted
0015 — Performance budgets enforced in CI	Accepted
0016 — Self-documenting project and the docs site	Accepted
0017 — Repository layout and monorepo tooling	Accepted
0018 — Licensing: AGPL-3.0 application, MIT plugin API	Accepted
0019 — TLS trust: bundled roots or the operating system store	Accepted
0020 — Edit a multi-file document as one, behind a mode	Accepted
0021 — Plugins are their own repositories, released and updated on their own	Accepted
0022 — MCP: calling out is a capability, exposing tools is a declaration	Accepted
0023 — The preview knows LaTeX; packages are plugins	Accepted
0024 — The page is a fixed box; content is pushed through it	Accepted
0025 — A generated list is a tab, not pages	Accepted
0026 — A task list is a core tab; a credential is a capability	Accepted
0027 — Completion while typing	Accepted
0028 — The file list edits the project	Accepted
0029 — A format brings its own preview	Accepted