I0006 — Generate the Mermaid DAG from the graph
Render the dependency graph as Mermaid from the same edges the engine derives, so that no diagram anywhere is drawn by hand.
DONE wave 4 · p1 · implementation profile · parallel safe
Part of M000 — Milestone and DAG driven development.
Objective
Render the dependency graph as Mermaid from the same edges the engine derives, so that no diagram anywhere is drawn by hand.
Why
A hand-drawn dependency diagram is a second source of truth that is wrong the first time an edge changes.
Current state
The site rendered Mermaid for architecture diagrams written by hand in Markdown.
Desired state
majordomus plan graph emits the DAG, and the docs, the site and the GitHub milestone body all use that output.
Scope
- lib/project.sh
Out of scope
- Layout tuning beyond what Mermaid decides
Dependencies
What waits on this
Acceptance criteria
- Every node in the diagram is an issue in the model and every edge is a dependency in the model
- Node styling reflects derived status
- Restricting to one milestone emits only that milestone's subgraph
Validation
- bash test/run.sh 42_dag_waves
Evidence required
- mermaid_test
Evidence
| covers | type | command | result | at commit |
|---|---|---|---|---|
| mermaid_test | test | bash test/run.sh 42_dag_waves | 1 passed, 0 failed | 2dd5915 |
Risk
Low
Timeline
- started
- 2026-09-04T03:12:53Z
- verified
- 2026-09-04T03:12:54Z
- completed
- 2026-09-04T03:12:55Z
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/I0006.yaml. Read it back with majordomus plan show I0006.