Intelligence, Agency & Consciousness · Paper 0088

When a plan is a proof guided by distance

Soutchanski and Young revive a foundational idea: ask logic to prove that a goal follows after an executable history, but let an A* heuristic decide which proof branch deserves attention first.

Intelligence, Agency & Consciousness · Paper 0088

When a plan is a proof guided by distance

Rajesh Ranjan Mahapatra

Soutchanski and Young revive a foundational idea: ask logic to prove that a goal follows after an executable history, but let an A* heuristic decide which proof branch deserves attention first.

© 2026 Rajesh Ranjan Mahapatra. 25 min read

When a plan is a proof guided by distanceAll AI Research Library

TLDR

Five-point orientation
  1. Plans are proofs about histories. A solution is a situation term whose action prefixes are executable and whose final situation entails the goal.
  2. Actions remain lifted. Schemas are grounded from their preconditions at the current situation instead of being fully instantiated before search.
  3. Progression makes states implicit. Nodes are histories; the current state is reconstructed from the initial theory and successor-state axioms when needed.
  4. Relaxed reachability guides A*. A Graphplan-style graph ignores delete effects and recursively selects actions supporting the goal.
  5. Logic buys clarity, not speed. TPLH visits few nodes and finds short plans, but its interpreted prototype is orders of magnitude slower than compiled planners.
01 · an old programme resumed

Planning and theorem proving have been connected since the field’s early years. The paper’s intervention is not to rediscover that connection but to make it computationally interesting again.

In 1969, Cordell Green described planning as deduction: encode actions and situations in first-order logic, state a goal existentially, then extract a sequence of actions from a proof. The idea is beautifully general. A logical theory can represent action preconditions, effects, object identities and incomplete knowledge in one language. But blind proof search does not inherit the practical guidance developed by half a century of classical planners.

STRIPS took a specialised route. It represented states extensionally and actions by add and delete lists, turning planning into graph search. Later systems such as FF and Fast Downward combined careful compilation with informative heuristics. Their speed made propositional grounding: the creation of every relevant ground action before search: a standard choice, even when the domain was originally written with variables.

Soutchanski and Young place both traditions in one machine. TPLH uses Reiter’s situation calculus and a Basic Action Theory as the semantics. It explores situation terms with A*. A delete-relaxation heuristic, inspired by FF and Graphplan, estimates distance to the goal. The result is theorem proving whose proof order is chosen by planning knowledge.

The revival matters because grounding can be expensive or impossible in richer first-order settings. TPLH keeps action schemas lifted and finds ground instances only when their preconditions hold in the current state. The authors also seek a route towards theories with incomplete initial information, successor-state axioms containing context conditions and fewer closed-world assumptions.

This is a research prototype, not a victory claim over mature planners. Its evidence is more discriminating: despite extreme runtime overhead, it often expands markedly fewer situations than Fast Downward expands states while producing plans of comparable length. That separation between guidance quality and implementation speed is the paper’s central empirical tension.

Two traditions converge in TPLHTheorem proving and situation calculus meet STRIPS, Graphplan and heuristic A star inside TPLH.GREENproof searchSITUATIONcalculusBASIC ACTIONtheorySTRIPSstate searchGRAPHPLANrelaxationFF / A*heuristicsTPLHproofs orderedby distance
Figure 1 · A hybrid inheritance. TPLH keeps the model theory of situation calculus and imports the search discipline of heuristic planners.Source scope: primary paper, Introduction and Related Work.

Worked example 1 · deduction without direction

A proof procedure can enumerate every executable stack, unstack and move history until one entails on(A,B). A relaxed-distance score instead favours histories that add clear(B) and holding(A), turning logical possibility into directed search.

Causal probe 1 · remove the heuristic

The semantics and bounded completeness argument remain, but the procedure loses an estimate of which situation is closer to the goal. The novelty lies in separating correctness from the order in which correct branches are explored.

02 · histories, not merged states

A situation is the route taken, not merely the facts now true

Situation calculus gives actions a history-sensitive home. Two histories may agree on every fluent and still be different situations.

The distinguished constant S0 denotes the initial situation. If action a occurs in situation s, the function term do(a,s) denotes the result. A sequence [a1,…,an] abbreviates a nested term whose outermost layer is the latest action. In Prolog, S0 can be the empty list and a successor a list extended by one action.

This construction forms a tree. Every non-initial situation has one predecessor, and a situation cannot be its own ancestor. Different action sequences never merge merely because they produce the same fluent valuation. That property eliminates duplicate situation terms from the open queue: no distinct search paths create the same history.

Yet “no duplicate situations” is not “no repeated states”. Move a block away and back, or inspect an object twice without changing anything, and distinct histories may describe identical current facts. State-space planners can detect and merge that equivalence; TPLH deliberately retains it because situations are histories in the semantics.

A fluent is a predicate or function whose final argument is a situation. On(A,B,s) can change with history; an atemporal relation such as A≠B does not. The world at s is not stored as an autonomous node in the logical language. It is what the theory entails about fluents at s.

This distinction explains the memory policy. TPLH stores the initial state and action histories. When it removes a situation from the queue, it progresses the initial state along that history to reconstruct the current valuation. Less state memory is retained, but previous effects may be replayed many times.

Situation tree and repeated stateHistories branch from S zero while two different routes return to the same fluent valuation.S₀outwaitbackwaitoutwaitsame fluent state · different histories
Figure 2 · The search space remembers routes. Equal valuations reached by different sequences remain different situation terms.Source scope: primary paper, Section 2 and Definition 1.

Worked example 2 · two ways to be home

At S0, home is true. The history [out,back] makes it true again; [wait] leaves it true. A state graph can identify one valuation. Situation calculus distinguishes do(back,do(out,S0)) from do(wait,S0).

Causal probe 2 · merge equal valuations

Search may shrink, but the node is no longer a unique proof witness. Any theory that refers to history: action counts, past events or trajectory constraints: can distinguish the routes. The tree is a semantic commitment, not an accidental data structure.

03 · the Basic Action Theory

Five axiom families turn action stories into consequences

A Basic Action Theory, or BAT, collects what is needed to determine whether an action may happen and what persists afterwards.

The foundational axioms Σ describe situations: S0 has no predecessor, do constructs successors, and induction reaches every situation. Action precondition axioms Dap state when each action is possible. For action schema A(x), poss(A(x),s) is equivalent to a formula ΠA(x,s) uniform in s.

Successor-state axioms Dss solve the representational frame problem. Instead of separate non-change axioms for every action–fluent pair, one biconditional states all ways a fluent becomes true and all ways it remains true because no terminating action occurred. Effects and persistence share one formula.

Unique-name axioms Duna say distinct action function symbols denote different actions and, where required, distinguish object names. The initial theory DS0 supplies facts and constraints about the starting world. Together: D=Σ∧Dss∧Dap∧Duna∧DS0.

Consider holding(x). Pickup makes it true; Drop makes it false; other actions preserve it. The successor-state axiom is not merely an update rule. It is a logical biconditional defining exactly when holding(x,do(a,s)) follows.

The formal account is broader than the implementation. Results for proper-plus initial theories and local-effect BATs can support incomplete information without declaring every unnamed fact false. The ECLiPSe Prolog prototype, however, requires domain closure and a closed-world assumption. That limit belongs to the software, not to every theorem-proving planner licensed by the formalism.

D = Σ ∧ Dss ∧ Dap ∧ Duna ∧ DS0
poss(PickUp(x),s) ↔ clear(x,s) ∧ handEmpty(s)
holding(x,do(a,s)) ↔ a=PickUp(x) ∨ (holding(x,s) ∧ a≠Drop(x))
Five components of a Basic Action TheoryFoundations, possibility, successor states, unique names and the initial theory surround a BAT core.BASIC ACTIONTHEORYΣ · SITUATIONStree foundationsDap · POSSIBILITYpreconditionsDss · CHANGEeffects + persistenceDuna · NAMESdistinct symbolsDS₀ · INITIALstarting facts
Figure 3 · One theory, five jobs. The BAT separates history, executability, change, naming and initial knowledge so each can be audited.Source scope: primary paper, Definition 2.

Worked example 3 · persistence without a frame list

If holding(A,s) and the next action is Paint(B), the biconditional entails holding(A,do(Paint(B),s)): Paint is not Drop(A). Persistence follows from the same axiom that handles pickup and drop.

Causal probe 3 · confuse theory and prototype

Saying “situation calculus requires complete initial states” overgeneralises a software restriction. The paper discusses progression under incomplete proper-plus initial theories, then marks closed-world and domain-closure support as future implementation work.

04 · planning as entailment

A bounded plan exists when one executable situation entails the goal

The planning problem becomes a model-theoretic question with a length bound. The bound makes the history tree finite; executability makes every prefix legal.

A situation is executable if S0 is executable and each successor do(a,s) is executable only when s is executable and poss(a,s) holds. For a sequence α1,…,αn, Theorem 1 expands that recursion into precondition claims at every preceding situation.

Given goal formula G(s) and upper bound N, planning asks whether D entails an s whose length is at most N, whose history is executable and whose final situation satisfies G. A witness is not just an action list ending in a goal valuation. The logical query certifies each transition.

Theorem 3 connects the existential statement to search. A ground situation term of length at most N is a solution exactly when one can choose action-schema indices and grounding substitutions such that the theory entails the goal after their composition and the possibility formula at every prefix.

This licenses lifted branching. Suppose Load(x,t,l) has variables. At a situation, the planner asks which substitutions make its precondition true: perhaps x=crate7, t=truck2 and l=depot. Only those ground instances become successors. It need not construct every crate–truck–location combination first.

Soundness and completeness are bounded. If N is at least the shortest solution length and the finite tree is searched faithfully, a solution can be found. If every solution is longer, failure proves only that the chosen horizon contains none. The bound is a termination device and an evidential limit.

D ⊨ ∃s [ Length(s) ≤ N ∧ executable(s) ∧ G(s) ]

executable([α₁,…,αₙ]) iff poss(α₁,S₀) ∧ … ∧ poss(αₙ,do([α₁,…,αₙ₋₁],S₀))
A query unfolds into executable prefixesAn existential goal query leads through schema choice, grounding and precondition checks to a proof witness.∃ situation sgoal(s) · |s|≤Nschema choicegrounding θposs at prefixdo(a₁,S₀)do(a₂,…)do(aₙ,…)GOALlegal proof witness
Figure 4 · Proof obligations become branches. Every successor needs a schema, substitution and entailed precondition; the completed history witnesses the goal.Source scope: primary paper, Theorems 1–3.

Worked example 4 · a grounded witness

For delivered(crate7), [Load(x,t,l),Drive(t,l,d),Unload(x,t,d)] becomes a candidate only after substitutions make every prefix possible. Its nested situation is a proof witness if delivered(crate7) is entailed at the end.

Causal probe 4 · set N below the shortest plan

The finite tree can be exhausted soundly and still fail. That means “no witness within this horizon”, not “the unbounded problem is unsolvable”. Any reproduction must preserve N.

05 · the TPLH loop

A* orders situation proofs by travelled cost plus relaxed distance

TPLH’s main algorithm is recognisably A*, but its nodes, state access and successor generation retain situation-calculus semantics.

The priority queue begins with S0. Every situation has f=g+h: its history length plus estimated remaining distance. Unit action costs make g exactly Length(s). The queue removes the lowest value, with implementation-specific tie handling.

On removal, the planner progresses the initial database along the history to obtain Now. If the goal holds, it returns the situation, readable as an action list. Otherwise it finds action instances whose preconditions are satisfied there.

For each possible Ai, TPLH constructs do(Ai,s), progresses across that action, checks the length bound and evaluates its heuristic with remaining lookahead d=N−Length(s). Qualifying successors enter the queue.

There is no closed list for duplicate situations because histories are unique. That saves comparison but admits equivalent fluent states under multiple histories. Nor does every queue node cache a state. Reconstructing Now after a pop trades space for repeated progression work.

The pseudocode exposes useful modularity. D defines legal worlds, progression answers what is true now, FindAllPossibleActions supplies lifted successors, H estimates distance and the priority queue imposes policy. Improving one component need not rewrite the semantics.

The TPLH A star loopA queue feeds progression, goal testing, action grounding, successor creation and scoring before looping.PRIORITY QUEUEremove best fPROGRESShistory → NowGOAL?return if trueGROUND ACTIONSpreconditions trueSUCCESSORdo(Aᵢ,s), within NSCORE|s| + HUNIQUE HISTORIES · IMPLICIT STATESsituation tree beneath every operation
Figure 5 · A proof-search circuit. TPLH reconstructs a state, checks the goal, grounds legal actions and feeds scored history successors back to A*.Source scope: primary paper, Algorithm 1.

Worked example 5 · why f changes

A two-action history has g=2. If its relaxed graph needs three layers, f=5. A three-action history with h=1 receives f=4 and is explored first: travelling farther can be rational when the goal appears much closer.

Causal probe 5 · cache every progressed state

Progression time falls but node memory rises. That tests a different engineering point on the same semantics. The paper proposes more efficient representations; its memory-saving choice is not logically necessary.

06 · lifted successor generation

Ground only the action instances the current proof can use

“Lifted” here names when variables disappear. The domain begins with schemas; current facts determine ground instances during search.

A propositional planner commonly compiles every parameterised action against compatible objects. In logistics, even impossible package–vehicle–location triples can appear before reachability pruning. That expense occurs regardless of which states are later visited.

TPLH queries action preconditions against Now. For Load(p,t,l), it solves at(p,l), at(t,l) and empty(t) to obtain substitutions supported by the current database. A package elsewhere never combines with the truck here. The action is ground when added, but grounding is delayed and contextual.

The approach resembles theorem proving because unification and query answering produce substitutions. It exposes richer future possibilities: preconditions could contain formulas that do not compile neatly into a fixed propositional operator set. The formal account is designed with that extensibility in view.

The prototype narrows the promise. Benchmark preconditions are conjunctions, optionally including negative equalities; successor-state axioms lack context conditions; goals are conjunctions of ground fluents. Domains are essentially STRIPS tasks translated from PDDL. Possible-action generation can itself be a bottleneck.

Lifted does not automatically mean small. If a state satisfies a schema many ways, the query returns many instances. Nor does run-time grounding erase repeated work across equivalent states. Its value depends on how selectively current preconditions constrain variables and how efficiently answers are indexed.

Run-time grounding from current preconditionsA Load schema and current facts produce two legal substitutions while an impossible combination is omitted.Load(p,t,l)at(p,l)at(t,l)empty(t)variables remainuntil this situationis visitedNOWat(crate7,depot)at(crate9,depot)at(crate4,port)at(truck2,depot)empty(truck2)crate7 · truck2 · depotcrate9 · truck2 · depotcrate4 × truck2 is absent: locations do not unify
Figure 6 · Grounding as a situated query. Current facts bind schema variables; impossible combinations have no precondition answer now.Source scope: primary paper, Algorithms 1–2 and implementation discussion.

Worked example 6 · selective binding

Three packages and two trucks admit eighteen naïve triples over three locations. If only two packages share depot with one empty truck, the current precondition query yields two Load actions.

Causal probe 6 · add a weakly constrained schema

Pair(x,y), requiring only x≠y, still produces quadratic branching. Lifted generation postpones combinatorics; it does not repeal them. Strong relational preconditions create the clearest advantage.

07 · delete-relaxed reachability

Imagine that achievements accumulate and estimate how far the goal lies

The heuristic builds a planning graph from the current state while ignoring negative effects. Once achieved, a fact remains available throughout the imagined future.

At each relaxed layer, the algorithm finds possible actions in the relaxed state. It retains relevant actions: those with at least one positive effect not already present: and progresses by adding all positive effects. Deletes are omitted. Each fact layer contains its predecessor.

Expansion stops when all goal literals appear or remaining lookahead is exhausted. If the bound d is crossed without reachability, the implementation returns a penalty beyond the visible horizon. Heuristic computation is tied to bounded search rather than pretending the relaxed problem is unlimited.

Ignoring deletes makes progress easier. A key can remain held after an imagined action that consumes it; mutually exclusive properties can coexist. The graph offers directional evidence, not an executable plan. It may underestimate interactions requiring restoration of deleted conditions.

The design is FF-inspired and Graphplan-like, but reaching a layer is not the final estimate. A second recursive phase selects supporting actions and their preconditions, approximating how many supports are required.

Actions adding nothing novel are filtered. They cannot improve a later monotonic fact layer. This simple relevance test prevents the relaxed graph filling with applicable operations that do not move any reachable fact frontier.

A delete-relaxed planning graphFact layers grow from key through open to inside while the delete effect on key is crossed out.LAYER 0LAYER 1LAYER 2keykeyopenkeyopeninsideunlockenterdelete key
Figure 7 · Optimism by omission. Unlock adds open while its key deletion is ignored, so later layers preserve every earlier achievement.Source scope: primary paper, Algorithms 2–3.

Worked example 7 · a useful underestimate

From key, Unlock adds open and Enter adds inside. The graph reaches the goal in two layers. If unlocking consumes the key but entry needs only open, it happens to be executable; if entry needs both, restoration cost is hidden.

Causal probe 7 · keep delete effects

The abstraction becomes real state expansion and loses monotonicity. Reachability is more faithful but far more expensive: the exact trade relaxation was introduced to avoid.

08 · backward support selection

Reach goals forward, then explain them backwards

The second phase turns relaxed reachability into a support count. Goals ask which actions first made them available.

Once the graph reaches the goal, recursion examines newly achieved literals at the latest relevant layer. For each, it collects actions whose positive effects support that literal and whose preconditions held in the preceding relaxed state.

Candidate supporters differ because their preconditions become subgoals. The procedure estimates each candidate and chooses a best supporting action. Preconditions from selected supporters are unioned into the next goal set. Facts already available require no added support.

Shared support matters. One action may add two goals; two selected actions may require one common precondition. Unions avoid treating identical subgoals as unrelated. The result is still approximate, but it extracts a causal skeleton instead of returning layer number alone.

This recursion is expensive. The authors report that heuristic computation consumes more than 95 per cent of runtime. Subproblems can be recalculated, making memoisation an obvious target. Indexing possible actions and improving progression are others.

FF-style relaxed-plan estimates are not guaranteed admissible lower bounds for optimal A*. The paper uses them to seek short plans and reports resulting lengths. “A*” describes the queue; it does not certify optimality when h lacks admissibility.

Backward selection of relaxed supportersTwo goals trace backwards to supporting actions and shared preconditions in a compact proof tree.goal: deliveredgoal: signedunloadhandoverregisterat destinationhas packageclerk readyshared supportpackage loaded
Figure 8 · A relaxed causal explanation. Backward recursion chooses actions for goals, gathers their preconditions and recognises shared requirements.Source scope: primary paper, Algorithm 3.

Worked example 8 · shared support

Delivered(P) and signed(P) can be supported by Unload and Register, both requiring has(P). A unioned precondition set asks for has(P) once. Independent branch counting would exaggerate distance.

Causal probe 8 · memoise the support query

If the same relaxed state and subgoal set recur, a stored answer removes repeated recursion without changing h. The paper proposes this because the heuristic dominates runtime.

09 · the benchmark

Few expansions, short plans, slow seconds

Nine domains reveal a prototype whose guidance can be economical even while its implementation is dramatically slower.

TPLH was compared with Fast Downward and Best First Width Search. TPLH and Fast Downward used eager A* with an FF heuristic and sought short unit-cost plans. BFWS used default greedy best-first search, so faster search and potentially longer plans were expected.

The machine was an Intel i7-3770 at 3.40 GHz. TPLH ran inside ECLiPSe CLP 7.0 #63 on x86-64 Linux; competitors were compiled executables. Every TPLH problem had a 30-minute timeout and a 50 MB global-stack limit.

Across Barman, BlocksWorld, ChildSnack, Depot, FreeCell, Grippers, Logistics, Miconic and PipesWorld, mean TPLH plan-length ratio to Fast Downward was approximately one. It visited fewer situations than Fast Downward states on eight of nine averages; PipesWorld, with six retained cases, was the exception.

Against BFWS, average TPLH plans were shorter in all nine. Expansion results varied: lower in four domain averages and worse in five. Means sometimes hid majority wins because severe losses dominated, so the paper also reports the fraction of instances where TPLH was no worse.

Runtime reverses the favourable picture. “Time per step” ratios place TPLH roughly 10²–10³ above Fast Downward and 10³–10⁴ above BFWS. These figures combine interpreted execution, preprocessing, repeated progression, lifted queries and expensive heuristic recursion; they do not isolate one cause.

Domain (retained)TPLH/FD plan · visited · time/stepTPLH/BFWS plan · visited · time/stepr · share r≥.75
Barman (100)1 · .10 · 10².90 · .24 · 10⁴.29 · 0
BlocksWorld (95).98 · .11 · 10².62 · .56 · 10³.60 · .53
ChildSnack (100)1 · .09 · 10².96 · 23.75 · 10⁴.34 · .40
Depot (76)1 · .09 · 10².98 · 2.81 · 10⁴.57 · .51
FreeCell (95)1.01 · .10 · 10².99 · .23 · 10⁴.89 · 1
Grippers (98)1 · .06 · 10².79 · 6.39 · 10³.38 · .30
Logistics (119)1 · .17 · 10³.87 · 4.07 · 10⁴.41 · .29
Miconic (93)1 · .11 · 10².86 · .26 · 10³.57 · .14
PipesWorld (6)1 · 6.06 · 10².94 · 15.27 · 10³.32 · .33
Search economy versus timeMost domain points show fewer visited nodes than Fast Downward yet time per step remains hundreds or thousands of times larger.TPLH / Fast Downward visited nodestime per step ratioequal visitedPipesWorldECONOMY ≠ SPEEDmostly fewer expansions · much slower steps
Figure 9 · The implementation paradox. TPLH usually expands less than Fast Downward yet spends two to three orders of magnitude more time per step.Source scope: primary paper, Tables 1–3. Positions are explanatory, not raw-instance replots.

Worked example 9 · FreeCell’s straight corridor

FreeCell has r=.89 and every retained instance at r≥.75, so visited situations lie close to final plan length. Sequential causal chains make relaxed support mirror the real route unusually well.

Causal probe 9 · read 0.10 as ten times faster

That is a visited-situation ratio, not time. TPLH’s neighbouring time-per-step ratio is about 10². Mixing columns reverses the conclusion.

10 · reading the experiment

Implementation, horizon and aggregation shape the result

The benchmark is informative because its limits are visible. A faithful interpretation keeps them attached to every comparison.

PDDL-to-Prolog domain translation took under a tenth of a second, but initial hash construction cost about 1.5 seconds per BlocksWorld problem and nearly ten per Barman problem. Total time includes it. Removing preprocessing helps easy instances but does not erase the wider gap.

The main horizon was N=100 for instances generally solved within twenty steps. Varying N over 25, 50, 75, 100, 125 and 150 changed time by under 0.5 per cent and left plan length and visits unchanged in tested domains. That local robustness is not a theorem that N never matters.

The dataset began with roughly one hundred generated cases in eight domains and ten pre-existing PipesWorld problems. Timeouts and zero-step exclusions left unequal samples: from 119 Logistics to six PipesWorld. Small cells deserve caution.

Plan length partly reflects policy. TPLH and Fast Downward shared eager A* with FF guidance; BFWS used greedy best-first. TPLH’s shorter plans than BFWS are useful, but do not isolate representation from objective.

The ratio r=plan length divided by visited situations diagnoses search shape. Near one means few situations outside a final route. ChildSnack’s interleavable actions and late goal atoms weaken relaxed guidance; FreeCell’s sequential dependencies strengthen it. The ratio is not runtime or absolute difficulty.

Memory speed expressiveness frontierA triangular field places TPLH near lifted expressiveness and low stored-state memory but away from implementation speed.RICHER LOGICAL EXPRESSIVENESSLOW STATE MEMORYHIGH SPEEDTPLHprototypegroundedplannersmemoise · cache · compile
Figure 10 · No single-axis verdict. TPLH combines lifted semantics and frugal state storage; the future programme is to gain speed without surrendering those reasons for building it.Source scope: interpretive synthesis from Conclusions and Future Work.

Worked example 10 · a fair speed ablation

Compile TPLH, cache progressed states and memoise repeated heuristic subgoals, then rerun situations in identical order. The difference estimates engineering overhead while guidance stays constant.

Causal probe 10 · compare only total time

A slow interpreter can obscure a selective heuristic; fast low-level code can hide wasteful expansions. Reporting both seconds and visited nodes exposes the distinction.

11 · executable laboratory

Search a bounded situation tree without merging histories

This laboratory implements the architecture on transparent synthetic tasks: unit-cost A*, run-time precondition checks, delete-relaxed layer distance and exact prefix executability.

Bounded situation proof searchA tree of action histories coloured by relaxed distance, with the returned proof path highlighted.
Returned proof history:
Search accounting:
Relaxed estimate at S₀:
Final entailed facts:

Door chain has a causal corridor: take key, unlock and enter. Harmless Wave and repeatable Look histories do not advance the relaxed goal frontier. Relevance drives the corridor first.

Distractor workshop requires measuring, cutting and assembly. Polish and Photograph add attractive but irrelevant facts. They never support the goal’s relaxed ancestry.

Consumed resource exposes optimism. Pour creates full; Drink consumes full and creates empty; Refill restores full; Serve needs full and empty. Relaxation imagines full surviving Drink and underestimates restoration.

Every node is keyed by its full action list, never its fact set. The display may contain different histories with equal current facts. That is deliberate situation search, not state deduplication.

The displayed h is minimum relaxed fact-layer distance, simpler than the paper’s recursive supporting-action count. It preserves monotonic add effects and ignored deletes while making every value inspectable. Tests concern the architecture, not a false claim of source-code reproduction.

Worked example 11 · the consumed-resource trap

After Pour then Drink, reality contains empty but not full. Relaxation remembers both and predicts Serve immediately. Exact successor generation refuses it until Refill restores full, so the returned proof remains executable despite optimism.

Causal probe 11 · disable prefix checks

The relaxed sequence could be reported even though Serve’s real precondition fails. Heuristics rank proof obligations; they never replace the BAT’s executability test.

12 · reproduction programme

Separate semantic generality, search quality and implementation cost

A modern replication should preserve the proof-search identity while isolating engineering decisions that made the prototype slow.

First reproduce the STRIPS-compatible subset: conjunctive preconditions, optional negative equality, context-free successor-state axioms, ground conjunctive goals and unit costs. Translate the same IPC instances and record every exclusion producing retained samples.

Log plan length, situations popped, possible-action answers, progression calls, heuristic calls, unique relaxed subproblems, preprocessing, search time, timeout and memory. Domain means need distributions so catastrophic losses cannot conceal majority wins.

Then ablate engineering: compile Prolog; cache progressed states; memoise recursive heuristic values; index precondition predicates; optionally keep a valuation-keyed closed table. Each answers a separate question and should not disappear inside one opaque optimised system.

To test lifting, scale object counts while reachable bindings remain sparse. Compare pre-grounding size, run-time action answers and memory. Include weakly constrained schemas showing where lifted queries only defer explosion.

Finally extend semantics one dimension at a time: incomplete proper-plus initial theories, removal of domain closure, context conditions, arbitrary costs and richer goals. Add soundness tests and compare with contemporary lifted planners, absent from the 2023 experiment and left for future work.

QuestionControlled comparisonRequired evidence
Is h selective?Same code, h versus breadth-first orderExpanded situations and plan length
Where does time go?Memoisation, caching and compilation ablationsProgression, grounding and heuristic time
When does lifting help?Sparse versus weak bindingsGround operators avoided and peak memory
Does generality survive?Incomplete and context-sensitive BATsEntailment oracle and sound plans

Worked example 12 · one-factor memoisation test

Run identical order, bound and tie-breaking before and after caching (relaxed state,subgoal set) estimates. If situations and plans match while heuristic time falls, computation improved rather than guidance.

Causal probe 12 · compare with a recent lifted planner

A fair study aligns expressiveness, costs and grounding assumptions. Without that control, differences may come from language coverage rather than theorem proving itself.

Two comprehensive reviews

What survived formal and evidential challenge

Review one: formal reconstruction. The companion was checked against the twelve-page v3 source. It retains the situation-tree ontology, five BAT components, recursive executability, bounded entailment, Theorem 3’s schema-and-substitution characterisation, Algorithm 1’s A* loop and Algorithms 2–3’s relaxed support logic.

The main risk was collapsing situations into states. The page states that histories never merge while valuations may repeat. A second risk was presenting relaxation as proof or admissible optimal distance. It is guidance only; exact possibility and goal entailment remain authoritative.

Review two: evidence and delivery. Hardware, interpreted-versus-compiled disparity, horizon, cap, preprocessing, retained counts and competitor policies remain attached to claims. Ratios are TPLH divided by comparator, and time per step is never confused with total time or visits.

The favourable result: fewer expansions than Fast Downward in eight domain averages: is paired with PipesWorld, severe runtime cost and no comparison with recent lifted planners. Figures have titles, descriptions and captions. Animation respects reduced motion; the laboratory labels its simplified h and publishes three exact tests.

Review verdict

Pass 1: formal fidelity: passed after distinguishing situation identity from state equality and bounded completeness from unbounded solvability. Pass 2: evidence and accessibility: passed after retaining implementation caveats, sample sizes, competitor policies and the guidance-versus-runtime distinction.

Memory studio

Twelve cards for durable recall

1 · SituationA unique action history rooted at S₀, not merely a fact valuation.
2 · do(a,s)The successor situation after action a occurs in history s.
3 · FluentA relation or function whose value varies with its situation.
4 · BATFoundations, successor states, preconditions, names and initial theory.
5 · ExecutableEvery action is possible at the prefix where it occurs.
6 · Bounded entailmentFind an executable goal situation no longer than N.
7 · Lifted schemaGround variables from current preconditions during search.
8 · ProgressionAdvance initial facts through history to reconstruct Now.
9 · Situation A*Order histories by travelled length plus relaxed distance.
10 · Delete relaxationIgnore negative effects so imagined facts accumulate.
11 · Support recursionChoose actions for goals, union preconditions and work backwards.
12 · Core resultEconomical expansions and short plans coexist with huge overhead.
Place in the canon

From temporal structure to logical proof, representation determines guidance

Paper 0087 deferred timestamps so non-temporal HTN heuristics could rank plans. Paper 0088 moves into logic: histories become proof terms and a planning heuristic ranks them.

Cavrel, Pellier and Fiorino retain temporal constraints while delaying concrete scheduling. Soutchanski and Young retain first-order action semantics while importing relaxed reachability. Both ask what must stay authoritative and what expensive detail may be approximated during search.

A formal representation is not only a language for solutions; it selects the nodes a heuristic sees, duplicates it recognises, computations it repeats and future extensions it can absorb. HTEP nodes are constraint-rich partial plans. TPLH nodes are complete action prefixes with implicit states.

Canon 0089 moves from planning representation to algorithm selection. Moreno-Scott, Ortiz-Bayliss, Terashima-Marín and Conant-Pablos ask whether features of a constraint-satisfaction instance can predict its best heuristic. Guidance shifts up a level: from ranking nodes to choosing who conducts search.

Interpretive synthesis

The proof and the guess should remain visibly different

TPLH assigns two kinds of reasoning different authority. The BAT decides what follows; the heuristic guesses where a short proof may be found.

Relaxation may imagine incompatible achievements, but it cannot certify an action. Progression may be slow, but it supplies exact current facts for precondition queries. The returned situation is sound because every prefix was checked in the theory, not because h was accurate.

Fewer visited situations show that the guess often points well. Comparable plan lengths show useful direction. Slow time per step shows that exact and approximate reasoning are implemented expensively. None cancels the others.

The durable contribution is a clean experimental object: logically grounded, lifted, bounded proof search with a familiar planning heuristic. It lets researchers ask how much modern performance can be recovered without surrendering expressive semantics that specialised grounding simplifies.

Publication brief

Primary source, companion scope and verification contract

This companion reconstructs Mikhail Soutchanski and Ryan Young’s “Planning as Theorem Proving with Heuristics”, arXiv:2303.13638v3 (20 June 2023). It covers situation identity, Basic Action Theories, bounded entailment, lifted grounding, progression, TPLH’s A* loop, delete-relaxed support estimation and comparisons with Fast Downward and BFWS. Figures are original. The laboratory uses synthetic finite STRIPS tasks; it is not a port of ECLiPSe Prolog.

Verification contract. Five orientation claims, ten accessible animated SVG figures, twelve worked examples, twelve causal probes, twelve memory cards, two reviews and three executable exact tests. British English, evidential boundaries, reduced-motion support and responsive design are included.

References

Primary and contextual sources

  1. Soutchanski, M., & Young, R. (2023). “Planning as Theorem Proving with Heuristics.” arXiv:2303.13638v3.
  2. Green, C. C. (1969). “Application of Theorem Proving to Problem Solving.” IJCAI, 219–239.
  3. Reiter, R. (2001). Knowledge in Action. MIT Press.
  4. Fikes, R. E., & Nilsson, N. J. (1971). “STRIPS.” Artificial Intelligence, 2, 189–208.
  5. Hoffmann, J., & Nebel, B. (2001). “The FF Planning System.” JAIR, 14, 253–302.
  6. Helmert, M. (2006). “The Fast Downward Planning System.” JAIR, 26, 191–246.
  7. Bonet, B., & Geffner, H. (2001). “Planning as Heuristic Search.” Artificial Intelligence, 129, 5–33.
  8. Blum, A. L., & Furst, M. L. (1997). “Fast Planning Through Planning Graph Analysis.” Artificial Intelligence, 90, 281–300.