A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I0006
Generate the Mermaid DAG from the graph
Where it stands
devtask.issueMoves
plan.transitionWhat it is
- 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.
- Now
- The site rendered Mermaid for architecture diagrams written by hand in Markdown.
- Wanted
- majordomus plan graph emits the DAG, and the docs, the site and the GitHub milestone body all use that output.
- Done when
- unknown: the record declares no `completion`
- Risk
- Low
Acceptance
- 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 present
mermaid_test
Scope
- Touches
lib/project.sh- Not
Layout tuning beyond what Mermaid decides- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- true
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-09-04
- Updated
- 2026-09-04T03:12:55Z
- Started
- 2026-09-04T03:12:53Z
- Verified
- 2026-09-04T03:12:54Z
- Completed
- 2026-09-04T03:12:55Z
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.