T-9TBQ-sdf-draws-the-module-graph-control-units-collapsed-structure
State: planning/proposed · Impact: high · Complexity: medium
The vision’s phase 1 ends with SDF drawing this repo’s module graph, so planning can happen in our
own tool. SDF already hosts the system-graph experience (@sdlc/exp-system-graph) with two sources,
structure and capabilities, and a foldable containment tree. The module graph should be a third
source, not a new page.
Proposed
Section titled “Proposed”The experience gains a modules source, bound through a ModuleGraphClient port that SDF’s plugin
fills from the dashboard route. A projection maps the module graph into the SystemGraph shape the
renderings read, the way capability-projection.ts does. Control units project as containers,
collapsed by default. Unfolding a unit shows its member code modules and their structural edges,
including edges that cross into other units. The page is read-only.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: In SDF, the system-graph page offers a Modules source that opens on this repo’s control units, collapsed.
- AC-2: Unfolding a unit shows its member modules, and a dependency that crosses into another unit is drawn to that unit.
- AC-3: The force, diagram, and table renderings work on the new source with no rendering changes.
- AC-4: A host that binds no
ModuleGraphClientdoes not offer the source. - AC-5: No mutating route or control is added, and the PR carries before and after screenshots.
Out of scope
Section titled “Out of scope”- The control-unit drill-down (T-KWJS-sdf-control-unit-drill-down-outside-view-rollups-and).
- Modules in other repos.
Dependencies
Section titled “Dependencies”Depends on
Section titled “Depends on”T-S4K4-serve-the-module-graph-to-sdf-through-the-dashboard-api