T-G3EH-federated-planning-roots-union-loading-flat-resolution-union
State: planning/proposed · Impact: medium · Complexity: large
The control plane already wants three planning units in this repo. Corpus loading, resolution, and minting all assume one root.
Proposed
Section titled “Proposed”Corpus loading unions the root and every planning_roots entry. Wikilinks resolve flat; a duplicate
basename across roots is an audit error. Minting reads the union taken set. Audit warns on a
definition kind under a sub-root. sdlc project setup --planning-root <id> scaffolds a sub-root.
Generated artifacts stay at the project root.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: A fixture with two roots and a duplicate basename fails audit; the same fixture without the duplicate passes and both roots’ entities appear in the index.
- AC-2:
task createin a two-root project never mints an id present in either root. - AC-3: A decision file under a sub-root produces an audit warning, not an error.
Out of scope
Section titled “Out of scope”- A second
sdlc.yamlunder a sub-root.
Dependencies
Section titled “Dependencies”Depends on
Section titled “Depends on”T-K9AI-slug-projects-and-planning-roots-keys-in-sdlc-yaml-with