Process spec
This page is a navigator. The canonical spec lives in the repo and is too detailed (and too live) to mirror verbatim in the docs. Always trust the source.
Canonical: core/process.md
Sections
| Topic | Where in the spec |
|---|---|
| Reading order + conflict resolution | § Reading order |
| Dispatch + parallelism rules | § Dispatch & parallelism rules |
| Task lifecycle Phases 1–8 | § Task lifecycle |
| Automatic mode (D12) | § Automatic mode |
| Engineering principles (config vs data, test oracles) | § Engineering principles |
| Documentation style — structure over prose | § Documentation style |
| Coordination protocol | § Coordination protocol |
| Task model (TODO / direct / issue) | § Task model |
Related specs (load-on-demand)
| Spec | Load trigger |
|---|---|
core/protocols/iteration-protocol.md |
Phase 4 / 5 / 6 / 7 work > 15 min, OR doc-roles pass, OR user-given timeframe |
core/protocols/automatic-mode.md |
Task prefixed auto: or PM proposes auto |
core/protocols/doc-roles.md |
New role-owned doc landing, doc grows past threshold, cross-ref repair after split, structure dispute author vs ai-engineer (D25) |
core/protocols/cross-domain-bugs.md |
Bug spans 2+ domains |
core/protocols/cross-agent-handoff.md |
Specialist diagnoses a root cause outside their domain |
core/protocols/post-task-check-in.md |
After every completed user request |
core/protocols/github-integration.md |
PM ops on GitHub issues / discussions |
core/protocols/delivery-modes.md |
PM resolving delivery mode pre-Phase-4 |
core/protocols/index-protocol.md |
Discovery / staleness check / re-extraction |