# SF Planning

Use this for SF planning-state changes in this repository.

## Rules

- SQLite `.sf/sf.db` is canonical when ordering, joins, validation, or status matter.
- Plans must state purpose before implementation detail.
- Promote durable human-facing artifacts into `docs/plans/`, `docs/specs/`, or `docs/adr/`.
- Runtime planning drafts stay under `.sf/` and remain gitignored unless promoted.