Architecture Decision Records

September 5, 2026 ยท View on GitHub

Decisions that shape architecture, workflow, or tooling are recorded here so humans and agents share the same memory. Each ADR follows 0000-template.md: context, options considered with trade-offs, decision, consequences. One page max.

Index

ADRTitleStatusDate
0001Development workflow: trunk-based, conventional commits, issues as backlogaccepted2026-07-26
0002GitHub Project board as execution view of the backlogaccepted2026-07-26
0003Same REST API in .NET, Go and C++ behind Nginxaccepted2026-07-28
0004Dual database providers with a dedicated migrations runneraccepted2026-07-28
0005Solidity contracts with a local Ganache node in the stackaccepted2026-07-28
0006Product docs and PRD workflowaccepted2026-07-28
0007Agent contribution workflow: worktrees, quality gates, e2e upkeepaccepted2026-08-18
0008PR review agent via Claude Code Actionaccepted2026-08-22
0009Flutter API client on the http packageaccepted2026-08-22
0010CodeQL analyzes only the languages a pull request changedaccepted2026-09-05
0011One validation and error contract across the .NET, Go and C++ APIsaccepted2026-09-05
0012In-browser mock API for the GitHub Pages demoaccepted2026-09-05
0013In-place overlays for reminder create, edit and deleteaccepted2026-09-05
0014Android network security config with a loopback-only cleartext allow-listaccepted2026-09-05

Process

  1. Ideas that need debate start as a GitHub Discussion (RFC).
  2. Draft the ADR as NNNN-short-title.md with status proposed, in a PR.
  3. Review and merge: status becomes accepted.
  4. Superseding: the new ADR references the old one; the old one gets status superseded by ADR-NNNN.
  5. Add every new ADR to the index table above in the same PR.