I0013 — Document the semantics and the dogfooding rule
Write the human documentation that explains why the model exists and what its terms mean, and leave every current fact to be generated.
DONE wave 5 · p1 · implementation profile · parallel safe
Part of M000 — Milestone and DAG driven development.
Objective
Write the human documentation that explains why the model exists and what its terms mean, and leave every current fact to be generated.
Why
Documentation that states current state goes stale. Documentation that states semantics does not. The split has to be deliberate or the first roadmap paragraph rots.
Current state
docs explained the task lifecycle and the doctrine chain, and nothing explained the plan.
Desired state
docs/PLANNING.md explains the model and docs/DOGFOODING.md states the rule that Majordomus cannot recommend a discipline it does not use.
Scope
- docs
Out of scope
- Any count, progress figure or status written in prose
Dependencies
What waits on this
Acceptance criteria
- The documents explain semantics and contain no current-state figures
- Every command they name exists and answers --help
- Both appear on the website through the existing docs pipeline
Validation
- scripts/generate-site-data --check
- bash test/run.sh
Evidence required
- docs_build
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| docs_build | build | scripts/generate-site-data --check | site data: in sync (bb6614bc9be5); docs/PLANNING.md and docs/DOGFOODING.md indexed and rendered | 2dd5915 |
Risk
Low
Timeline
- started
- 2026-09-04T03:13:12Z
- verified
- 2026-09-04T03:16:44Z
- completed
- 2026-09-04T03:16:45Z
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I0013.yaml. Read it back with majordomus plan show I0013.