Skip to content

Architecture Decision Records

Each record documents one significant decision: its context, the decision and its consequences. Records are immutable; a changed decision gets a new record that supersedes the old one.

No. Title Status
0001 Strict Clean Architecture for every module Accepted
0002 Go with the standard library for the backend Accepted
0003 SQLite via a pure-Go driver Accepted
0004 Svelte 5 SPA embedded into the binary Accepted
0005 Single-user auth with setup token and sessions Accepted
0006 Background jobs and cache-aside for integrations Accepted
0007 Own grid implementation for the dashboard Accepted
0009 Two-factor authentication with TOTP Accepted
0008 Sample data after the first setup Accepted
0010 Internationalisation without a framework Accepted
0011 Lean by default: dependency policy and resource budgets Accepted
0012 Owner and read-only guest accounts (supersedes the single-user scope of 0005) Accepted
0013 Single sign-on with OpenID Connect and trusted proxy headers Accepted
0014 Passkeys as second factor with a minimal WebAuthn implementation Accepted
0015 Raspberry Pi appliance image: native systemd service on Raspberry Pi OS Lite Proposed
0016 Cross-module read models: consumer-owned ports, adapters in the composition root Accepted
0017 Open core: MIT core, team features in ee/ under the Fair Core License Accepted, superseded in part by 0020
0018 Data ownership for several full accounts: owner and visibility per record for personal content Accepted
0019 The browser extension without a server: local gateways per feature Accepted
0020 ee/ stays proprietary, and only organisation features go there (supersedes part of 0017) Accepted
0021 Frontend of ee/ as a separate plugin package Accepted
0022 Several admins next to the owner: by hand or from single sign-on and directory groups Accepted
0023 How chat apps reach a private instance: Slack over Socket Mode, a Teams tab, the Teams command box search as an opt-in Accepted