Expand description
Load-time planning driver.
Program anchor: docs/session-prompts/plan-is-graph-rebuild.md
(Phase D — load-time, input-independent graph build).
Planner::warm is the explicit load-time entry: model loaders
(and user code that builds a graph ahead of realizing it) may call
it after graph construction to pre-optimize.
§Status post-PR-A3b-2
The identity-keyed PlanStore memoization layer
warm used to populate was deleted in PR-A3b-2 (the “plan IS the
graph” rebuild retires the separate ExecutionPlan source of truth
and the per-graph plan store). With the load-time-build model not
yet landed (Phase D), warm has nothing to memoize: the optimized
form lives in the graph, built once per realize by
optimize_graph, and there is no separate plan to stash and reuse.
warm is therefore a no-op today, preserved as the seam Phase D
will reimplement (optimize the graph in place at load so the first
realize finds the multi-path form already written). The realize path
remains authoritative — it runs optimize_graph itself.
Structs§
- Planner
- Load-time planning driver. Stateless.