Planning

Version

v1 · 2026-09-08 · History

Prime #

1538

Aliases

Prospective planning

Core Idea

Planning is the substrate-independent operation of representing a goal, present state, constraints, possible actions, dependencies, and contingencies so future commitments can be ordered or conditioned in advance. The abstraction is not exhausted by its familiar source-domain notation. Its autonomous core is the prospective goal-to-action bridge that orders or conditions commitments before execution while remaining auditable and revisable, rather than foresight alone, scheduling alone, or improvisation during action.^[1]

The operative mechanism is this: A planner models the gap between current and desired states, searches or constructs actions whose preconditions and effects bridge it, allocates time and resources, and installs monitoring and revision points for deviations. The mechanism separates identity from observation. A case does not qualify merely because an observer can describe it using the word planning; the constitutive relation must be present in the carrier.

The load-bearing invariant is that a plan explicitly links a future objective to a structured set of prospective actions or policies through preconditions, dependencies, resources, timing, uncertainty, and revision conditions. Carrier, relation, invariant, admissible variation and collapse condition must all be typed. This blocks migration from an exact mathematical or empirical claim into a loose metaphor.^[2]

Across substrates, notation and evidence change while the role graph remains. The analyst first identifies what can vary, then identifies the organization that survives those variations, then tests a nearby counterexample. This conserved decision sequence is the basis for Prime status.^[3]

The strict residual is the prospective goal-to-action bridge that orders or conditions commitments before execution while remaining auditable and revisable, rather than foresight alone, scheduling alone, or improvisation during action. It is broader than one technique that recognizes or controls the structure and narrower than an unqualified claim of order, resemblance or usefulness. A reference-grade use therefore states both the positive test and the nearest boundary.

Structural Signature

• Typed carrier: the objects, states, events or observations on which the claimed organization exists.
• Granularity: the spatial, temporal, logical or institutional scale at which elements and relations are individuated.
• Constitutive relation: a repeatable, invariant or organizing relation that does more work than the shared label.
• Observation map: a declared way of measuring or representing the carrier without confusing the representation with the thing.
• Admissible variation: transformations or perturbations that preserve identity and reveal which features are incidental.
• Invariant: a relation or diagnostic that remains stable across those variations.
• Boundary counterexample: a neighboring case with superficial similarity but without the constitutive relation.
• Evidence path: proof, measurement, repeated observation or traceable interpretation supporting the claim.
• Uncertainty: sensitivity to noise, sampling, resolution, model choice and observer expectation.
• Collapse test: a change that removes the invariant and therefore destroys the identity.
• Transfer mapping: literal occupants for every role in a second substrate, not a metaphorical reuse of vocabulary.
• Use separation: discovery, prediction, control and communication are consequences or applications, not the identity itself.

What It Is Not

• It is not prediction: forecasts describe possible futures but need not specify action.
• It is not scheduling alone: timing is one component and may omit goals, causal effects, resources, and contingencies.
• It is not execution: a plan can exist before or without its enactment.
• It is not a wish list: desired outcomes without feasible actions, dependencies, and commitments do not constitute a plan.
• It is not one canonical example. An example demonstrates the abstraction but cannot define the whole class.
• It is not a detector or recognition algorithm. A fallible method can identify the structure, but method and target remain distinct.
• It is not a convenient label for anything organized. The constitutive relation and collapse test must be stated.
• It is not proof of causation. Stable structure can arise from several mechanisms, confounding or selection.
• It is not observer-free by stipulation. Measurement scale and representation can create or erase apparent structure.
• It is not universal sameness. Variation is expected, but only within a declared identity-preserving class.
• It is not value or desirability. A harmful, accidental or meaningless case can satisfy the structural test.
• It is not a promise of prediction. Recognition can be retrospective or descriptive when dynamics remain uncertain.

Broad Use

individual action. The carrier is a person with a future goal, current state, options, time, and resources. The identity test is that prospective actions are ordered by precondition and linked to the goal with revision triggers. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is memory, motivation, and bounded cognition are local constraints. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

project management. The carrier is deliverables, tasks, dependencies, owners, budgets, and dates. The identity test is that the work graph and resource schedule jointly connect authorization to completion. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is organizational governance and estimation practices supply the accent. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

robotics. The carrier is an agent state, world model, action model, cost, and goal condition. The identity test is that a policy or action sequence reaches the goal across modeled contingencies. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is sensing, dynamics, computation, and control latency govern execution. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

public policy. The carrier is a collective objective, legal authority, stakeholders, instruments, and uncertain responses. The identity test is that staged interventions and evaluation points connect policy intent to implementation. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is legitimacy, distribution, and public accountability are constitutive domain constraints. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

manufacturing. The carrier is materials, operations, capacities, due dates, and demand. The identity test is that routing and scheduling assign feasible transformation steps before production. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is physical process capability and inventory are local accents. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

ecological restoration. The carrier is a degraded system, desired functions, interventions, seasons, and monitoring. The identity test is that sequenced actions and adaptive thresholds bridge current condition to a target range. This is a literal instantiation rather than decorative analogy because the carrier, observable organization, conserved relation, variation class, and failure test retain the same roles. The domain accent is ecological uncertainty and ethical stewardship constrain the plan. A responsible analysis states scale, observation window, representation and noise model before claiming the structure, then distinguishes the structure itself from the process used to discover, stabilize or exploit it. Removing the constitutive relation must make the classification fail; otherwise the label is only topical resemblance. Evidence can be mathematical, experimental, computational or documentary, but it must attach to the same role graph and expose uncertainty and counterexamples.

Across these substrates the workflow is conserved. Define the carrier and scale; state the relation; identify transformations that should preserve it; choose a diagnostic; test positive and negative cases; estimate sensitivity; and separate recognition from causal explanation or intervention. The workflow makes Planning portable without flattening each domain's evidence obligations.

The strongest test is residual substitution. Replace the source-domain nouns with typed roles and ask whether a second field can fill every role without changing the operation. If only the word survives, transfer is metaphorical. If carrier, relation, invariant, perturbation and collapse test survive, the Prime has literal reach. This requirement protects the encyclopedia from promoting fashionable vocabulary merely because it appears in many fields.

Scale is constitutive. A relation can be stable at one grain and disappear at another. Aggregation may manufacture regularity; high resolution may fragment a robust macroscopic object into irrelevant detail. Claims should therefore bind scale and observation window to the identity while preserving a route for comparing scales. The abstraction is not whatever remains under every imaginable magnification.

Uncertainty is also structural. Sparse data, measurement error, preprocessing and model choice can generate false positives. Confirmation should include alternative representations and held-out observations where feasible. Mathematical examples replace sampling uncertainty with convention and proof obligations, but still require precise carrier and equivalence.

Finally, use does not define identity. A structure may enable compression, explanation, prediction, aesthetic effect or control. Those payoffs motivate attention, yet a case can qualify without delivering every payoff. Conversely, an intervention may work for reasons unrelated to the claimed structure. The Prime records what the thing is before cataloging what agents do with it.

Clarity

A clear Planning claim can be rewritten as a testable sentence: on carrier C at scale S, relation R holds within tolerance T, remains under transformations V, and fails for counterexample K. This grammar exposes missing components and prevents a noun from standing in for an argument.

Names often mix target, representation and process. The target is the organization in the carrier. A diagram, equation, category or narrative is a representation. Detection, classification, design and control are processes. The three can be tightly coupled, but merging them creates collision with neighboring encyclopedia nodes.

Identity needs both intension and extension. The intensional test states a plan explicitly links a future objective to a structured set of prospective actions or policies through preconditions, dependencies, resources, timing, uncertainty, and revision conditions. The extension supplies diverse positive cases and instructive failures. Neither one list of examples nor one elegant definition is enough when conventions and measurement enter the boundary.

A claim should also state whether it is exact, statistical, approximate or interpretive. Exact identities require proof. Statistical identities require uncertainty and a null comparison. Interpretive identities require traceable evidence and alternative readings. The structural frame supports all four without pretending their warrants are interchangeable.

Ambiguity is resolved by the nearest-confusable test. If a candidate can be fully explained by recognition, resemblance, control, representation or one domain-specific subtype, it should route there. Planning remains only when the prospective goal-to-action bridge that orders or conditions commitments before execution while remaining auditable and revisable, rather than foresight alone, scheduling alone, or improvisation during action survives that subtraction.

Manages Complexity

Planning manages complexity by replacing an unstructured inventory with a small set of relations that survive relevant variation. Compression becomes legitimate when the retained relation supports reconstruction, comparison or reliable discrimination and the discarded details are declared incidental for the task.

The abstraction also supports chunking. Once an organized unit is established, reasoning can treat it as one object while retaining an audit trail to its elements. This lowers cognitive and computational load without asserting that internal variation is absent. Chunk boundaries must be reopened when transfer or failure depends on hidden detail.

It localizes disagreement. Analysts can dispute carrier boundaries, scale, relation, tolerance, evidence or causal explanation separately rather than arguing over the label as a whole. This is especially valuable where one field uses an exact definition and another uses probabilistic recognition.

It guides search by privileging transformations and counterexamples. Instead of collecting only more positive instances, the analyst asks which changes preserve identity and which destroy it. That experiment reveals the core faster than surface enumeration and reduces confirmation bias.

The primary compression hazard is false invariance. Preprocessing, selection and aggregation can make unrelated cases look stable. A reference-grade account reports what was normalized, which alternatives were tried and where the abstraction stops paying rent. Complexity is managed by controlled omission, not by hiding residuals.

Abstract Reasoning

1. Type the carrier and explain why its elements are individuated at the selected scale.
2. Separate the target structure from the notation, image, model or story used to display it.
3. State the constitutive relation as an equation, rule, repeatability condition or traceable interpretive criterion.
4. List transformations expected to preserve identity and justify why they are incidental.
5. Choose at least one positive diagnostic and one collapse test.
6. Construct a nearest counterexample that preserves surface similarity while removing the invariant.
7. Test sensitivity to scale, observation window, noise, sampling and representation choice.
8. Distinguish exact, approximate, statistical and interpretive claims and apply the matching evidence standard.
9. Map every structural role into a second unrelated substrate to test literal transfer.
10. Subtract neighboring processes such as recognition, completion, design or control and identify the remaining residual.
11. Separate descriptive identity from causal origin and from practical exploitation.
12. Record uncertainty, conventions and known failure domains so downstream users can rematch the claim.

Knowledge Transfer

Transfer begins from the role graph, not the name. Preserve carrier, relation, invariant, admissible variation, diagnostic and collapse test; then substitute domain occupants. A successful mapping explains how the target case would be recognized and how it would fail.

The most common transfer error is feature substitution. One field may represent the structure visually, another algebraically and another behaviorally. The visible features are not the invariant. Transfer must identify the relation those features evidence and state the target domain's measurement or proof obligations.

A second error is process substitution. A detector, classifier or design recipe can be reused while its target changes. That is method transfer, not necessarily transfer of Planning. Conversely, the same structure can be discovered by unrelated methods. The encyclopedia node concerns the conserved target relation.

Knowledge transfer improves when negative cases travel too. For every source example, construct a target case with similar components but without a plan explicitly links a future objective to a structured set of prospective actions or policies through preconditions, dependencies, resources, timing, uncertainty, and revision conditions. If analysts cannot articulate the failure, the mapping is too loose. Counterexamples prevent the Prime from expanding into a synonym for organization.

Transfer should preserve uncertainty. An exact theorem cannot make an empirical target exact, and an interpretive source does not remove target measurement requirements. What transfers is the decision architecture; warrants remain native to their domains.

The practical payoff is a reusable audit sequence. Teams can compare apparently different phenomena by the same typed questions, discover when a domain-specific subtype is sufficient, and route residuals without duplicating nodes. The result is cross-domain leverage with explicit limits rather than an analogy catalog.

Examples

1. In individual action, start with a person with a future goal, current state, options, time, and resources. Specify the units and transformations under which sameness is being asserted. Demonstrate that prospective actions are ordered by precondition and linked to the goal with revision triggers; then perturb a nonessential feature and verify that the identity remains, and perturb the defining relation and verify that it collapses. The boundary is memory, motivation, and bounded cognition are local constraints. The mapping is carrier → observations → relation → invariant → variation class → diagnostic failure. This walkthrough prevents one salient instance, a visual resemblance, or a successful application from substituting for the abstraction.
2. In project management, start with deliverables, tasks, dependencies, owners, budgets, and dates. Specify the units and transformations under which sameness is being asserted. Demonstrate that the work graph and resource schedule jointly connect authorization to completion; then perturb a nonessential feature and verify that the identity remains, and perturb the defining relation and verify that it collapses. The boundary is organizational governance and estimation practices supply the accent. The mapping is carrier → observations → relation → invariant → variation class → diagnostic failure. This walkthrough prevents one salient instance, a visual resemblance, or a successful application from substituting for the abstraction.
3. In robotics, start with an agent state, world model, action model, cost, and goal condition. Specify the units and transformations under which sameness is being asserted. Demonstrate that a policy or action sequence reaches the goal across modeled contingencies; then perturb a nonessential feature and verify that the identity remains, and perturb the defining relation and verify that it collapses. The boundary is sensing, dynamics, computation, and control latency govern execution. The mapping is carrier → observations → relation → invariant → variation class → diagnostic failure. This walkthrough prevents one salient instance, a visual resemblance, or a successful application from substituting for the abstraction.
4. In public policy, start with a collective objective, legal authority, stakeholders, instruments, and uncertain responses. Specify the units and transformations under which sameness is being asserted. Demonstrate that staged interventions and evaluation points connect policy intent to implementation; then perturb a nonessential feature and verify that the identity remains, and perturb the defining relation and verify that it collapses. The boundary is legitimacy, distribution, and public accountability are constitutive domain constraints. The mapping is carrier → observations → relation → invariant → variation class → diagnostic failure. This walkthrough prevents one salient instance, a visual resemblance, or a successful application from substituting for the abstraction.
5. In manufacturing, start with materials, operations, capacities, due dates, and demand. Specify the units and transformations under which sameness is being asserted. Demonstrate that routing and scheduling assign feasible transformation steps before production; then perturb a nonessential feature and verify that the identity remains, and perturb the defining relation and verify that it collapses. The boundary is physical process capability and inventory are local accents. The mapping is carrier → observations → relation → invariant → variation class → diagnostic failure. This walkthrough prevents one salient instance, a visual resemblance, or a successful application from substituting for the abstraction.
6. In ecological restoration, start with a degraded system, desired functions, interventions, seasons, and monitoring. Specify the units and transformations under which sameness is being asserted. Demonstrate that sequenced actions and adaptive thresholds bridge current condition to a target range; then perturb a nonessential feature and verify that the identity remains, and perturb the defining relation and verify that it collapses. The boundary is ecological uncertainty and ethical stewardship constrain the plan. The mapping is carrier → observations → relation → invariant → variation class → diagnostic failure. This walkthrough prevents one salient instance, a visual resemblance, or a successful application from substituting for the abstraction.

Structural Tensions

• Invariant versus variation: identity requires stability while meaningful cases retain nontrivial differences.
• Discovery versus projection: observers find structure but can also impose it through preprocessing and expectation.
• Compression versus residual loss: useful simplification can conceal details that matter under transfer or stress.
• Exactness versus tolerance: mathematical and empirical instances use different but explicit thresholds of sameness.
• Local versus global: organization at one region or scale may not extend to the whole carrier.
• Static versus dynamic: a snapshot may display structure while its persistence or generating process differs.
• Description versus explanation: specifying the relation does not alone identify why it exists.
• Recognition versus intervention: accurate classification does not guarantee controllability.
• Universality versus convention: the role graph transfers while notation and evidence standards remain local.
• Robustness versus sensitivity: the abstraction must ignore incidental variation without becoming blind to collapse.

Structural–Framed Character

Planning occupies the mixed-framed region of the structural–framed spectrum. It constructs a revisable connection from a represented current state to a desired future state through actions, dependencies, resources, timing, contingencies, and monitoring, whether for a personal project, a manufacturing process, a public program, or a robotic policy.

Its vocabulary is strongly shaped by each action domain because goals, feasible moves, and commitments differ. Planning has some evaluative force through feasibility and coherence, although a poor plan remains a plan. Institutions formalize project and policy planning, while individuals can plan without them, so that diagnostic is mixed. Planning is intrinsically tied to purposive agents. Finally, goals and action descriptions are supplied by the planner, whereas material constraints and dependencies are discovered. The five diagnostics therefore yield a clear framed lean without placing the concept at the endpoint.

Substrate Independence

The substrate-independence score is high because individual action, project management, robotics, public policy, manufacturing, ecological restoration all support literal occupants for carrier, relation, invariant, variation and collapse. None supplies a privileged material substrate.

Independence does not mean content-free. The invariant remains a plan explicitly links a future objective to a structured set of prospective actions or policies through preconditions, dependencies, resources, timing, uncertainty, and revision conditions. A proposed transfer that cannot instantiate that condition fails even if speakers commonly use the same word.

The abstraction spans exact and empirical carriers because its structure concerns relations and invariance, while warrant is typed locally. This is analogous to a mathematical form instantiated by noisy measurements: the target may be approximate without the concept becoming metaphorical.

The boundary is generic order. Not every organized thing is Planning. Prime status depends on an autonomous test, diverse counterexamples and preserved roles. Where a narrower existing Prime fully captures the case, that node should be used instead.

Relationships to Other Abstractions

Current abstraction Planning Prime

Parents (1) — more general patterns this builds on

• Planning is a kind of Foresight Prime

  The accepted reference-grade review places Planning under Foresight because the child instantiates or depends on the parent's broader structure while retaining its own constitutive identity.

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

• Automated planning and scheduling Domain-specific is a kind of Planning

  The proposed strict upward parent is prime:planning.

• Farsightedness (game theory) Domain-specific is a kind of Planning

  The proposed strict upward parent is prime:planning.

• Graph bandwidth Domain-specific is a kind of Planning

  The proposed strict upward parent is prime:planning.

▸ Show 9 more

Hierarchy path (1) — routes to 1 parentless root

• Planning → Foresight

Neighborhood in Abstraction Space

Planning sits among the more crowded primes in the catalog (2^nd percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.

Family — Design Process & Iterative Refinement (11 primes)

Nearest neighbors

• System — 0.97
• Inquiry — 0.97
• Addition — 0.97
• Information — 0.97
• Pattern — 0.97

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

Not to Be Confused With

• Foresight: Anticipates plural futures; planning constructs prospective actions within or across them.
• Strategy: Selects an overarching approach and allocation logic; planning elaborates executable actions, dependencies, and contingencies.
• Scheduling: Assigns activities to time and capacity, often after the action structure is selected.
• Decision: Commits to an alternative; planning can prepare a conditional structure before each decision point.
• Scenario planning: Develops multiple plausible futures to stress strategy; it is one planning method rather than the whole abstraction.

The prospective workspace queue contains one strict upward edge to prime:foresight. No live DAG mutation is authorized.

Solution Archetypes

No catalogued solution archetypes reference this prime yet.

References

[1] George A. Miller, Eugene Galanter, and Karl H. Pribram, Plans and the Structure of Behavior, Henry Holt, 1960. registry ↩

[2] Michael E. Bratman, Intention, Plans, and Practical Reason, Harvard University Press, 1987. registry ↩

[3] Malik Ghallab, Dana Nau, and Paolo Traverso, Automated Planning: Theory and Practice, Morgan Kaufmann, 2004. registry ↩