Skip to content

Realized vs Possible Outcomes

Version
v1 · 2026-08-24 · History
Prime #
1114
Origin domain
Mathematics
Subdomain
output set comparison → Mathematics

Core Idea

The structural comparison between what a process actually produces and what it could in principle produce — two sets, the realized nested inside the possible — where the gap between them, its shape, and its causes are the primary object of analysis. The realized set is observed; the possibility set is constructed from a model of the process, never directly seen.

How would you explain it like I'm…

Could-Have vs Did

When you roll a die, lots of numbers could have come up, but only one actually did. It helps to remember both: the number you got, and all the numbers you could have gotten. Looking at both together tells you more than just the one you rolled.

What Could Have Happened

Realized vs Possible Outcomes is about holding two things in mind at once: what actually happened, and everything that could have happened. What actually happened you can just see; the list of what could have happened you have to work out from how the thing works. The interesting part is the gap between them — what was possible but didn't happen, and why. Without thinking about both, you'd treat the one thing that happened as the whole story and miss everything the situation could have done.

Realized Inside Possible

Realized vs Possible Outcomes is the structural comparison between what a process actually produces and what it could in principle produce — two sets, with the realized one a subset of the possible one, and the relationship between them itself the object of analysis. The realized set (what happened, what was visited) is observable; the possibility set (what could happen, what's reachable) is constructed from a model of the process, often with real effort, and acts as the reference against which the realized outcomes are interpreted. The essential move is to hold both sets in view at once and treat the gap — its shape and its causes — as the primary thing to analyze. A key subtlety is that the possibility set is built, not seen: different models of the process give different possibility sets, so the construction is part of the analysis. Without this, you collapse one side — either leaving the possibilities unstated and treating the realized as everything, or reading the realized as if it exhausted what the system could do.

 

Realized-vs-possible outcomes is the structural comparison between what a process actually produces and what the process could in principle produce — two sets, one a subset of the other, where the relationship between them is itself a load-bearing object of analysis. The realized set — what happens, what was achieved, what was visited — is observable; the possibility set — what could happen, what could have been achieved, what is reachable — is constructed from a model of the process, often with effort, and is the implicit reference against which the realized outcomes are interpreted. The essential commitment is to hold both sets in view at once and to treat the gap between them, its shape, and its causes as the primary analytical object. Three structural pieces recur: a process with definable inputs, dynamics, or rules that determine what outputs are possible; a possibility set — the full collection of outcomes producible under its constraints (the reachable set of a dynamical system, the feasible set of an optimization, the support of a distribution, the action set in a game, the capability set in Sen's framework); and a realized set — the subset actually produced under the particular inputs, history, or play that occurred. The relationship is set inclusion, with the gap as the analytical object, and the gap's shape — uniform, lumpy, biased, fractal — is informative about which possibilities go unrealized and why. The distinctive commitment is that the possibility set is constructed, not observed: different models yield different possibility sets, and that construction is part of the analysis. Without the prime, analysis collapses one side — either leaving the possibility set unstated and treating the realized as the whole story, or reading the realized as if it exhausted the system's behavior.

Broad Use

  • Dynamical systems: the reachable set is the possibility set, the trajectory the realized set; safety verification operates on the gap.
  • Optimization: the feasible set versus the chosen point, with suboptimal choices sitting inside the Pareto frontier.
  • Probability: the support of a distribution versus a finite sample.
  • Game theory: the strategy space versus equilibrium actions, with off-equilibrium paths constraining behaviour.
  • Sen's capability framework: the capability set versus achieved functionings, so wellbeing requires assessing capabilities, not only outcomes.
  • Software testing: full execution paths versus paths the suite exercises; coverage reports on the gap.
  • Information theory: channel capacity versus the rate achieved.

Clarity

Separates four fused questions — descriptive (what did it produce?), capacity (what could it?), gap (what is unrealized?), and constraint (why is the gap that size?) — and forces the discipline of constructing the possibility set explicitly.

Manages Complexity

Compresses reachability, feasibility, support, capability, and coverage into one comparison with three clean interventions: expand the realized, shrink the possible, or reshape the gap.

Abstract Reasoning

Yields portable inferences: realized outcomes under-determine the possibility set; a large gap signals unused capacity or unrealized risk; selection effects bias inference; and comparative assessment requires possibility-set normalization.

Knowledge Transfer

  • Control → software: the reachable-set technique ports into model-checking, where reachable program states must be bounded.
  • Economics → AI: Sen's capability-versus-functioning distinction transferred into fairness, as the recognition that outcome equality does not imply opportunity equality.
  • Testing → method evaluation: the coverage-of-possibility-space discipline ports into comparing the explored region of a treatment space to the full space.

Example

Reachability analysis certifies a safety-critical system only if its computed reachable tube — not merely the actual trajectory — never intersects the unsafe region, which is why testing alone is insufficient: a system can pass every realized test yet have a reachable set that grazes catastrophe.

Relationships to Other Abstractions

Local relationship map for Realized vs Possible OutcomesParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Realized vsPossible OutcomesPRIMEPrime abstraction: Set and Membership — is part ofSet andMembershipPRIMEDomain-specific abstraction: Image (of a Function) — is a decomposition ofImage (ofa Function)DOMAINDomain-specific abstraction: Outcome (game theory) — is a kind ofOutcome(game theory)DOMAINDomain-specific abstraction: Outcome (probability) — is a kind ofOutcome(probability)DOMAIN

Current abstraction Realized vs Possible Outcomes Prime

Parents (1) — more general patterns this builds on

  • Realized vs Possible Outcomes is part of Set and Membership Prime

    Realized vs Possible Outcomes contains a possibility set, a realized subset, and the membership and inclusion tests that expose their gap.

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

  • Outcome (game theory) Domain-specific is a kind of Realized vs Possible Outcomes

    The proposed strict upward parent is prime:realized_vs_possible_outcomes.

  • Outcome (probability) Domain-specific is a kind of Realized vs Possible Outcomes

    The proposed strict upward parent is prime:realized_vs_possible_outcomes.

  • Image (of a Function) Domain-specific is a decomposition of Realized vs Possible Outcomes

    Stripping function-theory vocabulary from Image leaves the realized output set, possible codomain, subset gap, and coverage question intact.

Hierarchy path (1) — routes to 1 parentless root

Not to Be Confused With

  • Realized vs Possible is not Counterfactual Reasoning because counterfactual reasoning evaluates a single alternative world, whereas this prime holds the entire possibility set against the realized subset.
  • Realized vs Possible is not Regret because regret is the valued gap against a preference ordering, whereas this prime is the unvalued set comparison, indifferent to which outcomes are better.
  • Realized vs Possible is not Sampling Representativeness because representativeness asks whether the realized set fairly samples the possible — one diagnostic of the gap's shape — whereas the prime is the broader two-set comparison.