# {{PROJECT}} architecture

<!-- Living document. Update when components, data flow, invariants, or ADR outcomes change. Keep claims concrete and current. -->

## Purpose

Describe what this system exists to do, who uses it, and what success means.

## System context

List upstream callers, downstream services, data stores, queues, files, and trust boundaries.

## Components

- Component: responsibility, owner, key files.

## Data flow

1. Input source.
2. Validation and transformation.
3. Persistence or external calls.
4. Output and observability.

## Key invariants

- Invariant: why it must hold, where enforced, how verified.

## Decision log (ADRs)

<!-- Append ADR links or summaries here. Newest last. -->