Decision Log
Historical record of made decisions. Prevents re-litigating past choices.
Open/pending decisions live in decision-dashboard.
Decisions
D-001: Two-vault architecture (2026-02-26)
Context: Should personal content (thoughts, health, finance) live in the same vault as technical content? Decision: Two separate vaults — Opus (technical) and Atlas/My Life Lab (personal). Reasoning: Clean separation of concerns. Technical vault stays focused on system, features, and code knowledge. Personal vault handles daily life, CRM, health, finance. Bridge via FR-025.
D-002: FR numbering stays flat (2026-02-26)
Context: Should feature requests use area prefixes (e.g., SYS-001, DAILY-001) or flat numbering?
Decision: Keep flat FR-XXX format. Use frontmatter tags for categorization.
Reasoning: Simpler, avoids debates about categories. Tags provide flexible filtering without renaming files.
D-003: Specs deferred to FR-028 (2026-02-26)
Context: Should spec-driven development specs live in the vault or the codebase? Decision: Deferred. Will decide when implementing FR-028 (Feature Request Workflow Automation). Reasoning: Not enough implementation experience yet to make the right call.
D-004: Self-improvement via proposals (2026-02-26)
Context: How should Claude suggest system improvements without disrupting workflow?
Decision: Write proposals to vault/90_inbox/proposals/<type>/. Never implement without user approval.
Reasoning: Keeps the user in control. Proposals surface in Obsidian at the user’s pace. No surprise changes.
D-005: English-only output (2026-02-26)
Context: User types in Dutch but wants consistent vault content. Decision: All output (code, vault, responses, commits, terminal) must be in English. Reasoning: Consistency. Makes the vault searchable and reusable regardless of language context.