T-CTEV-cross-repo-modules-and-qualified-links-in-the-module-graph
State: planning/proposed · Impact: medium · Complexity: medium
The graph nests across repos, not only inside one. A peer repo brings its own code modules and control units, and a link into it is a qualified id from D-SK9G-cross-project-addressing. This is a stub: the roster keys and the qualified-link resolver have not landed.
Proposed
Section titled “Proposed”sdlc module graph adds each peer in the projects: roster. A present peer contributes its
structural layer and its control units under its slug. A qualified link from a task in one unit to a
task in a peer’s unit becomes an edge between the two units. An absent peer shows as one
unverified unit, matching the audit state D-SK9G defines.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: With a two-repo fixture, the graph shows both repos’ control units and a cross-repo edge
for a qualified
depends_on. - AC-2: An absent peer appears as
unverifiedand does not fail the op. - AC-3: SDF draws the peer’s units without a change to the renderings.
Out of scope
Section titled “Out of scope”- Dispatching work into a peer.
- A project entity.
Dependencies
Section titled “Dependencies”- T-JJHY-sdlc-module-graph-emits-structure-and-control-units-as-json
- T-K9AI-slug-projects-and-planning-roots-keys-in-sdlc-yaml-with (not landed)
- T-KBOI-qualified-wikilink-pattern-resolver-and-the-audit-unverified (not landed)
Depends on
Section titled “Depends on”T-JJHY-sdlc-module-graph-emits-structure-and-control-units-as-json, T-K9AI-slug-projects-and-planning-roots-keys-in-sdlc-yaml-with, T-KBOI-qualified-wikilink-pattern-resolver-and-the-audit-unverified