Project Control Plane DAG Consumption
Project Control Plane DAG Consumption
Purpose
This document defines the minimum platform capability required for platform-template-bootstrap to orchestrate the first project-control-plane build.
Current State Assessment
The platform already has two strong foundations:
- a canonical task-graph model
- an ExecPlan projection model
Existing evidence:
spec/task-graph.schema.yamldocs/planner-execplan-projection.mddocs/remaining-work-graph.mddocs/codex-orchestrator-execution-loop.md
That means the platform already knows how to:
- treat graph state as canonical
- project graph state into governed ExecPlans
- traverse bounded ready work
- preserve projection-versus-authority boundaries
Gap For This Project
The missing piece is not a new graph engine.
The missing piece is an explicit way to package a subset of graph nodes into a higher-order grouped execution slice without replacing the canonical graph.
For project-control-plane, that grouped layer is:
- grouped foundation exec plans
- grouped implementation packets
- grouped DAG bundles that reference task-node ids
Required Capability
platform-template-bootstrap must support two linked views:
1. Task-Level DAG
This remains canonical for dependency traversal.
Examples:
fnd-001fnd-002fnd-003
2. Grouped DAG Bundle
This is a projection that packages multiple task-level nodes into one governed execution slice.
Examples:
foundation bootstrapbronze scan modelsilver contract model
The grouped bundle must be projection-only. It cannot replace the canonical task graph.
Platform Rule
The platform should treat grouped DAG bundles the same way it treats ExecPlans:
- as governed projections
- sourced from canonical graph-backed state
- lineage-preserving
- bounded
Minimal Implementation Direction
The first implementation slice should add a grouped execution-bundle contract that:
- has a stable bundle id
- references one source DAG id
- references one source ExecPlan id where applicable
- carries an ordered list of node ids
- carries scope and status metadata
- can expand into task packets
Non-Goals
This slice should not:
- replace the task graph
- introduce a second canonical graph
- redesign the entire orchestrator
- generalize every future bundle concept up front
Acceptance
The platform is sufficient for project-control-plane when it can:
- ingest the task-level DAG
- ingest a grouped DAG bundle projection
- validate that grouped bundles reference legal node ids
- expand a grouped bundle into bounded task packets
- preserve lineage from bundle to task packet to execution outputs