T-SX0F-control-unit-outside-view-summary-capabilities-claimed-and
State: planning/proposed · Impact: high · Complexity: large
From outside, a control unit is one node: a summary, the surfaces its members publish, the capabilities it claims, its relations, and rollups of the work inside it. Rollups follow control units, not code modules. Without them the graph is a package diagram and says nothing about the project’s state.
Proposed
Section titled “Proposed”Each control unit in the op’s output carries an outside view. The summary comes from the unit’s
product entity when it has one, else its label. Capabilities claimed reuse the
sdlc capability coverage join: a capability belongs to the unit that owns the module its location
lands on. Entity counts by kind and status come from the unit’s own planning directory. Readiness
and drift use the definitions the module-graph decision fixes. A unit nested inside another shows
both its own counts and a total that includes its children.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: A unit’s capabilities are exactly those whose locations land on its member modules.
- AC-2: Entity counts by kind and status come from the unit’s planning directory and nowhere else.
- AC-3: A parent unit’s total equals its own counts plus its children’s totals.
- AC-4: Readiness and drift appear on each unit, with the rule that produced each value named in the output.
- AC-5: A unit with an empty planning directory shows zero counts, not an error.
Out of scope
Section titled “Out of scope”- Rollups per code module. Structure carries no rollups.
- Any SDF view.
Dependencies
Section titled “Dependencies”- T-JJHY-sdlc-module-graph-emits-structure-and-control-units-as-json
- T-G3EH-federated-planning-roots-union-loading-flat-resolution-union (not landed; union loading reads each planning directory)
Depends on
Section titled “Depends on”T-JJHY-sdlc-module-graph-emits-structure-and-control-units-as-json, T-G3EH-federated-planning-roots-union-loading-flat-resolution-union