Expand description
Planner passes and execution plan model scaffolding. See PLAN.md for staged tasks.
Exposes a deterministic pass pipeline from registry-sourced graphs to an ExecutionPlan.
Pass order (stubs today, contract documented): hydrate_registry -> typecheck -> convert -> align -> gpu -> schedule -> lint.
Modules§
Structs§
- Diagnostic
- Planner diagnostic entry.
- Diagnostic
Span - Where a diagnostic applies.
- Edge
- Edge from one node/port to another.
- Edge
Buffer Info - Edge buffer hints used by the GPU pass.
- Execution
Plan - Final execution plan with diagnostics and stable hash for goldens.
- GpuSegment
- Contiguous GPU segment metadata.
- Graph
- Planner input graph (pre-pass).
- Node
Instance - An instantiated node, identified by registry id.
- NodeRef
- Node reference within a graph (index-based for compactness).
- Planner
Config - Static planner config controlling optional passes.
- Planner
Input - Input to the planner: a graph plus registry reference.
- Planner
Output - Planner output: final plan and any diagnostics.
- PortRef
- Port reference by name within a node.
- Stable
Hash - Stable hash helper used for goldens; simple FNV-1a for determinism.
Enums§
- Compute
Affinity - Compute affinity hint for scheduling/GPU pass. Compute affinity hint for scheduling/GPU pass.
- Diagnostic
Code - Planner diagnostic codes (non-exhaustive).
Constants§
- DEFAULT_
PLAN_ VERSION - Default execution-plan version for deterministic serde/goldens.
Functions§
- build_
plan - Build an execution plan by running the ordered pass pipeline. Currently stubs; contracts are enforced via deterministic diagnostics ordering. Build an execution plan from a graph and registry.