ADRs
Architecture Decision Records capture choices that should stay stable across specs and implementation tasks.
Current ADRs
| ADR | Status | Summary |
|---|---|---|
| ADR-001: Use Central App State Store | Accepted | Use one canonical application state model for UI projection, command guards, and diagnostics. |
| ADR-002: File-Backed Run History Store Before Database Persistence | Proposed | Persist run history through an application abstraction backed by a configurable JSON file before introducing a database. |
| ADR-003: Use JSON Recipe Catalog Before In-App Editor | Proposed | Load recipes from a configurable folder-backed JSON catalog before building a full in-app recipe editor. |
| ADR-004: Use One Operational Maturity Slice Before Specialized Modules | Proposed | Group the remaining core operational work into one umbrella slice with medium-sized AI-friendly tasks instead of several tiny future slices. |
Writing Rule
Create a new ADR when a choice has architectural consequences across multiple slices.
Good candidates include:
- state management approach
- simulator boundary shape
- workflow orchestration model
- streaming and backpressure policy
- persistence model for summaries and diagnostics