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. Planning constructs, compares, and revises possible courses; a plan is the resulting arrangement available for use. The artifact may be written, diagrammed, encoded as a policy, retained in memory, or distributed among coordinated roles. It can be incomplete, mistaken, abandoned, or overtaken by events and still be a plan because planhood concerns prospective organization, not guaranteed success. Conversely, a retrospective narrative of what happened is not a plan unless it also served or now serves to guide intended action.

The Prime is substrate-neutral because goals, state descriptions, actions, preconditions, ordering, resources, checkpoints, and contingencies recur across individual behavior, projects, logistics, public policy, military operations, automated agents, and computing. A route itinerary, emergency protocol, project network, treatment plan, query plan, and robot policy differ in notation and authority, but each represents a conditional bridge from current conditions toward an objective. A mere wish lacks an action bridge; a schedule may lack an objective or dependencies; a prediction describes what may happen without committing an intended course.

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.

Structural Signature¶

Recurring features:

planning subject. the agent, group, organization, or controller for whom the arrangement guides action
present-state model. the relevant starting conditions, capabilities, commitments, and uncertainties
objective. the desired state, output, maintained condition, or avoided outcome
action repertoire. available interventions or steps capable of changing the represented state
ordering and dependency. temporal sequence, precedence, preconditions, and conditional branches among actions
resource commitments. time, attention, people, money, materials, authority, or computational capacity required
contingencies. conditions that select alternate actions, trigger escalation, or invalidate the arrangement
representation. memory, text, diagram, schedule, policy, program, or distributed protocol that preserves the arrangement
monitoring and revision. comparison of execution and environment with the represented path so the plan can be updated
execution boundary. the plan guides action but is not identical to the actions or their outcome

What It Is Not¶

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.
Schedule. A schedule assigns times; a plan may contain a schedule but also relates action to objectives, conditions, and dependencies.
Policy. A policy can function as a conditional standing plan, but many policies instead state permissions, principles, or constraints without a course of action.
Procedure. A procedure prescribes a repeatable method; a plan configures actions for a particular objective and situation, often by selecting procedures.
Wish or commitment. Desire and resolve orient action but do not by themselves represent a path from present state to objective.

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
Public policy. implementation plans translate adopted objectives into accountable actions and review points
Manufacturing. production plans allocate material and capacity through ordered operations
Computing. query planners and automated agents encode executable or conditional routes through state space
Education. learning plans relate outcomes, activities, evidence, pacing, and revision
Conservation. management plans connect desired ecosystem conditions to interventions, monitoring, and adaptive triggers
Applicability boundary. A case must identify the carrier, criterion or shared objective, operative relation, and collapse condition defined above; verbal resemblance alone does not instantiate Plan.

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. A precise claim therefore fills at least these roles: planning subject, present-state model, objective, and execution boundary. It also states the level of analysis and the evidence that would make a competent observer reject the classification. This prevents a familiar word from doing explanatory work that belongs to a testable relation.

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. This makes heterogeneous cases comparable while keeping local mechanisms, authority, uncertainty, and evidence visible.

Abstract Reasoning¶

Planning Subject move. Identify the agent, group, organization, or controller for whom the arrangement guides action and record what observation supports the assignment.
Present-State Model move. Identify the relevant starting conditions, capabilities, commitments, and uncertainties and record what observation supports the assignment.
Objective move. Identify the desired state, output, maintained condition, or avoided outcome and record what observation supports the assignment.
Action Repertoire move. Identify available interventions or steps capable of changing the represented state and record what observation supports the assignment.
Ordering And Dependency move. Identify temporal sequence, precedence, preconditions, and conditional branches among actions and record what observation supports the assignment.
Resource Commitments move. Identify time, attention, people, money, materials, authority, or computational capacity required and record what observation supports the assignment.
Contingencies move. Identify conditions that select alternate actions, trigger escalation, or invalidate the arrangement and record what observation supports the assignment.
Representation move. Identify memory, text, diagram, schedule, policy, program, or distributed protocol that preserves the arrangement and record what observation supports the assignment.
Counterexample move. Remove one constitutive role while holding the surrounding topic fixed; if the label still appears equally applicable, the definition has become too loose.
Neighbor move. Compare the filled roles with the distinctions below and route the case to the narrower or broader entry whose collapse test it actually satisfies.

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. Formal domains may use proof, specifications, or executable traces; empirical domains use observation and measurement; institutions use authority, records, and rules; practical settings use performance and counterfactual tests. This Prime coordinates the questions without replacing those standards.

Transfer procedure. First identify the source case without metaphor. Then abstract planning subject, present-state model, objective, action repertoire, ordering and dependency. Map each role to the receiving case, test the collapse condition, and explicitly carry any domain qualification that affects validity. If a role has no literal occupant, transfer only a neighboring abstraction or label the comparison as analogy.

Examples¶

Formal/abstract¶

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.

Mapped back: planning subject → the carrier in the example; present-state model → its stated counterpart; objective → the defining condition; execution boundary → the described counterfactual boundary.

Applied/industry¶

A database query plan represents one executable strategy for obtaining a requested result: scan or index choices, join order, algorithms, intermediate data flows, and resource estimates. The optimizer performs planning by comparing alternatives; the selected plan is the action structure handed to execution. Runtime adaptation can replace part of it when cardinality estimates fail, showing that revision does not destroy plan identity and that the plan is distinct from both the query goal and the operations actually performed.

Mapped back: the applied carrier fills planning subject, its governing relation fills objective, the evidence fills resource commitments, and removal of execution boundary marks the point at which the example would cease to instantiate Plan.

Structural Tensions¶

T1 — Commitment versus revisability. A plan must constrain action enough to coordinate it, yet remain revisable when assumptions or conditions change. Diagnostic: Which elements are commitments, which are forecasts, and what evidence authorizes revision?

T2 — Detail versus adaptability. Fine detail reduces ambiguity but can make the representation brittle or costly to maintain. Diagnostic: What is the smallest action structure that preserves critical dependencies and contingencies?

T3 — Central coherence versus local knowledge. A shared plan integrates work while local actors often possess better information at execution time. Diagnostic: Where does the plan prescribe action, and where does it delegate conditional discretion?

T4 — Preferred path versus contingency set. One path aids coordination, but uncertainty may require branches, reserves, and abort criteria. Diagnostic: Which uncertainties are represented as branches rather than hidden assumptions?

T5 — Representation versus execution. A plan can be coherent while execution fails, and improvisation can succeed without following the plan. Diagnostic: Is the assessment about plan quality, compliance, implementation, or outcome?

T6 — Objective stability versus drift. Actions and measurements can gradually substitute a proxy or expanded mission for the original objective. Diagnostic: Does every major commitment still trace to the declared objective and acceptance criteria?

Terminal boundary synthesis. For Plan, the terminal identity test begins with the definition 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.. A reviewer must then establish the carrier and operation described by the agent, group, organization, or controller for whom the arrangement guides action and the relevant starting conditions, capabilities, commitments, and uncertainties. Recognition is constrained by the desired state, output, maintained condition, or avoided outcome, while admissible variation is limited by available interventions or steps capable of changing the represented state and the collapse boundary temporal sequence, precedence, preconditions, and conditional branches among actions. The source-domain setting in goal-directed action matters because a person orders tasks, allocates time, and sets fallback conditions for an objective and work packages, dependencies, milestones, resources, and risks form a revisable delivery structure specify where those roles have literal occupants. The strongest negative controls are Planning is the process of constructing and revising prospective action structures; a plan is a represented result of that process. and A goal identifies a desired condition without necessarily specifying actions, dependencies, resources, or contingencies.; a case satisfying either exclusion should not be rescued merely because its label or examples look familiar.

Terminal adjudication sequence. First, bind the claimed instance to a concrete carrier and state the criterion by which 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. is recognized. Second, vary implementation, scale, notation, and example while holding the relevant starting conditions, capabilities, commitments, and uncertainties fixed; persistence supports one identity rather than several topic fragments. Third, remove the desired state, output, maintained condition, or avoided outcome or trigger temporal sequence, precedence, preconditions, and conditional branches among actions and verify that the classification fails. Fourth, compare the result with the two negative controls instead of relying on name similarity. Fifth, check scope against a person orders tasks, allocates time, and sets fallback conditions for an objective and record any qualification supplied by goal-directed action. Finally, audit the graph claim. The accepted parent Representation records only the reviewed genus or prerequisite; it does not license migration of the specialist name to every parent instance. This sequence makes the entry rejectable, keeps analogy separate from literal transfer, and exposes which fact would require revision.

Structural–Framed Character¶

Plan is structural on the structural–framed spectrum. 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. Its structural skeleton is expressed by the roles above and can be evaluated without importing one home-domain mechanism.

Framing still matters for Plan. Institutions choose some criteria, communities stabilize terminology, practices determine admissible evidence, and normative consequences can follow from classification. Those facts qualify an instance without making the whole abstraction conventional. The correct test is whether changing the frame removes the constitutive relation or merely changes how it is named, measured, governed, or valued.

Across the spectrum tests, the vocabulary travels with moderate qualification, evaluative weight is separable from the descriptive identity, institutional origin is not universally constitutive, and import must be distinguished from recognition. The entry is therefore portable but not context-free.

Substrate Independence¶

Plan has high substrate independence — composite 5 / 5. 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 carrier can change while the relation and its rejection test remain intact. A cross-domain use does not require one material, notation, institution, species, or implementation.

The Plan rating is not a license for metaphor. Mechanisms and evidence remain local, and a familiar surface does not substitute for the typed roles. This Prime survives transfer only when the same relation is present and the same kind of counterfactual removal would make it fail.

Composite substrate independence — 5 / 5
Domain breadth — 5 / 5
Structural abstraction — 5 / 5
Transfer evidence — 5 / 5
Mechanism neutrality — 5 / 5

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

Neighborhood in Abstraction Space¶

Plan sits in a moderately populated region (57^th percentile for distinctiveness): it has near-neighbors but no dense thicket of synonyms.

Family — Iterative Learning & Plan Revision (5 primes)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With¶

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.
Schedule. A schedule assigns times; a plan may contain a schedule but also relates action to objectives, conditions, and dependencies.
Policy. A policy can function as a conditional standing plan, but many policies instead state permissions, principles, or constraints without a course of action.
Procedure. A procedure prescribes a repeatable method; a plan configures actions for a particular objective and situation, often by selecting procedures.
Wish or commitment. Desire and resolve orient action but do not by themselves represent a path from present state to objective.

Solution Archetypes¶

No catalogued solution archetypes reference this prime yet.

Notes¶

The immediate DAG parent is Representation (Representation, subsumption). The parent supplies a necessary broader identity, while Plan adds the differentiating roles stated here.

The entry intentionally separates the abstraction from its causes, instruments, outcomes, moral appraisal, and common implementations. Future DAG or solution-archetype work may add non-hierarchical relations, but those links should be adjudicated independently rather than inferred from shared vocabulary.

References¶

Frozen Wikipedia revision: https://en.wikipedia.org/wiki/Plan (revision 1368119763).
DOI: https://doi.org/10.1002/smj.4250070207
Supporting reference preserved in the packet: https://pmhut.com/what-should-be-included-in-a-project-plan
Supporting reference preserved in the packet: http://www.forecastingprinciples.com/paperpdf/Value%20of%20Formal%20Planning.pdf

The frozen Wikipedia revision is discovery provenance. The retained source set was reviewed for identity, formal or operational relation, and scope. The encyclopedia's structural synthesis is bounded to those claims; a thin authority surface is recorded as a nonblocking source-strengthening repair rather than concealed.