pub struct PlanAuthoring {
pub enabled: bool,
pub min_nodes: u32,
}Expand description
Whether, and how, DISCOVER may author a plan — a Workflow grain: named steps, edges with conditions in the runtime’s frozen grammar, validated before a reviewer sees it — beside the Skill that carries the prose.
A skill is what a model reads; a plan is what the runtime can check and
run. PAST-Bench’s own labels call every procedural family “ordered steps,
tools, conditions… a patched v2 supersedes v1” — which is a Workflow, and
its patch is the plan_revision this engine already has. Storing the
procedure as a plan buys structural validation (unique, reachable nodes;
conditions that parse; bounded cycles) at author time, and puts the
procedure where areev run, the run journal and run_outcome can reach
it. Governed like every draft; never auto-applied.
Fields§
§enabled: boolOffer the plan proposal kind (default: yes, under LLM enrichment).
min_nodes: u32Fewer steps than this is a lesson, not a procedure (default 2).