Table of contents
Plan
Formal definition
A Plan is a pair :
together with:
- A precondition specifying the states from which the plan applies
- A goal condition specifying the states the plan aims to achieve
where:
- is the operation set — the finite collection of steps (intended actions, operations, or tasks) that the plan consists of; each step has its own preconditions (what must hold before executes) and effects (what changes in the state when it executes)
- is the ordering constraint — a strict partial order on specifying which steps must precede which; means “step must be completed before step begins”; is the plan’s causal and temporal skeleton; steps not related by may execute in any order (or concurrently)
The plan is valid iff: there exists a total ordering of extending such that, starting from any state satisfying , sequentially executing produces a state satisfying .
Four invariants. is a plan iff:
-
Finite commitment: . A plan is a finite structure — it commits to a bounded set of intended steps. An infinite plan is not a plan but a policy or strategy. Finiteness is what makes plans executably communicable: one can state a plan, hand it off, and verify its completion.
-
Partial order consistency: is a strict partial order (irreflexive, asymmetric, transitive) with no cycles. A plan with a cyclic dependency () cannot be executed. The acyclicity of is the condition that makes the plan a directed acyclic structure rather than a loop.
-
Causal groundedness: every ordering constraint in is causally grounded — must precede either because produces an effect that requires (producer-consumer dependency), or because ’s execution would threaten ’s precondition if done after (threat ordering). Ordering constraints without causal grounding are arbitrary serializations, not plan structure.
-
Means-end coherence: every step is connected to the goal by a chain of means-end relations — is included in the plan because it contributes (as a necessary or sufficient means) to some subgoal that itself contributes to the plan’s goal . Formally: there is no step such that removing from (and dropping all constraints involving ) leaves achievable from . A step that can be removed without affecting plan validity is not part of the plan’s means-end structure — it is redundant. Means-end coherence ensures plans are not padded with irrelevant steps.
Plan refinement. Plans over the same goal admit a refinement preorder: iff , where is the set of total orderings (linearizations) of consistent with . A refinement commits to more — it permits fewer execution orderings but every ordering it permits is also permitted by . In terms of the ordering relation: iff (the concrete plan adds ordering constraints). A total ordering of consistent with is the most refined plan: it selects a single linearization. The partial-order plan with no ordering constraints is the least refined plan — all linearizations are permitted.
Fikes and Nilsson: STRIPS
Richard Fikes and Nils Nilsson (STRIPS: A New Approach to the Application of Theorem Proving to Problem Solving, 1971) introduced the first formal planning language and the foundational planning algorithm:
A STRIPS operator (action schema) is a triple :
- : the precondition — a set of positive literals that must hold in the current state for the operator to be applicable
- : the add list — literals made true by the operator’s execution
- : the delete list — literals made false by the operator’s execution
A STRIPS plan is a total sequence of operator instances such that:
- is applicable in the initial state ()
- Each successive is applicable in the state resulting from applying to
- The goal condition is satisfied in the final state
STRIPS operates with the closed world assumption: every literal not asserted to be true is assumed false. The STRIPS representation is propositional: state variables are ground literals (no quantification over individuals).
The STRIPS algorithm: goal regression — work backward from the goal condition, finding operators whose add-lists include goal literals, then recurse on the operators’ preconditions. The algorithm is correct (produces valid plans) but incomplete for some domains (the Sussman anomaly shows that STRIPS-style regression can fail on interacting subgoals).
McAllester and Rosenblitt: partial-order planning
David McAllester and David Rosenblitt (Systematic Nonlinear Planning, 1991; building on Sacerdoti’s NOAH 1975 and Tate’s NONLIN 1977) formalized partial-order planning — a more expressive plan representation than STRIPS’s total sequences:
A partial-order plan is a tuple :
- : a set of steps (operator instances)
- : open precondition goals — preconditions of steps not yet causally supported
- : temporal ordering constraints on steps
- : causal links — asserting that step achieves precondition of step
Threat resolution: a step threatens a causal link if might delete and could execute between and . Threats are resolved by demotion () or promotion ().
The partial-order planner systematically refines a partial plan by: (1) selecting an open goal and finding an achiever, (2) detecting threats and resolving them. The plan is complete when all goals have causal support and all threats are resolved. Partial-order planning produces plans with the minimum necessary ordering constraints — the most flexible execution orderings.
Bratman: plans as practical reasoning structures
Michael Bratman (Intention, Plans, and Practical Reason, 1987) provides the philosophical account of what plans ARE — their role in practical reasoning, not just their formal structure:
Plans as commitments: for Bratman, a plan is an intention — a mental state that (i) disposes the agent toward certain actions, (ii) shapes future practical reasoning, and (iii) plays an important coordinating role in the agent’s activity over time. Plans are not merely representations of intended action sequences; they are normatively binding commitments that the agent must have reasons to abandon.
Three functional roles of plans:
- Coordination over time: plans allow an agent to coordinate its activities — a plan settled upon now guides future deliberation; one need not re-deliberate from scratch at each moment
- Coordination with others: shared plans provide a common structure for cooperative action — two agents with a shared plan can coordinate without continuous negotiation
- Nesting: plans nest — sub-plans are adopted in service of higher-level plans; the plan hierarchy connects immediate actions to long-term intentions
Partial plans: Bratman argues that plans are typically partial — they specify some but not all aspects of future action. Partial plans leave room for further specification as execution proceeds. A fully specified total-order plan is the exception; partial plans with underspecified steps and unresolved choices are the norm.
Reconsideration: plans can be reconsidered — abandoned, revised, or replaced — but rational reconsideration requires reasons. The agent’s commitment to a plan is defeasible but not arbitrary: abandoning a plan requires that something has changed that makes the plan no longer appropriate, not just that the agent has new preferences. This normative structure distinguishes plans from mere sequences of intended actions.
PDDL: the standard formal planning language
Ghallab, Howe, Knoblock et al. (PDDL — The Planning Domain Definition Language, 1998) standardized the planning language used in the International Planning Competition:
A PDDL problem consists of:
- A domain definition: object types, predicates, and action schemas (STRIPS-style operators with typed parameters)
- A problem definition: initial state (ground literal assignments), goal condition (formula over ground atoms), and object instances
A PDDL plan is a sequence of ground action instances that transforms the initial state into a state satisfying the goal. PDDL extensions support: numerical fluents, temporal constraints (durations, concurrency), probabilistic effects, and preferences.
PDDL’s action schemas are parameterized STRIPS operators: where is a tuple of typed variables; grounding with object instances produces a STRIPS operator.
Open questions
- Whether Bratman’s plan nesting (sub-plans in service of higher plans) corresponds to the tree structure of causal links in partial-order planning — whether the normative hierarchy of intentions has the same formal structure as the causal link hierarchy in the plan’s DAG.
- Whether there is a coalgebraic account of planning — whether a planner is a coalgebra that maps problem states to plan extensions, and whether the planning problem’s solution corresponds to a final coalgebra (the complete plan).
- Whether partial-order plans have a sheaf-theoretic characterization — whether a partial plan is a local section of the “possible plan” presheaf, and whether plan extension (adding steps and causal links) is the gluing of local sections into a global section that covers all open goals.
- Whether Bratman’s reconsideration norm (defeasible but not arbitrary plan abandonment) can be formalized as a refinement relation on plans — whether a revised plan is a refinement of the original in some appropriate sense, and whether the conditions for legitimate reconsideration correspond to the conditions for refinement.