adrlisted

# /adr — Architecture Decision Records ADRs capture *why* a non-trivial architectural choice was made — the context, the decision, the consequences. They're short, dated, numbered, and **once accepted, immutable**. Changes happen by writing a new ADR that supersedes the old one. That history is the reader's most valuable asset: every decision shows when it was made, what was known at the time, and why a later ADR changed it. Format: Michael Nygard's, lightly extended with `Date`, `Deciders`, `Tags`, and `References`. ## Storage Default: `docs/adr/` at repo root. Files: `NNNN-kebab-case-title.md` (zero-padded to 4 digits), e.g. `0007-use-spring-modulith-instead-of-microservices.md`. Index: `docs/adr/README.md` — auto-regenerated table of all ADRs. Alternative paths can be set in the conventions overlay, `.agents/dca/conventions.md` (or `.claude/dca/conventions.md`). ## ADR template ```markdown # NNNN. Kurztitel - **Status:** Proposed | Accepted | Deprecated | Superseded by NNNN (`NNNN-...md`) - **Date:** YYYY-MM-DD - **Deciders:** Names or roles - **Tags:** bounded-context, framework, integration, persistence, security, ... ## Context Welches Problem? Welche Kräfte wirken? Constraints, Trade-offs, Annahmen. Hier *keine* Lösung — nur die Situation. ## Decision Was wurde entschieden? Aktiv und kurz formulieren: „Wir verwenden X." ## Consequences Positive, negative, neutrale Folgen. Welche Optionen schließt diese Entscheidung aus? Welche neuen Möglichkeiten entste