engineering-docslisted

# Engineering docs Treat docs as deliverables: cite decisions, archive retired docs and load `engineering-writing` for substantial prose. Read `Repository process` first. If absent, use an unambiguous existing owner or propose paths in chat; never invent one. In `issue-tracker`, parent issues own canonical scope and stories; docs own durable intent, decisions and invariants. In `project-docs`, use its named home. Do not create a second story or status projection. Link-only files are unavailable or cross-tracker fallbacks. ## Default homes Use this table only with `setup-repo` write authority; advisory mode proposes paths without creating them. | Type | Home | Convention | |---|---|---| | Durable intent / specifications | `docs/specs/` | semantic, indexed | | Architecture map | `docs/ARCHITECTURE.md` | current state; link ADRs | | Diagrams | owning document or `docs/diagrams/` | colocate unless independently owned, reused or generated | | Runbooks | `docs/runbooks/` | numbered steps; verification | | Open-decision register | declared project-docs path | never create in issue-tracker mode | | Threat models | `docs/threat-models/` | STRIDE/LINDDUN structure | | Session or run continuity | declared owner; explicit run state | `session` handoff; autopilot state remains run-local | | 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 number