DR-074 — Projects are multi-task containers; the 1:1 S472 project→task records collapse

Status: accepted · S-current (ratified by Liam; model doc: specs/id-148-initiatives-ledger-cli/notes/new-dev-workflow-concepts.md, migrated S507 out of canonical’s gitignored scratch)

Per the initiatives topology, ONLY projects carry linked_tasks/linked_backlog, and a project is a container for MULTIPLE tasks grouped around a shared outcome — so the S472 pattern of one project per task is over-split. The five S472 follow-up projects collapse to fewer multi-task projects: sub-initiative 4.2 (“Ledger creation and improvements”) → one project linking tasks 148 + data-quality + qol; sub-initiative 4.4 → one project linking 149 + 150. Initiative 4’s initiative-level linked_tasks/linked_backlog (the only misplaced-link node) redistribute down to projects and are then removed. Executed PROGRAMMATICALLY via the new initiatives CLI verbs (create/delete-project, move-task/move-backlog) in the initiatives-ledger-data-quality task — NOT by hand-editing JSON. Exact groupings are Liam’s to confirm at execution.