# Architecture — [Your Project Name]

## System Structure

*How the system is structured. Layers, services, data stores, deployment
target. Cabinet members use this to understand what they're reviewing.*

## Codebase Layout

*Key directories and files. What lives where. Which files are most
important to read.*

## Technology Stack

*Languages, frameworks, libraries, databases, infrastructure. Include
versions when they matter (e.g., Mantine v8, not just "Mantine").*

## UI Framework

*Optional — fill this in if your project has a UI framework and you've
adopted framework-quality or a tech-specific variant (e.g.,
mantine-quality).*

*Include:*
- *Framework name and version (e.g., Mantine v8, Chakra UI v3)*
- *Import conventions — does the project centralize framework imports
  through a barrel file? If so, path and convention.*
- *Framework reference docs — curated decision guides, component
  inventories, or reference files the project maintains*
- *Theme system — how theming works, what's configurable at runtime,
  which files control it*
- *App-specific conventions — framework-first rules, destructive action
  patterns, etc.*
