Intelligence, Agency & Consciousness · Paper 0087

When time is assigned after structure

Cavrel, Pellier and Fiorino ask whether temporal HTN planning can borrow guidance from a simpler world: refine hierarchy and causal structure as instantaneous events, then let a constraint solver restore the clock.

Intelligence, Agency & Consciousness · Paper 0087

When time is assigned after structure

Rajesh Ranjan Mahapatra

Cavrel, Pellier and Fiorino ask whether temporal HTN planning can borrow guidance from a simpler world: refine hierarchy and causal structure as instantaneous events, then let a constraint solver restore the clock.

© 2026 Rajesh Ranjan Mahapatra. 29 min read

When time is assigned after structureAll AI Research Library

TLDR

Five-point orientation
  1. Separate structure from timestamps. HTEP searches a relaxed partial-order causal-link plan, then asks a CSP to assign times satisfying the accumulated temporal constraints.
  2. Compile duration into events. A durative action becomes start and end snap actions, an exact-duration constraint and causal links protecting its invariants.
  3. Repair four kinds of flaw. Open preconditions, causal threats, abstract decompositions and unresolved durative tasks drive plan refinement.
  4. Reuse non-temporal guidance. Task-decomposition-graph and FAPE-style estimates rank partial plans while one common flaw-selection policy controls the comparison.
  5. Speed trades against expressiveness. HTEP scores better on solving time in the tested domains, while chronicles usually lead on makespan and alone cover necessary concurrency.
01 · the planning gap

Hierarchy says what may unfold; time says when it may coexist

Temporal HTN planning combines two sources of structure that are individually difficult: abstract tasks decompose into networks of subtasks, while durative actions impose relations among start points, end points, conditions and effects.

Classical STRIPS planning searches over actions that change a state. Hierarchical Task Network planning adds abstract tasks and methods. A method does not execute; it explains how an abstract task can be replaced by a network of lower-level tasks subject to ordering constraints. The hierarchy can carry domain knowledge that makes otherwise huge searches tractable.

Time complicates the object. Every non-instantaneous action has a start and an end. Preconditions may be required at the start, the end or throughout an interval. Effects occur at particular endpoints. Actions may overlap, and overlap may be optional, beneficial or logically necessary.

The authors organise this expressiveness using Cushing’s three categories. Category one admits only sequential solution plans. Category two permits concurrency but also admits at least one sequential plan. Category three contains problems for which every valid solution requires concurrency. A planner that serialises all action interactions can address the first two categories but not the third.

Chronicle planners keep temporally indexed proposition values and refine constraint-rich timelines. They are expressive, including for necessary concurrency, but heuristic guidance can be weak because each partial object already carries substantial temporal machinery. State-space compilations can use mature classical heuristics, yet often restrict the solution language.

HTEP seeks an intermediate point. It keeps a flexible plan-space representation and temporal constraints, but conducts the structural search through non-temporal snap actions and POCL flaws. Only when a partial plan has no unresolved flaws does a CSP solver find timestamp assignments. The research question is whether this relaxation exposes useful non-temporal HTN guidance without destroying too much temporal meaning.

HTN decomposition meets a temporal scheduleAn abstract mission decomposes into move, scan and transmit tasks above a timeline where move and calibrate overlap before scan.SURVEY REGIONMOVESCANTRANSMITmovecalibratescantransmithierarchy constrains refinement · time constrains coexistence
Figure 1 · One plan, two structures. A decomposition explains which tasks realise the mission; a schedule explains how their intervals can coexist.Source scope: primary paper, Introduction and Problem Statement.

Worked example 1 · an optional overlap

A rover can move for four minutes while its antenna calibrates for two. Both must finish before a three-minute scan. A sequential schedule takes nine minutes before scanning ends; a partial order allows calibration under the move and ends the scan at minute seven.

Causal probe 1 · erase the hierarchy

The same primitive actions may still form a valid schedule, but search loses the method’s knowledge about which task combinations realise “survey region”. Temporal reasoning survives while domain-guided refinement branches far more widely.

02 · formal objects

Tasks name obligations; snap actions alone change the world

The paper distinguishes three task kinds and gives every task a start and end variable, even when the task is abstract and has no fixed duration of its own.

A snap action is a classical action tuple: a name, a set of preconditions and positive or negative effects. It occurs at one time point, so its start and end coincide. Preconditions hold strictly before that point; effects hold afterwards. A snap action refines a task when their names match.

A durative action contains named start and end snap actions, a set of invariant propositions and a strictly positive duration d. Its start and end variables satisfy vend−vstart=d. The invariant must hold after the start event and until the beginning of the end event: the open interval between them.

An abstract task does not itself alter the state. A method maps it to a set of subtask symbols and qualitative temporal constraints among their start and end points. The point-algebra relations admitted include <, ≤, >, ≥, = and ≠. The parent’s bounds enclose the starts and ends of its children during refinement.

A partial temporal plan is π=(T, α, C, L): task symbols T; a mapping α from symbols to task names; temporal ordering constraints C; and causal links L. A causal link ti: p→ tj says the provider’s effect p supports the needer’s precondition p, with ti ordered before tj.

The initial partial plan contains two special snap actions. t₀ has the initial state as effects and no preconditions. t∞ has the goal as preconditions and no effects. Search refines everything between them until every task is a snap action, every precondition is supported, every threat is resolved and every time variable receives a consistent value.

π = (T, α, C, L)
solution ⇔ all tasks are snap actions
∧ no open preconditions
∧ no causal threats
∧ timestamps satisfy C
The four components of a partial temporal planTask symbols, task-name mapping, temporal constraints and causal links occupy four connected panels around a plan symbol.πpartial planT · TASK SYMBOLSinstances in the planα · NAME MAPPINGsymbol → task kindC · TIME CONSTRAINTSstart/end relationsL · CAUSAL LINKSprovider: p→ needer
Figure 2 · Structure is explicit and revisable. Refinement changes tasks and constraints while causal links record why a precondition is protected.Source scope: primary paper, “Action, Methods, Tasks and Plan”.

Worked example 2 · a complete partial plan

For t₀→Move→Scan→t∞, T contains four symbols, α names their snap actions, C orders their endpoints, and L links “at-site” from Move to Scan and “image” from Scan to t∞. If no action can delete either protected fact in between, the structure is flaw-free.

Causal probe 2 · keep ordering but remove causal links

The schedule can still say Move precedes Scan, yet it no longer states which fact makes Scan executable or which intervening deletion would threaten it. Temporal feasibility is not causal adequacy.

03 · method refinement

An abstract task disappears, but its temporal envelope remains

Applying a method replaces one abstract symbol with its subtasks, extends the name mapping and merges the method’s temporal constraints into the partial plan.

Suppose method m refines abstract task t. The refined task set removes t and inserts the method’s subtask symbols. The new mapping keeps every old symbol except t and adds the method’s symbol-to-name assignments. Existing causal links remain; later search must support any new open preconditions.

The constraint set gains all method constraints. It also connects the parent interval to each child: the parent start is no later than every child start, and the parent end is no earlier than every child end. A start-before-end relation is kept for the parent boundary. The abstract symbol can therefore remain as a temporal envelope even though its executable content has been replaced.

This is plan-space refinement rather than forward execution. Search does not commit to one total order or simulate a single state after every step. It accumulates only those orderings needed by the method, causal support, threat repair and temporal consistency.

Different methods create branches. “Survey” might decompose into Move, Calibrate, Scan and Transmit, or into Move, QuickScan and Return. Plan-selection heuristics rank the resulting partial plans. Flaw selection then chooses which unresolved obligation inside the chosen plan to repair next.

Hierarchy often supplies useful ordering that a chronicle solver would otherwise derive from richer temporal constraints. This helps explain the paper’s empirical observation: although a chronicle can reject some temporally impossible partial refinements earlier, many benchmark failures arise from non-temporal flaws, and HTN methods already encode much of the necessary order.

Method refinement replaces an abstract task with constrained subtasksA Survey task on the left opens into Move, Scan and Report subtasks on the right, all bounded by the original task's start and end.SURVEYabstract task tparent temporal envelopeMOVESCANREPORT
Figure 3 · Refinement adds detail without forcing a total schedule. The method introduces tasks and relations while the parent supplies an enclosing temporal boundary.Source scope: primary paper, method-refinement equations.

Worked example 3 · two legal decompositions

A “deliver data” task has a reliable method: compress, transmit, verify: and a fast method: transmit raw. Refinement creates two partial plans. Neither has timestamps yet; the heuristic can prefer the branch estimated to require fewer remaining modifications.

Causal probe 3 · force every sibling into a total order

Search becomes simpler but optional concurrency disappears. A method saying only that Move and Calibrate precede Scan should not invent an order between Move and Calibrate; preserving that freedom can improve makespan.

04 · temporal-event compilation

A duration becomes two instantaneous decisions and a protected interval

HTEP’s signature translation replaces a durative action with start and end snap actions, then carries the duration and invariant as constraints that survive the non-temporal search.

For durative action a, the task symbol is replaced by vsa and vea, mapped to start(a) and end(a). The constraint set gains vsa<vea and vea−vsa=d. These are retained for the timestamp CSP.

The invariant propositions are added to the preconditions of both endpoint actions in the authors’ compilation. For each invariant p, a causal link start(a): p→end(a) protects p over the interior. Any snap action that deletes p and could fall between the endpoints becomes a causal threat.

Threat resolution orders the deleter before the start or after the end. In this way a familiar POCL mechanism guards a temporal interval. The structural search can reason with provider, needer and threat relations without continuously solving a complete chronicle.

The relaxation is not an erasure of time. Exact duration constraints, method relations and added ordering constraints accumulate in C, and consistency is checked during refinement. At a flaw-free candidate, a CSP assigns all temporal variables. A structurally valid branch with no timestamp solution is rejected.

Yet the placement of invariants creates the expressiveness boundary. For necessary concurrency, an invariant may need to become true immediately after the start event through another concurrent action. Treating it as a precondition of start requires it too early. The compilation can therefore exclude valid category-three plans.

A durative action compiles into start and end snap eventsA six-unit Observe action becomes start and end circles joined by an invariant causal link and an exact duration constraint.OBSERVEduration d = 6STARTpre + invariantENDpre + invariantstablevᵉ − vˢ = 6two events · one protected interval
Figure 4 · Time is deferred, not discarded. Endpoint actions enter POCL search while duration and invariant constraints remain available to the temporal solver.Source scope: primary paper, Figure 1 and durative-refinement equations.

Worked example 4 · protect “stable” during observation

Observe lasts six units and requires stable throughout. Compilation creates Observe-start and Observe-end, fixes their separation to six and links them with stable. A Reset action deleting stable must be promoted before start or demoted after end.

Causal probe 4 · keep endpoint preconditions but remove the causal link

Stable may hold at both endpoints while a deleter slips into the interval and another action restores it before the end. The endpoint test passes even though the invariant was violated; the protected link is essential.

05 · the four flaws

Search advances by repairing one explicit defect at a time

POCL planning turns incompleteness into a typed agenda. HTEP inherits open conditions and causal threats, then adds unresolved abstract and durative tasks as temporal-hierarchical flaws.

An open-precondition flaw occurs when a snap action requires p but no causal link supports it. A repair selects a preceding snap action that produces p and adds the link and necessary order. Existing actions can be reused when consistent.

A causal-threat flaw occurs when an action deletes p and remains unordered with respect to a link protecting p from provider to needer. The repair either promotes the threat before the provider or demotes it after the needer, provided the new temporal constraints remain consistent.

A decomposition flaw is an abstract task still awaiting a method. Each applicable method supplies a possible repair and branches the plan space. The resulting subtasks may themselves be abstract or durative, so one repair can introduce several future flaws.

A durative flaw is a durative action still represented as an unresolved task. Repair compiles it into start and end snap actions, adds exact-duration constraints and installs invariant causal links. The structural plan grows while temporal commitments remain partial.

Every flaw must eventually disappear, but order affects effort. A flaw with one possible resolver is attractive because failure is discovered without expanding several branches. The FAPE-inspired policy refines least-cost flaw repair by prioritising unresolved tasks and preconditions, giving the search hierarchy and causality early attention.

Four flaw types and their repairsFour coloured quadrants show an open precondition repaired by a causal link, a threat repaired by ordering, an abstract task repaired by a method and a duration repaired by endpoint compilation.OPEN PRECONDITIONfind provider: p→ neederCAUSAL THREATorder deleter outside linkDECOMPOSITIONapply one matching methodDURATIVE TASKcreate start/end events
Figure 5 · Refinement is flaw repair. Each repair changes a partial plan while preserving the possibility of later causal and temporal completion.Source scope: primary paper, “Temporal Flaws” and Figure 2.

Worked example 5 · one repair creates two more

Decomposing “collect sample” introduces a durative Drill task and an Analyse action needing “sample-ready”. The method flaw vanishes; a durative flaw and an open precondition appear. Progress is not fewer flaws at every step but greater executable detail.

Causal probe 5 · resolve the first flaw listed

Completeness can remain, yet branching can explode if an easy-looking flaw has many resolvers. Selecting a flaw with few alternatives exposes forced failures earlier and reduces the number of partial plans placed on the open list.

06 · the HTEP loop

Choose a partial plan, choose a flaw, and postpone the clock until structure closes

HTEP alternates non-deterministic plan selection with deterministic flaw selection. A candidate becomes a solution only after its structural flaws vanish and a temporal assignment exists.

The initial plan π₀, bounded by t₀ and t∞, enters an open list. A plan-selection heuristic chooses which partial plan to explore. HTEP computes its flaws. If any remain, the flaw-selection heuristic chooses one and every consistent repair produces a successor plan added to open.

If no flaws remain, HTEP asks a CSP solver for values of all time variables satisfying C. A successful assignment returns the partial plan and timestamps. If the CSP fails, that structurally complete candidate is discarded and search continues with another plan.

The separation creates two decision layers. Plan selection controls which branch of the refinement tree receives attention, directly affecting performance and which solution quality is reached first. Flaw selection controls local branching within the chosen plan. Because every flaw must eventually be repaired, the authors say admissibility depends on plan selection, while flaw order still strongly affects runtime.

Constraint consistency is not necessarily postponed entirely to the leaf. Qualitative temporal constraints can be checked through the associated constraint graph; the paper notes polynomial-time consistency checking through strongly connected components for the relation set it defines. The final CSP nevertheless supplies concrete timestamps.

Failure of open means no solution exists within HTEP’s representation and search policy assumptions. It does not prove that a category-three plan is impossible in the original temporal domain, because compilation may have removed necessarily concurrent solutions before search began.

The HTEP search loopAn open list feeds plan selection, flaw detection and repair; flaw-free plans go to a timestamp CSP that either returns a solution or resumes search.OPEN LISTSELECTPLANCOMPUTEFLAWSREPAIR ONEFLAWTIMESTAMPCSPflawsnonestructure closes first · concrete time validates last
Figure 6 · A relaxed search with a temporal gate. Non-temporal heuristics guide plan refinement; the candidate still needs a consistent timestamp assignment.Source scope: primary paper, Algorithm 1.

Worked example 6 · structurally complete, temporally impossible

A branch supports every precondition and resolves every threat, but requires B after A, A after B and positive duration for both. Its flaw set is empty under causal inspection; the temporal constraints have no assignment, so the CSP rejects it.

Causal probe 6 · invoke the CSP after every repair

Earlier temporal rejection may shrink search, but repeated solving can dominate. HTEP’s design choice is an economic one: exploit cheap structural guidance and consistency checks, paying for a full assignment only when a candidate closes.

07 · borrowed guidance

A non-temporal heuristic can rank temporal partial plans

Once durative tasks have been expressed as snap events, HTEP can evaluate candidate plans with heuristics designed for hybrid or non-temporal HTN search. The wager is that hierarchy and unresolved causal structure predict enough of the remaining effort.

A plan-selection heuristic chooses among partial plans in open. The most elementary POCL signal is the number of open conditions. Task Decomposition Graphs enrich that signal by summarising which tasks and conditions must eventually appear under possible method refinements.

The paper describes hTC as the cardinality of mandatory tasks expected in the decomposition and combines it with the number of flaws, producing h#F+TC. It also describes hMME, an estimate of modifications needed to reach a solution, and hTDGm, a refinement that accounts for causal links already introduced.

A third plan score, hFAPE, is taken from the FAPE chronicle planner and estimates remaining effort. Using it in both the temporal-event and chronicle representations creates the most direct representational comparison: HTEP+hFAPE and Chr+hFAPE differ principally in the constraints their search states carry.

Flaw selection is held common across the experimental configurations: the FAPE policy, described as a refinement of least-cost flaw repair. LCFR prioritises flaws with the fewest resolvers. FAPE’s ordering additionally gives priority to unrefined tasks and preconditions. This control matters because a different flaw policy could overwhelm the effect of plan scoring.

The article’s notation is not perfectly stable. The prose first defines h#F+TC, while the experimental configuration is printed as h#F+PC and the small figure label appears to contain an additional term. A faithful reading should flag that editorial ambiguity rather than invent a definition for the changed letters. The robust claim is about the flaw/task-decomposition-count family.

Plan selection and flaw selection operate at different levelsThree partial plans are ranked by estimated remaining effort, then one chosen plan exposes four flaws and the flaw with fewest resolvers is selected.PLAN SELECTIONπ₁estimate 14π₂estimate 7π₃estimate 11FLAW SELECTION INSIDE π₂open p4 repairsthreat2 repairsduration1 repairmethod3 repairswhich plan next? · which defect inside it?
Figure 7 · Two selectors, two branching decisions. Plan scores allocate global attention; flaw policy chooses the next local repair.Source scope: primary paper, “Partial Order Planning heuristics”.

Worked example 7 · equal flaws, unequal future work

Two partial plans each contain three visible flaws. A task-decomposition graph shows that π₁ must introduce nine additional tasks while π₂ must introduce two. Counting only present flaws ties them; hTDGm can prefer π₂ because it estimates refinement still hidden by hierarchy.

Causal probe 7 · give each configuration a different flaw policy

A faster HTEP run could then come from resolving forced flaws earlier rather than from the temporal-event representation or plan heuristic. Holding flaw selection and the CSP solver constant makes the comparison more diagnostic.

08 · experimental contract

Four representations and heuristics enter the same bounded arena

The experiment compares three HTEP configurations with a chronicle configuration over four temporal HTN domains, using common infrastructure and two IPC-scored outcomes.

The configurations are HTEP+hTDGm, HTEP with the flaw/task-count TDG family, HTEP+hFAPE, and Chr+hFAPE. The chronicle planner is encoded to mimic FAPE’s behaviour. All use the same FAPE-derived flaw-selection heuristic and the same CSP solver, reducing implementation asymmetry.

Problems are written in HDDL 2.1. Gripper is category one and sequential. Satellite is also category one but offers different sequential makespans. Rover is category two: concurrent solutions may improve duration, yet a sequential solution exists. Area Scan permits extensive cooperation and optional concurrency. No category-three benchmark appears because HTEP’s compilation cannot represent necessary concurrency.

Runs use one core of an Intel Core i7-9850H, at most 8 GB of RAM and a 600-second limit. Solving time covers instantiation through solution. Makespan is the time from the initial state to the final task endpoint. Both are converted to International Planning Competition-style scores, so larger bars mean better relative performance rather than raw seconds or raw plan length.

The prose says “three indicators” but lists solving time and makespan, two items. Figure 3’s caption says “five configurations” although the text enumerates and the chart displays four. These appear to be editorial slips. They do not justify creating a hidden metric or planner; a careful reconstruction keeps the observable design at two measures and four configurations.

The paper states that code and benchmarks would be made freely available if accepted. That statement is a reproducibility intention, not evidence in this reconstruction that an archived release was inspected. The present companion therefore assesses the reported design and figure without claiming an independent rerun.

The experimental matrix crosses four configurations with four domainsA grid shows three HTEP heuristics and one chronicle baseline across Gripper, Satellite, Rover and Area Scan, with common hardware and limits below.HTEP + TDGmHTEP + countHTEP + FAPEChronicle + FAPEGRIPPER · C1SATELLITE · C1ROVER · C2AREA SCAN · C2one core · i7-9850H · 8 GB · 600 s · IPC time and makespan scores
Figure 8 · Controlled comparison, bounded scope. Common flaw selection and CSP infrastructure help isolate plan representation and plan-selection guidance.Source scope: primary paper, Experimental Setup and Figure 3.

Worked example 8 · what an IPC score conceals

A time score of 0.9 says a configuration is close to the best observed solver on that instance set; it does not say the run took 0.9 seconds. Reading chart height as raw time would invert the meaning, because higher is better after scoring.

Causal probe 8 · add a necessary-concurrency benchmark

The chronicle planner may solve it while every HTEP configuration fails representationally. Average performance would then mix search efficiency with language coverage, making the boundary visible but changing the experiment’s question.

09 · what the figure supports

Temporal events win the time score; chronicles usually protect makespan

The chart reveals a consistent efficiency-quality tension. HTEP’s simpler structural search finds solutions quickly, while the chronicle representation can use full temporal information to choose shorter schedules among equally ranked candidates.

Across every domain and compared under hFAPE, HTEP’s solving-time score exceeds the chronicle counterpart. The authors attribute this to simpler non-temporal constraints and flaws. A chronicle can reject temporally impossible refinements earlier, but in these HTN domains method structure supplies much of the necessary order and non-temporal flaws dominate rejection.

The two classical HTN-guided HTEP configurations are the strongest time performers across the plotted domains. The flaw/task-count family is especially strong on Rover, while hTDGm leads on the others. The authors emphasise that heuristic informativeness depends on the domain definition; there is no globally dominant formula independent of modelling choices.

For makespan, Chr+hFAPE is generally strongest. Its fuller temporal representation can break ties between plans of equal heuristic value by preferring the schedule with better makespan. HTEP remains competitive in several domains, so the relaxation does not automatically force serial plans.

Rover exposes the cost of using refinement effort as a surrogate for temporal quality. HTEP+hTDGm has the weakest makespan score there because it seeks a plan requiring fewer refinements regardless of resulting duration. A structurally economical plan can schedule poorly.

Area Scan needs special caution. The paper notes that one configuration’s apparently superior makespan score is partly caused by other configurations failing to solve some instances, which changes the score aggregation. Coverage and quality are entangled. A complete comparison should publish per-instance solving, raw time, raw makespan and coverage beside aggregate scores.

Representation trades solving speed against makespan guidanceTwo scales compare temporal-event plans, high on solving efficiency, with chronicles, high on temporal quality and expressiveness.TEMPORAL EVENTSsimpler search · stronger time scoreCHRONICLESfuller time · stronger makespanthe benchmark chooses where the balance settles
Figure 9 · Faster refinement is not the same objective as shorter execution. HTEP and chronicles expose different information to the heuristic, so they favour different outcomes.Source scope: primary paper, Results and Discussion.
Reported patternMechanistic readingFairness condition
HTEP beats chronicle on time scoreFewer and simpler temporal constraints during structural refinementSame CSP and flaw policy; tested categories one and two only
Classical HTN scores lead HTEPTask-decomposition guidance predicts dominant non-temporal workHeuristic success depends on domain encoding
Chronicle leads makespanFull temporal state informs tie-breaking and plan qualityAggregate scores should be read with coverage
Rover punishes TDGm qualityFew refinements need not imply a short scheduleTime and makespan are separate objectives

Worked example 9 · fewer refinements, longer mission

Method A expands into three long actions and Method B into five short actions with overlap. A modification-count heuristic prefers A, but B has lower makespan. The heuristic correctly estimates its own structural target while misranking the temporal objective.

Causal probe 9 · tie-break HTEP with temporal lower bounds

A cheap critical-path estimate could distinguish structurally equal plans without installing a full chronicle in every node. The experiment suggests this hybrid direction, but does not test it; it remains a proposed extension, not a reported result.

10 · the expressiveness boundary

An invariant needed after start cannot always be required before start

HTEP’s causal-link compilation protects an invariant once present, but requiring that invariant as a start precondition rules out problems where another action must establish it concurrently after the protected action begins.

In category one, only sequential solutions exist. The compilation is well aligned with the domain because every required relation can be realised without overlap. In category two, overlap may shorten the plan but serial execution remains possible. HTEP can still find a solution and may preserve useful optional concurrency through partial order.

Category three is different. Some temporal condition forces overlap: no sequential plan exists. Cushing’s examples show why endpoint-only compilations are delicate. An invariant is semantically required just after the start, not necessarily strictly before it. Another action beginning at the same time may establish the condition in the interval.

HTEP adds the invariant to the start event’s preconditions. The provider must therefore precede the start under POCL causality. If the domain requires the provider to begin only after or simultaneously with that start, the compiled problem becomes inconsistent although the original temporal problem has a valid necessarily concurrent schedule.

This is not a bug discovered by the companion; it is the limitation named in the paper’s Discussion and Conclusion. The authors propose improving compilation to admit the third category. Until then, “temporal HTN planner” should be qualified: HTEP produces partial temporal plans for the first two categories represented by its compilation.

The boundary explains part of the speed advantage. A representation that excludes some interactions can search fewer possibilities and use cheaper heuristics. Efficiency and expressiveness are not independent axes; the experiment compares methods over the shared fragment, not over the entire language available to chronicles.

Cushing's three concurrency categories and HTEP coverageThree nested regions show sequential-only, optionally concurrent and necessarily concurrent problems; HTEP covers the first two while chronicles extend through the third.CATEGORY 3 · CONCURRENCY NECESSARYCATEGORY 2 · CONCURRENCY OPTIONALCATEGORY 1solutions are sequentialHTEP coverage ← categories 1–2 · chronicle coverage ← categories 1–3
Figure 10 · The shared benchmark fragment is not the whole temporal language. HTEP’s relaxation buys guidance inside categories one and two; the chronicle baseline retains necessary concurrency.Source scope: primary paper, Introduction, Discussion and Conclusion; Cushing 2007.

Worked example 10 · condition established just after start

Action Heat begins, and only then can Action Stabilise establish pressure needed throughout Heat’s interior. The temporal semantics admits simultaneous starts with pressure true immediately afterwards. A compilation demanding pressure before Heat-start rejects the only valid pattern.

Causal probe 10 · add category three without changing compilation

More search or a stronger heuristic cannot recover solutions removed by representation. The repair must change when and how invariant support is expressed, not merely which partial plan is explored first.

11 · executable temporal-event laboratory

Compile intervals, honour precedence and protect invariants

The laboratory turns three tiny HTN-style task networks into start/end events, computes an earliest feasible schedule under optional extra ordering, and audits the exact properties HTEP’s final candidate must satisfy.

Temporal-event scheduleDurative tasks rendered as scheduled bars, with start and end events and protected invariant intervals.
Compiled events:
Makespan:
Temporal constraints:
Protected facts:

Gripper-style sequence orders Carry before Drop. Its schedule is category one: added serialisation changes nothing because the task order is already total.

Rover optional concurrency lets Move and Calibrate begin together, requires both before Scan, and requires Scan before Transmit. The earliest partial order overlaps the independent tasks. Safe serialisation remains valid but increases makespan, modelling a category-two choice.

Protected invariant places Reset before Observe and Archive afterwards. Reset deletes the fact stable, but its endpoint occurs outside Observe’s protected interval. The causal-threat audit therefore passes. Moving Reset inside would be a flaw requiring promotion or demotion.

The scheduler is an exact longest-path oracle for these acyclic precedence networks, not the historical planner. HTEP permits general point-algebra relations and delegates timestamp assignment to a CSP. The artefact isolates the paper’s core separation: a structural task network becomes event pairs, then receives a concrete time assignment.

Worked example 11 · optional concurrency saves two units

In the Rover network, Move lasts four and Calibrate lasts two. Running them together lets Scan start at four. A safe serial policy places Calibrate after Move, so Scan starts at six. Both schedules satisfy the same causal requirements; only makespan differs.

Causal probe 11 · add one-unit gaps

Every precedence edge gains slack. The exact duration of each action is unchanged, every invariant remains protected, and makespan rises. This separates action duration from scheduling policy and shows why timestamp choices affect quality after structure is fixed.

12 · reproduction and interpretation

Preserve the representation, the controls and the missing denominators

A modern rerun should distinguish three hypotheses: temporal-event states are cheaper, classical HTN scores guide them better, and that advantage remains after accounting for solution quality and representational coverage.

Implement the formal objects exactly: snap, durative and abstract tasks; start and end variables; method constraints; the partial-plan tuple; causal links; threat semantics; and the two special boundary actions. Check that method refinement preserves parent bounds and that durative refinement adds both exact duration and invariant protection.

Reproduce the four visible configurations with the same CSP solver, grounding, open-list policy, FAPE flaw selection and stopping limits. Resolve the paper’s h#F+TC/h#F+PC notation from source code or author clarification before naming a fifth formula. Do not infer a fifth configuration from the figure caption.

Publish raw per-instance wall time, instantiation time, search nodes, CSP calls, coverage, makespan and IPC score. Report timeout and memory censoring. Aggregate quality only over a clearly stated common solved set, or show coverage alongside the conditional quality score so failure cannot improve the apparent average.

Include category-three tasks as a separate expressiveness suite. Failure there is expected under the published compilation and should not be blended anonymously with search time. For categories one and two, include method encodings with strong and weak ordering knowledge to test the authors’ explanation that hierarchy supplies temporal constraints before chronicles can exploit them.

Finally, ablate the representation and heuristic independently: HTEP and chronicle under hFAPE; multiple plan scores inside HTEP; and temporal lower-bound tie-breaking added to HTEP. This factorial design reveals whether speed comes from cheaper nodes, better ranking, narrower expressiveness or their interaction.

Audit itemRequired evidenceFailure mode
Formal fidelityEndpoint, duration, method-envelope and invariant testsA relaxed plan is mistaken for a temporally executable plan
Search fairnessCommon CSP, flaw policy, grounding and resource capImplementation differences masquerade as representation effects
Quality fairnessCoverage and common-instance makespanUnsolved cases disappear from an attractive aggregate
ExpressivenessCushing category reported per domainNecessary-concurrency failure is called poor heuristic search

Worked example 12 · a clean representation ablation

Run HTEP+hFAPE and Chr+hFAPE with identical flaw ordering, CSP and limits. Node-processing time and rejection depth then reveal what representation changes. Compare HTEP heuristics separately to measure guidance.

Causal probe 12 · report only solved-instance makespan

A configuration solving one easy problem could appear perfect. Adding coverage and a shared-instance analysis prevents selection by success from being mistaken for generally better temporal quality.

Two comprehensive reviews

What survived formal and evidential challenge

Review one: scholarly fidelity and teaching. The reconstruction was checked against the seven-page primary source page by page. It preserves the three task kinds, the partial-plan tuple, the two refinement equations, four flaw types, open-list algorithm, two-stage structural/temporal logic and the category-three limitation. Each diagram is a new explanatory abstraction rather than a reproduction.

The main teaching risk was saying that HTEP “removes time”. It does not: duration and ordering constraints remain, consistency is checked and a timestamp CSP gates success. The page therefore uses “relaxation” and “defer concrete assignment”, and repeatedly distinguishes POCL causal closure from temporal executability.

Review two: evidence, language and accessibility. The empirical claims were limited to the four plotted configurations and four domains, with hardware, resource cap and IPC interpretation retained. The article’s “three indicators”/two-item list and “five configurations”/four-item chart inconsistencies are disclosed. No raw numerical value is reverse-engineered from chart pixels.

The strongest headline: HTEP outperforms chronicles on solving time: is paired with the chronicle makespan advantage, Rover exception, Area Scan coverage caveat and missing category-three tests. Prose was checked for inflated certainty and generic AI transitions. Figures have titles, descriptions and captions; controls are labelled; animation honours reduced-motion preferences; the laboratory publishes exact invariant tests.

Review verdict

Pass 1: formal reconstruction: passed after clarifying that time is retained as constraints and separating constraint consistency from final timestamp assignment. Pass 2: evidence and delivery: passed after retaining notation/caption irregularities, coverage caveats, expressiveness limits and the efficiency-quality trade-off.

Memory studio

Twelve cards for durable recall

1 · HTNAbstract tasks branch into method-constrained subtask networks.
2 · Snap actionAn instantaneous state-changing action at one time point.
3 · Durative actionStart and end snaps, a positive duration and interval invariants.
4 · Partial planTasks, name mapping, temporal constraints and causal links.
5 · Causal linkA provider protects proposition p until a needer uses it.
6 · ThreatAn unordered action can delete the proposition inside a link.
7 · CompilationReplace a duration with event endpoints while retaining time constraints.
8 · Plan selectionChoose which partial plan in open receives the next refinement.
9 · Flaw selectionChoose which local defect inside that plan is repaired next.
10 · TDG guidanceEstimate tasks and modifications hidden beneath unresolved hierarchy.
11 · Timestamp CSPA flaw-free structure succeeds only if its time variables can be assigned.
12 · BoundaryRequiring invariants before start excludes necessary concurrency.
Place in the canon

From causal explanations inside Graphplan to guidance across temporal representations

Paper 0086 asked how a search procedure can learn which constraints caused failure. Paper 0087 asks a complementary architectural question: which representation should expose a search state to the heuristic in the first place?

Kambhampati’s dynamic-CSP reading of Graphplan translated planning extraction into a neighbouring formalism so that explanation-based learning and dependency-directed backtracking could be imported. Cavrel, Pellier and Fiorino likewise translate temporal HTN planning into event-based POCL structure so that non-temporal HTN heuristics can guide refinement.

Both papers treat representation as computational leverage. In Graphplan, smaller causal no-goods prune future branches. In HTEP, a relaxed structural state is cheaper to rank than a full chronicle. In both, the gain is bounded by what the abstraction omits: coupled causes limit memo generality, while necessary concurrency limits event compilation.

Canon 0088, Soutchanski and Young’s “Planning as Theorem Proving with Heuristics”, moves the translation again: this time into proof search. The sequence therefore traces a general research strategy: recast planning in a formal system with mature guidance, then audit whether the imported heuristic respects the original problem’s semantics.

Interpretive synthesis

A useful relaxation postpones expensive detail without losing the right failures

HTEP’s design can be read as staged commitment. Hierarchy and causality decide what must exist; temporal constraints preserve what must coexist; concrete timestamps arrive only after the structural obligations close.

This architecture works when the relaxed state contains signals correlated with final feasibility. The experiments suggest that in the selected HTN domains, method knowledge and non-temporal flaws do most of the discriminating work. Classical HTN heuristics can therefore direct search before full temporal structure earns its cost.

The trade-off is asymmetric. A chronicle remembers more and can improve makespan or express necessary concurrency, but pays for a richer search object. HTEP remembers less and searches faster, but no heuristic can recover schedules the compilation cannot express. Relaxation is a hypothesis about which details can safely wait.

The enduring lesson is not that time should always be postponed. It is to locate the earliest representation that preserves the causes of failure relevant to the objective. For time-to-first-plan in categories one and two, temporal events may suffice. For optimal makespan or required overlap, temporal information must enter guidance earlier.

Publication brief

Primary source, companion scope and verification contract

This companion reconstructs Nicolas Cavrel, Damien Pellier and Humbert Fiorino’s “On Guiding Search in HTN Temporal Planning with non Temporal Heuristics”, presented at the ICAPS Hierarchical Planning Workshop in 2023 and archived as arXiv:2306.07638. It focuses on formal task semantics, temporal-event compilation, POCL flaw repair, plan and flaw selection, the four-domain comparison and the explicit necessary-concurrency boundary. The figures are original explanatory graphics. The laboratory uses synthetic acyclic task networks to test endpoint compilation, precedence and invariant protection; it is not a runtime reproduction of HTEP.

Verification contract. The page contains five orientation claims, ten accessible animated SVG figures, twelve worked examples, twelve causal probes, twelve memory cards, two distinct reviews and three executable exact tests. It uses British English, labels evidential boundaries, respects reduced-motion preferences and is designed for desktop, tablet and mobile widths.

References

Primary and contextual sources

  1. Cavrel, N., Pellier, D., & Fiorino, H. (2023). “On Guiding Search in HTN Temporal Planning with non Temporal Heuristics.” 6th ICAPS Workshop on Hierarchical Planning. arXiv:2306.07638.
  2. Pellier, D., Albore, A., Fiorino, H., & Bailon-Ruiz, R. (2023). “HDDL 2.1: Towards Defining an HTN Formalism with Time.” HPlan 2023. arXiv:2206.01822.
  3. Bit-Monnot, A., Ghallab, M., Ingrand, F., & Smith, D. E. (2020). “FAPE: a Constraint-based Planner for Generative and Hierarchical Temporal Planning.” arXiv:2010.13121.
  4. Cushing, W. (2007). “Evaluating Temporal Planning Domains.” ICAPS, 105–112.
  5. Bercher, P., Keen, S., & Biundo, S. (2014). “Hybrid Planning Heuristics Based on Task Decomposition Graphs.” SoCS.
  6. Bercher, P., Behnke, G., Höller, D., & Biundo, S. (2017). “An Admissible HTN Planning Heuristic.” IJCAI, 480–488.
  7. Dechter, R., Meiri, I., & Pearl, J. (1991). “Temporal Constraint Networks.” Artificial Intelligence, 49, 61–95.
  8. Younes, H. L. S., & Simmons, R. G. (2003). “VHPOP: Versatile Heuristic Partial Order Planner.” JAIR, 20, 405–430.
  9. Höller, D., et al. (2020). “HDDL: An Extension to PDDL for Expressing Hierarchical Planning Problems.” AAAI, 9883–9891.