engineering-docslisted

# Engineering docs Treat docs as durable, audited deliverables. Cite decisions, archive retired docs, use Australian English and load `engineering-writing` for substantial prose. ## Default homes Resolve project instructions and existing canonical owners first. The table is a fallback only when project-write authority includes documentation setup. In advisory mode, propose paths without creating them. | Type | Home | Convention | |---|---|---| | Stories / specs | `docs/stories/` or `docs/specs/` | `NN-slug.md`, indexed | | Architecture map | `docs/ARCHITECTURE.md` | current state; links to ADRs | | Diagrams | owning document or `docs/diagrams/` | colocate by default; separate when independently owned, reused or generated | | Runbooks | `docs/runbooks/` | numbered steps and verification | | Open-decision register | `docs/OPEN_DECISIONS.md` | one row per user/owner gate; never auto-answered | | Threat models | `docs/threat-models/` | STRIDE/LINDDUN structure | | Rolling state | `docs/STATE.md` | rules embedded in the file (`session` skill) | | Archive | `docs/archive/` | indexed by its README | ## Binding rules 1. Verify a decision ID against its log before citing it. 2. Regenerate generated files; never hand-edit them. 3. Keep numbered directories contiguous and update their index in the same change. 4. Quote and link frozen legal, compliance or gate wording; do not paraphrase. 5. **Anti-bloat**: an agent-facing doc past ~15 KB is a split/merge review signal, not a