# Architecture overview

## Purpose
Enduring technical structure of the system. Task-level implementation detail belongs in specs and plans.

## High-level components
- <component> — <responsibility>
- <component> — <responsibility>

## Data flow
- <brief flow>

## Boundaries
- <external boundary>
- <internal boundary>

## Dependencies
- <dependency>
- <dependency>

## Out of scope for this doc
- Per-change rollout, file lists, and verification steps → `specs/<id>/plan.md`
- Product intent → `NORTHSTAR.md`, `PRD.md`
- Architectural decisions and rationale → `docs/adr/`
