PFES — Prediction Feasibility Standard

Architecture Ecosystem: Structured Reality Standards™

Architecture Family: PGA™ — Prediction Governance Architecture

Operational Layer: Prediction Feasibility Governance Layer

Category:

Governance & Enforcement

Subcategory:

Prediction Governance

Type: Parent Standard

Governed Space:

Prediction Feasibility

Origin ID: OOF-PGA-PFES

Version: 1.0

Status: Canonical · Open Standard

Effective Date: 9 September 2026

Compatibility: OOF® Methodology OS™ · GOA™ · ORA™ · VALIDOS™ · INTEGROS® · ADIT® · AGA™ · AIG® · ASGA™ · CLIA® · SIMULOS®

AI-Readable: Yes

Authority: OOF®

Protection:

MIP® — Methodological Intellectual Property

Canonical Language:

English (UCL™)

Governed Space

Prediction Feasibility

Canonical Definition

Prediction Feasibility Standard (PFES) defines the governance conditions under which a Governed Prediction is assessed to determine whether the predicted outcome is realistically achievable under its stated assumptions, constraints, Prediction Horizon, Prediction Basis, applicable operational conditions, and relevant dependencies.

PFES governs the distinction between an outcome being theoretically possible, plausibly imaginable, operationally achievable, and probabilistically likely.

It determines whether the conditions necessary for the predicted outcome can coexist within the applicable operational environment and whether known constraints materially prevent, restrict, or condition that outcome.

PFES does not determine whether the predicted outcome will occur.

It governs whether the predicted outcome can legitimately be treated as feasible .

Core Question

Is the predicted outcome realistically achievable under the stated assumptions, constraints, time horizon, Prediction Basis, and relevant conditions?

Foundational Principle

An outcome may be possible without being feasible, and feasible without being probable.

Architecture Position

PFES is the seventh governed space within the PGA™ — Prediction Governance Architecture .

It receives a Governed Prediction after:

the prediction has been formed; probability and uncertainty have been represented; relevant assumptions have been identified; applicable predictive conditions have been established.

PFES introduces a distinct governance test:

Can the predicted outcome actually be achieved within the world in which the prediction claims it can occur?

PGA™ Governance Flow

Prediction Object & Purpose → Prediction Methodology → Prediction Basis → Prediction Assumptions → Prediction Formation → Prediction Probability & Uncertainty → Prediction Feasibility → Collective Prediction where applicable → Communication & Reliance → Monitoring & Revision → Outcome & Performance → Prediction Record & Continuity

Current Position: Prediction Feasibility

Prediction Feasibility

Prediction Feasibility represents the governed assessment of whether a predicted outcome is realistically achievable within the constraints and conditions relevant to that prediction.

Feasibility concerns compatibility between:

Predicted Outcome

and:

Operational Conditions Required for That Outcome

Possible ≠ Plausible ≠ Feasible ≠ Probable

These states must remain distinct.

Possible means an outcome is not inherently impossible.

Plausible means an outcome can reasonably be contemplated given available understanding.

Feasible means the outcome can realistically be achieved under applicable constraints, resources, dependencies, timing, and conditions.

Probable concerns estimated likelihood that the outcome will occur.

Possibility

Possibility establishes only that an outcome is not ruled out by known absolute constraints.

Possibility alone does not establish operational achievability.

Plausibility

Plausibility concerns whether an outcome is reasonably coherent with available understanding.

A plausible outcome may remain infeasible because critical operational conditions cannot be satisfied.

Feasibility

Feasibility requires that necessary enabling conditions are sufficiently compatible with the prediction.

These may include:

time; resources; capacity; authority; infrastructure; technology; dependencies; human capability; regulatory conditions; physical constraints; economic constraints; operational sequencing.

Probability

Probability does not replace feasibility.

A prediction may assign high probability to an outcome while failing to account for a hard operational constraint.

Similarly, a feasible outcome may have low probability.

Feasible ≠ Probable

Low Probability ≠ Infeasible

An outcome may be difficult or unlikely while remaining fully achievable.

High Probability ≠ Feasible by Default

A probability estimate does not override a binding operational constraint.

Feasibility Object

PFES requires an identifiable feasibility object.

The feasibility object is the specific predicted outcome whose achievability is being assessed.

Outcome Definition

Feasibility cannot be governed where the predicted outcome is materially undefined.

The assessment must remain associated with the Governed Prediction established through PFOS.

Feasibility Horizon

Feasibility is horizon-dependent.

An outcome may be infeasible within:

3 months

but feasible within:

3 years.

Feasible at Horizon A ≠ Feasible at Horizon B

Feasibility Boundary

The applicable predictive boundary materially affects feasibility.

Example boundaries may include:

geographic scope; organizational scope; system scope; production environment; population; jurisdiction; market; infrastructure domain.

Constraint

A Constraint is a condition that limits, restricts, prevents, or materially shapes the ability to achieve the predicted outcome.

Constraint Types

Relevant constraints may include:

physical; technological; resource; capacity; financial; temporal; legal; regulatory; organizational; infrastructural; logistical; dependency; environmental; human; authority-related.

Hard Constraint

A Hard Constraint prevents the predicted outcome unless the constraint itself changes.

Examples may include:

physical impossibility; missing mandatory authority; insufficient minimum capacity; unavailable essential infrastructure; incompatible system limit.

Soft Constraint

A Soft Constraint reduces achievability without making the outcome impossible.

Examples may include:

limited staffing; increased cost; resource competition; schedule pressure; implementation complexity.

Hard Constraint ≠ Low Probability

A binding hard constraint may render an outcome infeasible regardless of an otherwise high probability estimate.

Constraint State

Constraints may be:

Active

Potential

Conditional

Emerging

Resolved

Unable to Determine

Constraint Interaction

Multiple constraints may interact.

A collection of individually manageable constraints may become collectively prohibitive.

Individually Manageable Constraints ≠ Collectively Feasible Conditions

Resource Feasibility

Predicted outcomes may require sufficient:

capital; materials; energy; compute; personnel; time; equipment; data; infrastructure.

Resource availability must be assessed relative to the predicted outcome and horizon.

Resource Availability ≠ Resource Accessibility

Resources may exist but remain unavailable to the actor or system responsible for producing the predicted outcome.

Capacity Feasibility

Capacity concerns whether available systems, people, infrastructure, or processes can support the required scale or rate of execution.

Required Capacity > Available Capacity

Where required capacity materially exceeds available capacity and no credible capacity transition exists, feasibility may be restricted or absent.

Capacity Expansion

Predictions may depend upon future capacity expansion.

Such expansion must remain distinguishable from currently available capacity.

Planned Capacity ≠ Available Capacity

Temporal Feasibility

Temporal Feasibility asks whether the required sequence of actions can realistically occur within the Prediction Horizon.

Time Available ≠ Time Required

A prediction may be technically achievable while temporally infeasible.

Sequence Feasibility

Some outcomes depend upon actions occurring in a required order.

Example:

Approval → Procurement → Construction → Testing → Deployment

If required steps cannot be completed in the available horizon, the outcome may be infeasible within that horizon.

Dependency Feasibility

A prediction may depend upon external actors, systems, permissions, events, or resources.

PFES governs whether those dependencies are compatible with achieving the predicted outcome.

Dependency Exists ≠ Dependency Will Be Satisfied

Critical Dependency

A dependency is critical where failure to satisfy it would materially prevent the predicted outcome.

Dependency Chain

Multiple dependencies may form a chain.

The feasibility of the final outcome may depend upon the weakest critical link.

Parallel Dependencies

Several dependencies may need to be satisfied simultaneously.

Their interaction must remain governable.

Authority Feasibility

Some predicted outcomes require legal, organizational, contractual, or system authority.

An actor's ability to perform an action must not be assumed merely because the action is operationally desirable.

Operational Capability ≠ Authority to Act

Permission Feasibility

Required permissions may include:

regulatory approval; contractual consent; access permission; system authorization; governance approval; licensing.

Regulatory Feasibility

A technically achievable outcome may be infeasible within a jurisdiction if legally required approvals cannot be obtained within the applicable conditions or horizon.

PFES does not determine law.

It governs regulatory dependency as a feasibility condition.

Technical Feasibility

Technical Feasibility concerns whether required technology, systems, interfaces, or engineering capability can support the predicted outcome.

Technology Exists ≠ Technology Is Deployable

A technology may exist experimentally while remaining unsuitable for the predicted operational environment.

Operational Feasibility

Operational Feasibility concerns whether the outcome can function in real operational conditions rather than only in conceptual, experimental, or simulated environments.

Demonstrated Prototype ≠ Operational Feasibility

Infrastructure Feasibility

Required infrastructure must be sufficiently available, compatible, and accessible.

Examples include:

energy; network; transportation; cloud; manufacturing; storage; physical facilities.

Economic Feasibility

An outcome may be technically possible but economically impractical within the prediction's stated conditions.

PFES may govern economic constraints where they determine achievability.

It does not independently govern economic value.

Economic Feasibility ≠ Economic Desirability

An outcome may be economically achievable without being commercially attractive.

Human Feasibility

Predicted outcomes may require human:

expertise; availability; training; coordination; decision-making; sustained performance.

Human Capacity ≠ Unlimited Operational Capacity

Behavioral Feasibility

Some predicted outcomes depend upon humans or organizations behaving in particular ways.

PFES may assess whether the required behavioral conditions are realistically compatible with the prediction.

It does not determine future behavior.

Environmental Feasibility

Physical or environmental conditions may constrain achievability.

Examples include:

weather; temperature; terrain; natural-resource availability; environmental restrictions.

System Feasibility

For digital, AI, autonomous, or technical systems, feasibility may depend upon:

compute availability; latency; memory; interoperability; integration; data access; system reliability; control boundaries.

Interoperability Feasibility

An outcome requiring incompatible systems to operate together may be infeasible without an identified integration mechanism.

Scale Feasibility

An outcome demonstrated at small scale may not remain feasible at production scale.

Prototype Feasibility ≠ Scale Feasibility

Local Feasibility ≠ System-Wide Feasibility

An outcome may be feasible for one component while infeasible across the entire system.

Feasibility Assumptions

PAS governs Predictive Assumptions.

PFES consumes relevant assumptions when determining whether required conditions can coexist.

It does not redefine those assumptions.

Feasibility and Prediction Basis

PBAS governs Prediction Basis.

PFES uses applicable governed information when assessing feasibility.

Feasibility and Probability

PPUS governs Probability and Uncertainty.

PFES does not modify probability merely because an outcome is feasible or infeasible.

However, material feasibility findings may create a reason for later prediction reassessment.

Probability ≠ Feasibility

This distinction is mandatory.

Feasibility and Uncertainty

Uncertainty about a constraint may result in conditional feasibility rather than a definitive feasible or infeasible state.

Unknown Constraint State ≠ Constraint Absent

Conditional Feasibility

An outcome may be feasible only if specified conditions hold.

Example:

Feasible if regulatory approval is obtained by June and production capacity increases by 20%.

Conditional Feasibility ≠ Unconditional Feasibility

Feasibility Condition

A Feasibility Condition is a condition that must be satisfied for the predicted outcome to remain operationally achievable.

Feasibility Threshold

Some constraints have identifiable thresholds.

Example:

minimum capacity; maximum latency; minimum funding; minimum staffing;

latest approval date.

Crossing such a threshold may materially change the feasibility state.

Feasibility Margin

Feasibility Margin represents the distance between required conditions and limiting constraints where this can legitimately be determined.

A prediction operating close to a critical constraint may remain feasible while carrying low margin.

Feasible ≠ Robustly Feasible

Robust Feasibility

An outcome may be considered more robustly feasible where reasonable variation in conditions does not cause feasibility failure.

Fragile Feasibility

Fragile Feasibility exists where small changes in one or more conditions could render the predicted outcome infeasible.

Feasibility Sensitivity

PFES may assess which constraints most strongly affect feasibility.

Dominant Feasibility Constraint

A Dominant Feasibility Constraint is a constraint with disproportionate influence over whether the predicted outcome can be achieved.

Constraint Concentration

Many apparently independent feasibility factors may depend upon one shared constraint.

Feasibility Composition

Overall feasibility may depend upon the combination of multiple dimensions.

A prediction should not automatically be labeled feasible merely because one dimension is feasible.

Technical Feasibility ≠ Overall Prediction Feasibility

Feasibility Conflict

Different legitimate assessments may reach different feasibility conclusions because they use different:

constraints; boundaries; assumptions;

horizons; operational conditions.

The disagreement must remain attributable.

Feasibility Disagreement ≠ Governance Failure

Feasibility State

PFES supports governed states such as:

Feasible

Conditionally Feasible

Feasibility Restricted

Feasibility Uncertain

Infeasible

Unable to Determine

Feasible

The relevant constraints and conditions do not currently prevent realistic achievement of the predicted outcome within the applicable horizon and boundary.

Conditionally Feasible

The predicted outcome is achievable only if identified conditions are satisfied.

Feasibility Restricted

The outcome may remain achievable, but material constraints significantly limit the conditions under which it can occur.

Feasibility Uncertain

Available information is insufficient to determine whether relevant constraints can be satisfied.

Infeasible

One or more material constraints prevent realistic achievement of the predicted outcome under the stated conditions, horizon, and boundary.

Unable to Determine

There is insufficient governed basis to establish a legitimate feasibility state.

Unable to Determine ≠ Feasible

Absence of proof of infeasibility does not establish feasibility.

Infeasible ≠ Impossible

An outcome assessed as infeasible under current conditions may become feasible if relevant conditions change.

Current Feasibility ≠ Permanent Feasibility

Feasibility Change

Feasibility may change when:

constraints are removed; capacity expands; permissions are granted; technology matures; resources become available; conditions deteriorate; dependencies fail.

Feasibility Change ≠ Prediction Revision by Default

A material feasibility change may create a trigger for PMRS review.

Historical Feasibility State

The feasibility state associated with a prediction at a particular lifecycle point must remain reconstructable.

Later Capability ≠ Historical Feasibility

An outcome that becomes feasible later must not be retroactively treated as feasible at the earlier prediction state.

Operational Reality Relationship

ORA™ governs Operational Reality.

PFES may consume sufficiently governed operational conditions in determining feasibility.

PFES does not establish Operational Reality itself.

Feasibility Assessment ≠ Operational Reality Determination

Validation Relationship

VALIDOS™ may govern validation processes relevant to systems or claims used in feasibility analysis.

PFES does not replace independent validation governance.

Evidence Relationship

ADIT® governs evidence.

PFES may rely upon governed evidence references without owning evidence validity.

Integrity Relationship

INTEGROS® may govern integrity conditions relevant to supporting information or systems.

PFES governs Prediction Feasibility only.

Governance Relationship

GOA™ governs broader governance architecture.

PFES governs the predictive question of whether a specific predicted outcome is operationally achievable.

Prediction Monitoring Relationship

PMRS later governs whether changing feasibility requires prediction review, revision, supersession, or withdrawal.

PFES establishes the feasibility state and material changes relevant to that later lifecycle decision.

Prediction Performance Relationship

POFPS later governs whether the prediction aligned with governed outcome.

PFES does not determine predictive performance.

A prediction may concern a feasible outcome and still be wrong.

A prediction may concern an infeasible outcome and later become outdated because conditions changed.

Feasibility Governance Requirements

PFES requires that:

1. feasibility remain associated with a specific Governed Prediction; 2. the predicted outcome being assessed remain identifiable; 3. Prediction Horizon remain explicit; 4. Predictive Boundary remain identifiable; 5. possibility remain distinguishable from plausibility; 6. plausibility remain distinguishable from feasibility; 7. feasibility remain distinguishable from probability; 8. low probability not automatically imply infeasibility; 9. high probability not automatically imply feasibility; 10. material constraints remain identifiable; 11. hard and soft constraints remain distinguishable where material; 12. constraint state remain governable; 13. interacting constraints remain assessable; 14. resource requirements remain identifiable where material; 15. resource availability remain distinguishable from resource accessibility; 16. required and available capacity remain distinguishable; 17. planned capacity remain distinguishable from available capacity;

18. temporal feasibility remain assessed where timing is material; 19. required operational sequence remain identifiable where material; 20. critical dependencies remain identifiable; 21. dependency chains remain governable; 22. authority and permission constraints remain identifiable where material; 23. technical feasibility remain distinguishable from operational feasibility; 24. prototype feasibility remain distinguishable from scale feasibility; 25. local feasibility remain distinguishable from system-wide feasibility; 26. economic constraints remain representable where they affect achievability; 27. behavioral and human constraints remain representable where material; 28. infrastructure constraints remain identifiable; 29. conditional feasibility preserve applicable conditions; 30. uncertainty concerning constraints remain visible; 31. inability to determine feasibility remain a legitimate state; 32. absence of an identified constraint not automatically establish feasibility; 33. dominant feasibility constraints remain identifiable where possible; 34. fragile feasibility remain distinguishable from robust feasibility where material; 35. material feasibility changes remain traceable; 36. historical feasibility states remain reconstructable; 37. later capability not overwrite historical feasibility; 38. feasibility assessment remain distinct from Operational Reality determination.

Governance Logic

PFES applies the following architecture-level governance logic:

Governed Prediction

Governed Probability & Uncertainty Representation

Governed Predictive Assumptions

Relevant Prediction Basis

Applicable Operational Conditions

↓

Predicted Outcome Identified

↓

Prediction Horizon and Boundary Confirmed

↓

Required Conditions Identified

↓

Material Constraints Identified

↓

Hard / Soft Constraint Structure Assessed

↓

Resource / Capacity Conditions Assessed

↓

Temporal and Sequence Conditions Assessed

↓

Dependency Conditions Assessed

↓

Authority / Permission Conditions Assessed

↓

Technical / Operational / Infrastructure Conditions Assessed

↓

Human / Behavioral / Economic / Environmental Conditions Assessed where applicable

↓

Constraint Interaction and Concentration Assessed

↓

Feasibility Sensitivity Assessed

↓

Conditionality and Uncertainty Assessed

↓

Feasibility State Established

↓

Historical Feasibility State Preserved

↓

Governed Prediction Feasibility Determination

↓

CPGS — Collective Prediction Governance Standard where applicable

or:

PCRS — Prediction Communication & Reliance Standard

Where sufficient feasibility determination cannot be established:

Prediction Feasibility Governance Gap → Clarification / Additional Constraint Analysis / Conditional Feasibility / Restricted Feasibility / Unable to Determine

Governance Outputs

PFES may produce:

Governed Prediction Feasibility Determination; Feasibility State; Feasibility Constraint Record; Constraint Classification;

Hard Constraint Record; Soft Constraint Record; Critical Dependency Record; Capacity Feasibility State; Resource Feasibility State; Temporal Feasibility State; Sequence Feasibility State; Technical Feasibility State; Operational Feasibility State; Infrastructure Feasibility State; Economic Feasibility State where applicable; Authority Feasibility State; Permission Feasibility State; Conditional Feasibility Record; Feasibility Condition Set; Feasibility Threshold; Feasibility Margin; Dominant Feasibility Constraint; Feasibility Sensitivity Record; Feasibility Conflict; Feasibility Governance Gap; historical feasibility state; Feasibility Change Record.

Critical Distinctions

Possible ≠ Plausible ≠ Feasible ≠ Probable

Feasible ≠ Probable

Low Probability ≠ Infeasible

High Probability ≠ Feasible by Default

Feasible at Horizon A ≠ Feasible at Horizon B

Hard Constraint ≠ Low Probability

Individually Manageable Constraints ≠ Collectively Feasible Conditions

Resource Availability ≠ Resource Accessibility

Planned Capacity ≠ Available Capacity

Time Available ≠ Time Required

Dependency Exists ≠ Dependency Will Be Satisfied

Operational Capability ≠ Authority to Act

Technology Exists ≠ Technology Is Deployable

Demonstrated Prototype ≠ Operational Feasibility

Economic Feasibility ≠ Economic Desirability

Prototype Feasibility ≠ Scale Feasibility

Local Feasibility ≠ System-Wide Feasibility

Probability ≠ Feasibility

Unknown Constraint State ≠ Constraint Absent

Conditional Feasibility ≠ Unconditional Feasibility

Feasible ≠ Robustly Feasible

Technical Feasibility ≠ Overall Prediction Feasibility

Feasibility Disagreement ≠ Governance Failure

Unable to Determine ≠ Feasible

Infeasible ≠ Impossible

Current Feasibility ≠ Permanent Feasibility

Feasibility Change ≠ Prediction Revision by Default

Later Capability ≠ Historical Feasibility

Feasibility Assessment ≠ Operational Reality Determination

Canonical Boundary

PFES governs whether a specific predicted outcome is realistically achievable under the applicable Prediction Horizon, Predictive Boundary, Prediction Basis, Predictive Assumptions, operational conditions, dependencies, resources, capacity, authority, permissions, technological capability, infrastructure, timing, sequencing, and other material constraints. It does not govern Prediction Formation, Probability Representation, Predictive Uncertainty, Confidence Representation, Collective Prediction composition, communication and reliance, prediction-level monitoring or revision, Operational Reality determination, evidence validity, outcome determination, or predictive performance assessment.

PFES governs:

whether the predicted outcome can realistically be achieved under the conditions in which the prediction claims it can occur.

It does not determine:

whether that outcome will actually occur.

Canonical Closing Statement

Probability asks how likely an outcome is. Feasibility asks whether the outcome can actually be achieved.

PFES prevents predictions from treating theoretical possibility, statistical likelihood, or conceptual plausibility as substitutes for operational achievability.

A predicted future should not be treated as feasible until the conditions required to make it possible can coexist in operational reality.

About standard

About the Prediction Feasibility Standard

What Is the Prediction Feasibility Standard?

The Prediction Feasibility Standard (PFES) is the seventh Parent Standard within the PGA™ — Prediction Governance Architecture .

PFES governs whether a Governed Prediction is realistically achievable under the assumptions, constraints, Prediction Horizon, Prediction Basis, operational conditions, dependencies, resources, capacity, authority, permissions, technology, infrastructure, timing, and other conditions relevant to the predicted outcome.

Its purpose is not to determine whether the predicted outcome will occur.

Its purpose is to determine whether that outcome can legitimately be treated as feasible .

The central question is:

Is the predicted outcome realistically achievable under the stated assumptions, constraints, time horizon, Prediction Basis, and relevant conditions?

Why the Standard Exists

Predictions frequently express what appears statistically likely without asking whether the predicted outcome can actually be achieved.

A model may estimate:

80% probability of completion by December.

But that probability may coexist with:

insufficient production capacity; missing regulatory approval; unavailable infrastructure; impossible sequencing; insufficient time; absent legal authority; unresolved critical dependencies.

A high probability does not remove these constraints.

PFES therefore introduces a separate governance layer between:

what is predicted

and:

whether that predicted outcome is operationally achievable.

Possible ≠ Plausible ≠ Feasible ≠ Probable

PFES separates four concepts that are frequently collapsed.

Possible means that an outcome is not absolutely ruled out.

Plausible means that the outcome can reasonably be contemplated.

Feasible means that the outcome can realistically be achieved within applicable constraints and conditions.

Probable concerns how likely the outcome is estimated to be.

These concepts may overlap.

They are not interchangeable.

Probability Does Not Establish Feasibility

A prediction can be:

high probability but infeasible

if the probability estimate failed to incorporate a binding constraint.

It can also be:

low probability but fully feasible

where the outcome is difficult or unlikely but remains realistically achievable.

Therefore:

Feasible ≠ Probable

Low Probability ≠ Infeasible

High Probability ≠ Feasible by Default

What PFES Governs

PFES governs the feasibility relationship between a predicted outcome and the conditions required for that outcome to be achieved.

This may include:

resource feasibility; capacity feasibility; temporal feasibility; sequencing feasibility; dependency feasibility; technical feasibility; operational feasibility; infrastructure feasibility; authority and permission feasibility; regulatory constraints; economic constraints where they affect achievability; human capability; behavioral conditions; environmental constraints; system interoperability; scale constraints.

PFES does not require every prediction to involve every feasibility dimension.

Only dimensions materially relevant to the predicted outcome need to be governed.

Prediction Horizon Matters

Feasibility is time-dependent.

An outcome may be infeasible within three months and feasible within three years.

For example:

A production increase of 50% may be impossible with current equipment this quarter but entirely feasible after planned capacity expansion next year.

Therefore:

Feasible at Horizon A ≠ Feasible at Horizon B

Constraints Matter

PFES identifies the constraints capable of limiting or preventing the predicted outcome.

A constraint may be:

Hard — the outcome cannot realistically be achieved unless the constraint changes.

or:

Soft — the outcome remains achievable, but the constraint materially restricts how or under what conditions it can occur.

A feasibility assessment should not treat all constraints as equivalent.

Capacity Matters

Many predictions assume future capacity without distinguishing it from current capacity.

PFES requires that:

Planned Capacity ≠ Available Capacity

A prediction depending upon future capacity expansion must remain explicit about that dependency.

Resources Matter

The existence of a resource does not establish that it can be used.

For example:

capital may exist but remain unavailable;

infrastructure may exist but be inaccessible;

personnel may exist but lack required capability.

Therefore:

Resource Availability ≠ Resource Accessibility

Timing and Sequence Matter

Some outcomes require multiple actions to occur in a defined order.

For example:

Approval → Procurement → Construction → Testing → Deployment

Even where every step is technically possible, the predicted final outcome may remain infeasible if those steps cannot be completed within the Prediction Horizon.

Dependencies Matter

Predictions may depend upon actors or systems outside the predictor's direct control.

Examples include:

suppliers; regulators; financial institutions; external infrastructure; counterparties; public authorities; technology providers.

A dependency being identified does not establish that it will be satisfied.

Dependency Exists ≠ Dependency Will Be Satisfied

Authority and Permission Matter

An actor may be capable of performing an action without having authority to perform it.

PFES therefore distinguishes:

Operational Capability ≠ Authority to Act

Where a predicted outcome depends upon approval, licensing, access permission, contractual consent, or another form of authority, that requirement belongs within feasibility governance.

Technical Feasibility Is Not Enough

A technology may work in a laboratory while remaining unsuitable for deployment.

A prototype may succeed while the same system fails at production scale.

Therefore:

Technology Exists ≠ Technology Is Deployable

Demonstrated Prototype ≠ Operational Feasibility

Prototype Feasibility ≠ Scale Feasibility

Conditional Feasibility

Some outcomes are feasible only if defined conditions are satisfied.

Example:

Feasible if regulatory approval is obtained by June and production capacity increases by 20%.

PFES can preserve that state as:

Conditionally Feasible

rather than incorrectly classifying the outcome as simply feasible or infeasible.

Feasibility States

PFES may distinguish states such as:

Feasible

Conditionally Feasible

Feasibility Restricted

Feasibility Uncertain

Infeasible

Unable to Determine

The last state is important.

A lack of sufficient information does not justify assuming feasibility.

Unable to Determine ≠ Feasible

Feasibility Can Change

Feasibility is not necessarily permanent.

An outcome may become feasible when:

a constraint is removed; infrastructure becomes available; capacity expands; technology matures; permission is granted.

It may become infeasible when:

capacity deteriorates; regulation changes; a critical supplier fails; resources disappear.

Therefore:

Current Feasibility ≠ Permanent Feasibility

Feasibility and Operational Reality

PFES may rely upon governed operational conditions supplied through ORA™ — Operational Reality Architecture or another sufficiently governed source.

PFES does not itself determine Operational Reality.

It governs the feasibility conclusion derived from conditions relevant to the prediction.

Feasibility Assessment ≠ Operational Reality Determination

What PFES Does Not Govern

PFES does not govern:

what the prediction itself is; how the prediction was formed; Prediction Methodology; Prediction Basis; Predictive Assumption identification; probability calculation; Predictive Uncertainty representation; Confidence Representation; Collective Prediction composition; communication and reliance; prediction-level revision decisions; Operational Reality determination; outcome determination; predictive performance.

Its governed space is narrower:

whether the predicted outcome is realistically achievable under the applicable conditions.

Position Within PGA™

PFES follows the governance of Probability and Uncertainty.

The PGA™ governance sequence is:

PFES therefore adds a crucial question after the prediction and its uncertainty have been defined:

Even if this is the prediction, can this future actually be achieved under the conditions in which the prediction claims it can occur?

Where Collective Prediction does not apply, the lifecycle may proceed directly from:

Prediction Feasibility → Communication & Reliance

Why PFES Matters

Without feasibility governance, organizations may rely on predictions that are statistically impressive but operationally impossible.

PFES forces predictive systems to confront:

real constraints; resource limits; required capacity; timing; dependencies; permissions; physical limitations; infrastructure; scale.

It therefore creates a bridge between prediction and operational achievability.

A strong prediction should not merely say:

what may happen.

It should also make clear whether the predicted outcome can actually exist within the conditions required to produce it.

Use Case 1 — High Probability, but the Factory Cannot Produce Enough

A manufacturing forecast states:

85% probability that production will reach 1.5 million units next year.

The prediction is supported by strong demand data and historically reliable sales forecasting.

However, the current manufacturing system can produce a maximum of:

1.1 million units

and the planned additional production line will not become operational until the following year.

The critical governance question is:

Can an outcome legitimately be treated as highly probable when the operational capacity required to produce that outcome does not exist within the Prediction Horizon?

PFES identifies the capacity constraint and distinguishes:

Demand Probability

from:

Production Feasibility

The prediction may remain methodologically valid as an estimate of demand.

The predicted production outcome, however, cannot be treated as feasible under the stated capacity conditions.

High Probability ≠ Feasible by Default

Use Case 2 — Technically Possible, but the Required Approval Cannot Arrive in Time

An infrastructure project is predicted to begin commercial operation by:

December 2028.

Engineering teams confirm that construction can be completed in approximately fourteen months.

The prediction therefore appears technically achievable.

However, construction cannot legally begin until a mandatory public approval process is complete.

The approval process itself has a minimum statutory duration that means the earliest realistic construction start leaves insufficient time to complete the project by December 2028.

The critical governance question is:

Is a technically achievable project feasible within the predicted horizon when a mandatory dependency makes the required execution sequence impossible?

PFES separates:

Technical Feasibility

from:

Overall Prediction Feasibility

and evaluates the approval dependency, required sequence, and available time.

Time Available ≠ Time Required

Technical Feasibility ≠ Overall Prediction Feasibility

Canonical Boundary

PFES governs:

whether the predicted outcome can realistically be achieved under the conditions in which the prediction claims it can occur.

It does not determine:

whether that outcome will actually occur.

Canonical Closing Statement

A future can be imaginable, plausible, and even statistically likely while still being operationally unreachable.

PFES connects prediction to the constraints, capacity, timing, dependencies, authority, and conditions that determine whether the predicted outcome can actually be achieved.

Probability describes likelihood. Feasibility establishes whether the predicted future has a realistic path to existence.

Governed Links

About Prediction Feasibility Standard (PFES)
Feasibility Condition Identification Module (FCIM)
Prediction Constraint Mapping Module (PCMM)
Operational Plausibility Assessment Module (OPAM)
Execution & Outcome Feasibility Module (EOFM)
Feasibility State Determination Module (FSDM)

←