T-EIZX-declare-this-repo-s-own-control-units-as-planning-roots

State: planning/proposed · Impact: medium · Complexity: small

Goal

This repo should be the first instance of the module graph. The approved breakdown in docs/planning/notes/N-A6ZD-module-breakdown.md names 12 control units: dev (the repo root), ontological, determined, agent-pants, augmented, pumice, zoo, sdf (nested in ontological), engine, markdown, app-kit, and cli-substrate. Each becomes a control unit by declaring a planning root. The config keys come from D-SK9G-cross-project-addressing and have not landed.

Proposed

The root sdlc.yaml declares planning_roots: for the 11 sub-units, using the YAML in the breakdown’s section 5. Every unit is a folder, and its planning root is <folder>/docs/planning/. members: is only for cross-tree exceptions, such as agent-pants claiming exp-agent-pants and product-agent-pants out of solutions/determined. Each root is scaffolded with sdlc project setup --planning-root <id>. The contiguous units with no corpus (ontological, augmented, pumice) go first. The four suites register as their folders land: engine, markdown, app-kit, and cli-substrate, each under packages/<suite>/. determined joins last, after union loading lands. Execution entities that belong to one unit move there in a later triage.

Acceptance criteria

AC-1: sdlc.yaml declares the 11 sub-unit roots from docs/planning/notes/N-A6ZD-module-breakdown.md, and sdlc entities audit passes, including the one-unit-per-module check.
AC-2: sdlc module graph shows the 12 control units, each with its members, and every moon project lands in exactly one of them.
AC-3: A task created under a sub-root appears in that unit’s rollup and nowhere else.
AC-4: determined’s 19 ids that clash with the root corpus (C-0001..C-0003, D-0002..D-0014, D-0016..D-0018) are renumbered and their links rewritten. Its decisions move from solutions/determined/docs/decisions/ under solutions/determined/docs/planning/, and its separate sdlc.yaml is retired or reconciled with the sub-root rules.

Out of scope

Moving existing entities into the sub-roots. That is a separate triage.
The control plane’s unit registry (T-Y8DS-the-control-plane-unit-registry-reads-planning-roots).

Dependencies

T-CY6T-control-units-a-planning-root-is-the-boundary-and-every
T-G3EH-federated-planning-roots-union-loading-flat-resolution-union (not landed)
The four suite moves, each of which registers its root: T-SKMB-co-locate-the-engine-suite-under-packages-engine, T-Z0KK-co-locate-the-markdown-suite-under-packages-markdown, T-PLW6-co-locate-the-app-kit-suite-under-packages-app-kit, T-G6KG-co-locate-the-cli-substrate-suite-under-packages-cli

Depends on

T-CY6T-control-units-a-planning-root-is-the-boundary-and-every, T-G3EH-federated-planning-roots-union-loading-flat-resolution-union, T-SKMB-co-locate-the-engine-suite-under-packages-engine, T-Z0KK-co-locate-the-markdown-suite-under-packages-markdown, T-PLW6-co-locate-the-app-kit-suite-under-packages-app-kit, T-G6KG-co-locate-the-cli-substrate-suite-under-packages-cli

← Back to Tasks