In automated planning, a landmark is a proposition (a fact about the world) that must be true at some point in every valid plan that solves a given problem. Landmarks are derived from the structure of the planning domain and problem instance, not from a single plan. They represent necessary stepping stones between the initial state and the goal. Identifying landmarks allows planners to impose ordering constraints on actions and to create powerful, informed heuristic functions that dramatically improve search efficiency by estimating the minimum number of actions needed to achieve all required facts.
Glossary
Landmark (in Planning)

What is a Landmark (in Planning)?
A formal definition of a landmark in the context of automated planning and heuristic search.
Landmarks are categorized as fact landmarks (single propositions) or action landmarks (actions that must occur). They can be necessary (true in all plans) or disjunctive (one of a set must be true). Algorithms like LAMA use landmark-based heuristics to guide forward state-space search, such as A*, by counting unachieved landmarks. This connects directly to heuristic search in STRIPS/PDDL problems and is foundational for efficient solvers in hierarchical task network (HTN) planning and other complex domains.
Core Properties of Landmarks
Landmarks are logical propositions that must be true at some point in every valid plan for a given problem. They are foundational for deriving ordering constraints and creating powerful, informed heuristics in automated planning systems.
Logical Necessity
A landmark's defining property is its logical necessity. For a given planning problem with initial state I and goal G, a proposition L is a landmark if, for every plan π that solves the problem, there exists at least one state s in the execution trace of π where L is true. This is a semantic property derived from the domain and problem definition, not from a specific search algorithm.
- Example: In a logistics domain where a package must be moved from city A to city B, the proposition
(at package cityB)is a landmark because it is the goal itself. The proposition(in package truck)is also very likely a landmark, as the package must be inside a vehicle to be transported between cities.
Ordering Constraints
Landmarks induce a natural partial order over the plan. If landmark L1 must be achieved before landmark L2 can be achieved in every valid plan, then L1 is ordered before L2. This creates a landmark graph, a directed acyclic graph where nodes are landmarks and edges represent necessary orderings.
- Natural Order:
(in package truck)is naturally ordered before(at package cityB). - Greedy-Necessary Order: Two landmarks may be mutually exclusive in a state; achieving one may delete the other's preconditions, forcing an order.
- Reasoning Benefit: This graph decomposes the planning problem into a sequence of sub-problems (achieve the next set of landmarks), providing critical structural guidance.
Heuristic Foundation
Landmarks are the basis for highly effective admissible heuristics, such as the Landmark-Count Heuristic. The core idea: any plan must achieve all required landmarks. Therefore, a lower-bound estimate of the remaining plan cost is the cost of achieving all yet-unachieved landmarks.
- Landmark-Count Heuristic: The simplest form counts the number of unachieved landmarks. While admissible, it can be weak.
- Landmark-Cost Heuristic: A more powerful variant sums the minimum cost of achieving each remaining landmark, respecting their orderings in the landmark graph. This provides a much more informed, yet still admissible, estimate that dramatically prunes the search space for algorithms like A*.
Discovery & Computation
Identifying landmarks automatically is a key computational challenge. Exact discovery can be as hard as planning itself, so efficient approximations are used.
- Reachable & Necessary: Common algorithms work by analyzing the relaxed planning graph (used in Fast-Forward planning). A proposition is a candidate landmark if it is reachable from the initial state and necessary for achieving the goal in the relaxed problem.
- LAMA Algorithm: The LAMA planner popularized the use of landmark-based heuristics. It extracts a set of landmarks and their orderings from a relaxed planning graph, then uses the landmark-cost heuristic to drive a greedy best-first search with periodic restarts.
Fact vs. Action Landmarks
While the classical definition centers on fact landmarks (propositions), the concept extends to action landmarks.
- Fact Landmark: A proposition that must be true.
(at package cityB). - Action Landmark: An action that must appear at least once in every valid plan. In a problem requiring driving between two cities, the action
(drive truck cityA cityB)is an action landmark. - Relationship: Action landmarks can often be derived from fact landmarks (an action that achieves a necessary fact is a candidate). Using both types provides a more comprehensive view of the plan's necessary structure.
Disjunctive & Conjunctive Landmarks
Landmarks can be complex logical formulas, not just single facts.
- Disjunctive Landmark: A set of propositions
{L1, L2, ..., Ln}where at least one must be true in every plan. Example: To board a plane, you must have(has boarding-pass)OR(has mobile-pass). This represents multiple ways to satisfy a requirement. - Conjunctive Landmark: A set of propositions that must all be true together at some point. Example: To perform a chemical reaction, you must have
(in beaker reagent-A)AND(in beaker reagent-B)AND(temperature beaker 100C)simultaneously. - System Impact: Recognizing disjunctive landmarks prevents heuristic overestimation, while conjunctive landmarks reveal critical synchronization points.
How Landmarks Guide Automated Planning
A landmark is a proposition or fact that must be true at some point in every valid plan for a given problem, providing critical structural constraints for heuristic search algorithms.
In automated planning, a landmark is a logical proposition that must become true at least once in any sequence of actions that solves the problem. Identifying these mandatory facts—such as 'package is loaded' before 'package is delivered'—provides a powerful ordering constraint on potential solutions. Planners use algorithms to extract landmarks from the problem's initial state, goal conditions, and action definitions in PDDL, creating a partial skeleton that every valid plan must satisfy.
Landmarks are primarily used to derive informed heuristic functions for search algorithms like A*. The most common, the landmark-count heuristic, estimates the distance to the goal by counting the number of remaining unachieved landmarks. This heuristic is admissible (never overestimates cost) when considering only necessary facts, guaranteeing optimal solutions. This makes landmark-based guidance essential for efficiently navigating vast state spaces in domains like logistics, robotics, and hierarchical task network planning.
Frequently Asked Questions
A landmark is a critical concept in automated planning, representing a fact that must be true at some point in every valid plan for a given problem. This section answers common technical questions about how landmarks are identified and used to create efficient heuristics.
A landmark is a proposition (a fact about the world) that must be true at some point in every valid plan that solves a given planning problem. It represents an unavoidable intermediate achievement on the path from the initial state to the goal state. For example, in a logistics problem where a package must be in City B, a landmark might be 'package is on a truck' or 'truck is in City A.' Landmarks are derived from the structure of the problem's actions, preconditions, and effects, not from a single plan. They are used to derive ordering constraints and to create informed heuristic functions that dramatically improve the efficiency of planners like Fast Downward.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Landmarks are foundational constructs within automated planning. Understanding related concepts is essential for system architects designing robust, goal-directed agents.
Heuristic Function
A heuristic function estimates the cost to reach a goal from a given state, guiding search algorithms like A* toward promising solutions. Landmarks are a primary source for deriving informed heuristics (e.g., landmark-count heuristics), which are more accurate than uninformed ones. These heuristics calculate the number of remaining landmarks or the cost to achieve them, providing a powerful lower-bound estimate that dramatically prunes the search space.
Admissible Heuristic
An admissible heuristic never overestimates the true cost to the goal, guaranteeing that algorithms like A* will find an optimal plan. Heuristics derived from landmarks, such as the landmark-cut heuristic, are often admissible. This property is critical for domains requiring provably optimal solutions, as it ensures the planner will not be misled by an overly optimistic cost estimate during its state-space exploration.
Ordering Constraint
An ordering constraint specifies a necessary temporal relationship between two plan steps. Landmark analysis automatically discovers two key types:
- Natural Orderings: A landmark L1 must be achieved before L2 in every valid plan.
- Necessary Orderings: L1 must be achieved before L2 in at least one valid plan. These constraints are crucial for plan graph algorithms like Graphplan, as they refine the search by eliminating invalid action sequences early.
Precondition
A precondition is a logical proposition that must be true in the current state for an action to be executable. Landmarks are a generalization of this concept. While a precondition is a fact required before a single action, a landmark is a fact required at some point in the entire plan. Recognizing that a goal is a landmark whose achievement is necessarily deferred helps planners reason about action sequencing and intermediate subgoals.
STRIPS Formalism
STRIPS (Stanford Research Institute Problem Solver) is the foundational representation for classical planning, defining states as sets of logical propositions. Landmarks are inherently defined within STRIPS-like representations. The formalism's clear semantics—preconditions, add effects, and delete effects—enable the automated extraction of landmarks through causal analysis of how propositions become true and are used by subsequent actions.
Graphplan Algorithm
Graphplan is a planning algorithm that builds a layered planning graph, alternating between proposition layers and action layers. Landmark discovery is deeply integrated into modern Graphplan derivatives. The algorithm's structure naturally reveals mutual exclusions (mutexes) between propositions and actions, which is directly used to infer landmark ordering constraints and to compute effective landmark-based heuristics for guiding the solution extraction phase.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us