| Document | What it covers |
|---|---|
| Architecture | Layers, data flow, component map, folder layout |
| Data model | Domain types, state machines, class pack registry |
| Export contract | Zip structure, NDJSON schema, YOLO txt, Label Studio |
| ADR 001 | Why v1 is detect-only |
| ADR 002 | Why NDJSON is the canonical format |
| ADR 003 | Why UI state lives in meta/project.json |
| ADR 004 | Why IndexedDB, no backend |
| ADR 005 | Why src/ wraps domain + UI |
| ADR 006 | Label Studio import/export strategy |
All architecture decisions that affect the public contract or repo structure need an ADR before merging. New tasks beyond detect (segment, pose, OBB) need their own ADR when the time comes.