documentation-adrslisted

# Architecture Decision Records Document decisions, not just code. When someone asks "why did we do it this way?" six months from now, the answer should exist. ## Progress Checklist - [ ] Detect if this is a significant decision - [ ] Check memories for related past decisions - [ ] Capture the decision - [ ] Store to memory provider ## When to Record Not every choice is worth recording. Record when: - **New dependency** added (framework, library, service) - **Architecture pattern** chosen (monolith vs microservice, state management, data access pattern) - **Infrastructure decision** (hosting, database, caching layer, message queue) - **Security model** defined or changed (auth strategy, encryption approach) - **Significant tradeoff** made (chose speed over correctness, chose simplicity over flexibility) Don't record: - Implementation details (naming a variable, choosing a loop structure) - Obvious choices (using TypeScript in a TypeScript project) - Temporary decisions (using a workaround until the real fix ships) ## Auto-Detection Watch for these signals that a significant decision is being made: ```bash # New dependencies being added git diff --cached package.json go.mod *.csproj Directory.Packages.props # New infrastructure config git diff --cached docker-compose* Dockerfile* k8s/ terraform/ bicep/ .github/workflows/ azure-pipelines* # New auth patterns git diff --cached | grep -i "auth\|jwt\|oauth\|session\|identity" ``` ## Step 1: Check Existing Decisions B