Plan

Version

v2 · 2026-09-28 · History

Prime #

1564

Domain group

Interdisciplinary & Synthetic

Origin domain

Cognitive Science

Subdomains

Planning, Action Theory → Cognitive Science

Also from

Computer Science & Software Engineering, Military & Strategic Studies, Organizational & Management Science

Aliases

Action plan, Prospective action structure

Core Idea

A plan is a prospective representation that organizes intended action before or during commitment. It connects a represented present state to an objective by specifying some combination of actions, ordering, dependencies, timing, resources, decision conditions, and contingencies. Plans range from a remembered intention with two ordered steps to a formally versioned program of work. Their common identity lies neither in length nor documentation but in providing an action-guiding structure that can be consulted, executed, monitored, and revised. A plan is the product of planning, not the planning process itself.

How would you explain it like I'm…

Steps to Get There

A plan is when you decide ahead of time what steps you'll do to get something you want. If you want to build a sandcastle, your plan might be: get the bucket, fill it with wet sand, flip it over. Even if a wave messes it up, you still had a plan.

Steps to a Goal

A plan is a set of steps you figure out before you do something, to get from where you are to where you want to be. It can say what to do, in what order, when, and what you'll need. A good plan also has 'if this happens, then do that' parts, like 'if it rains, we'll play inside.' Plans can be in your head or written down, and they can be tiny or huge. A plan can go wrong and still be a plan; just wishing for something isn't a plan, because it has no steps.

Structured Intended Action

A plan is a forward-looking arrangement that guides what you intend to do, connecting where things stand now to a goal through actions, their order, dependencies, timing, resources, and backup options. It's the product of planning, not the process: planning is the work of building and comparing options, while the plan is the result you can consult, follow, check progress against, and revise. A plan doesn't have to succeed, be complete, or be written down to count; what matters is that it's meant to guide action. That separates it from nearby things: a wish has a goal but no route, a schedule may list times without a goal or dependencies, and a prediction says what may happen without committing you to do anything. A diary of what happened last week isn't a plan either, unless it's being used to guide future action.

 

A plan is a prospective representation that organizes intended action, connecting a represented current state to an objective by specifying some combination of actions, ordering, dependencies, timing, resources, decision conditions, and contingencies. It is the output of planning, the arrangement available for use, rather than the construction-and-comparison process that produced it. Plans vary from a remembered two-step intention to a formally versioned program, and they can be written, diagrammed, encoded as a policy, stored in memory, or distributed across coordinated roles. What they share is an action-guiding structure that can be consulted, executed, monitored, and revised. Planhood concerns prospective organization rather than success, so an incomplete, mistaken, or abandoned plan still qualifies, whereas a retrospective account of events does not unless it guides action. The same structure appears in itineraries, emergency protocols, project networks, treatment plans, database query plans, and robot policies. Nearby concepts differ in specific ways: a wish lacks an action bridge, a schedule may lack an objective or dependencies, and a forecast describes likely events without committing to an intended course.

Broad Use

Plan applies wherever its complete role structure is present; the source domain is historical provenance, not a boundary on the Prime. Individual action. a person orders tasks, allocates time, and sets fallback conditions for an objective Projects. work packages, dependencies, milestones, resources, and risks form a revisable delivery structure Emergency response. trigger conditions select roles, communications, evacuation, containment, and recovery actions Medicine. treatment plans connect diagnosis and goals to sequenced interventions and monitoring Military operations. intent, phases, logistics, command relationships, branches, and sequels coordinate action.

Clarity

Use Plan only after naming the carrier and the relation that makes the case one. The minimal definition is: A plan is an externalized or internally maintained, revisable arrangement of intended actions, dependencies, timing, resources, and contingencies directed from a represented present state toward an objective. The most common ambiguity is to substitute a neighbor, an enabling condition, or a consequence for the identity itself.

Manages Complexity

Plan manages complexity by compressing many implementations into a stable role structure without erasing the variables that control validity. Analysts can compare cases by filling the same slots, locate disagreement in a missing role, and separate the constitutive relation from causes, instruments, representations, and consequences. The compression is intentionally reversible: the short label expands into planning subject, present-state model, objective, action repertoire, ordering and dependency, resource commitments, with explicit boundaries for variation and collapse.

Abstract Reasoning

1. Planning Subject move. Identify the agent, group, organization, or controller for whom the arrangement guides action and record what observation supports the assignment.
2. Present-State Model move. Identify the relevant starting conditions, capabilities, commitments, and uncertainties and record what observation supports the assignment.
3. Objective move. Identify the desired state, output, maintained condition, or avoided outcome and record what observation supports the assignment.
4. Action Repertoire move.

Knowledge Transfer

Cross-domain transfer. The present-state–objective–action–dependency representation travels without requiring one institution, notation, or material carrier; local authority and planning conventions alter warrants but not the relation. The invariant is not the source-domain vocabulary but the typed relation expressed by the one-line definition. Transfer is literal when a receiving domain can fill the same roles and expose the same failure boundary; it is analogical when only a visual, verbal, or narrative resemblance survives. Local warrants for Plan. Different domains establish those roles differently.

Example

An emergency plan for a chemical release identifies detection thresholds, command roles, isolation zones, evacuation routes, shelter conditions, hospital coordination, communication channels, resource caches, and criteria for switching between actions. The plan exists before any release, can be exercised and revised, and guides action if its trigger occurs. A list saying only “protect the public” states an objective, while a timetable without conditional actions is merely a schedule.

Relationships to Other Abstractions

Current abstraction Plan Prime

Parents (1) — more general patterns this builds on

• Plan is a kind of Representation Prime

  Plan is a strict kind of Representation: A plan is an externalized or internally maintained, revisable arrangement of intended actions, dependencies, timing, resources, and contingencies directed from a represented present state toward an objective.

Children (1) — more specific cases that build on this

• Budget Domain-specific is a kind of Plan

  A budget is a quantitative, time-bounded, resource-constrained kind of plan.

Hierarchy path (1) — routes to 1 parentless root

• Plan → Representation → Abstraction

Distinction from Neighbors

• Planning. Planning is the process of constructing and revising prospective action structures; a plan is a represented result of that process.

• Goal. A goal identifies a desired condition without necessarily specifying actions, dependencies, resources, or contingencies.

• Prediction. A prediction represents an expected future, whereas a plan represents an intended and action-guiding route.