T-Y8DS-the-control-plane-unit-registry-reads-planning-roots
State: planning/proposed · Impact: medium · Complexity: small
The ontological plan hard-codes three planning units. The roster should be the source.
Proposed
Section titled “Proposed”The unit registry is built from the project root plus planning_roots, exposed through a published
surface.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: Adding a planning root to
sdlc.yamlmakes it appear in the control plane without a code change.
Out of scope
Section titled “Out of scope”- Any control-plane view work.
Dependencies
Section titled “Dependencies”- T-G3EH-federated-planning-roots-union-loading-flat-resolution-union
- T-NAQB-the-ontological-control-plane-reads-the-entity-model-through
Depends on
Section titled “Depends on”T-G3EH-federated-planning-roots-union-loading-flat-resolution-union, T-NAQB-the-ontological-control-plane-reads-the-entity-model-through