Skip to content

Architecture Decision Records

Decisions that shape how Linumed Base is built and that will plausibly be questioned later - recorded with context, evaluated alternatives, and the consequences accepted along the way.

The goal is not completeness. What lands here meets these criteria:

  • The decision needs explaining from the outside (someone asks "why not X?").
  • Reversing it would be expensive or have consequences for operators.
  • The reasoning isn't readable from the code.

Everything else belongs as a comment at the relevant spot, not here.

A record stays once written; the status says what happened to it. Superseded by N means a later ADR decided the same question differently. Obsolete since N means the question stopped applying - the thing it decided about is gone - which is not the same event and should not be relabelled to the other one.

No. Decision Status
0001 BridgeLink instead of Mirth Connect as the integration engine accepted (2026-08-11)
0002 English as the documentation language accepted (2026-08-14)
0003 Loopback-only access, no bundled identity provider accepted (2026-08-14)
0004 VM tests in CI via the host's libvirt socket accepted (2026-08-14)
0005 docker/ is a manual-testing reference, not a required mirror accepted (2026-08-16)
0006 The product is called Linumed Base, not Linumed OS accepted (2026-08-18)
0007 Docker Compose, not Kubernetes accepted (2026-08-20)
0008 What the v1.0 stability guarantee covers accepted (2026-08-20)
0009 jodogne/orthanc-plugins as the Orthanc image obsolete since 0011 (2026-08-21)
0010 Internal variables are a documented list, not an enforced one accepted (2026-08-21)
0011 Orthanc removed - not part of Linumed Base accepted (2026-08-23)