# Project Context

## What we are building

_Fill in: one paragraph describing the product — what it does, who it is for, and what problem it solves._

## Tech stack

- _Fill in: primary language and runtime (e.g. Rust 1.78, Node 20, Python 3.12)_
- _Fill in: key libraries and frameworks (e.g. axum, React, SQLAlchemy)_
- _Fill in: database(s) and storage (e.g. PostgreSQL 16, S3)_
- _Fill in: build and packaging tools (e.g. Cargo workspaces, pnpm, Docker)_
- _Fill in: CI/CD platform (e.g. GitHub Actions, CircleCI)_

## Repo structure

```
_Fill in: top-level directory tree with a one-line description per entry, e.g.:_
src/          Application source
tests/        Integration test suite
docs/         User-facing documentation
```

## Module responsibilities

_Fill in: for each crate, package, or major directory, one paragraph explaining what it owns — its public API, the invariants it enforces, and what it explicitly does NOT do._

## Key technical decisions

- _Fill in: non-obvious architectural choice and its rationale (e.g. "We use event sourcing for X because Y")_
- _Fill in: trade-off accepted and why (e.g. "We prefer X over Y for Z reason")_
- _Fill in: constraints that shaped the design (e.g. "Must support offline use, so all data is local-first")_
