Spec Docs

Each file in this folder describes what a feature is and why it exists — requirements, design intent, and constraints. Spec docs are stable: they describe the intended system, not implementation details or current bugs.

Template

# [Feature Name] — Spec

## Purpose
What this feature does and why it exists. One short paragraph.

## Behaviour
Bullet-point list of observable behaviours and rules. Be precise — these are the contract.

## Constraints
Hard limits, rate limits, data rules, or non-negotiable requirements.

## Open Questions
Unresolved design decisions or known gaps. Remove when resolved.