FSDM — Feasibility State Determination Module
Architecture Ecosystem: Structured Reality Standards™
Architecture Family: PGA™ — Prediction Governance Architecture
Parent Standard:
Prediction Feasibility Standard (PFES)
Operational Layer: Prediction Feasibility Governance Layer
Category:
Governance & Enforcement
Subcategory:
Prediction Governance
Type: Parent Standard Module
Governed Space:
Feasibility State Determination
Version: 1.0
Status: Canonical · Open Module
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
Feasibility State Determination
Canonical Definition
Feasibility State Determination Module (FSDM) defines the governance conditions under which the outputs of feasibility constraint identification, predictive constraint mapping, operational pathway assessment, and execution and outcome feasibility assessment are integrated into a governed determination of the feasibility state of a specific predicted outcome.
FSDM establishes whether the predicted outcome may legitimately be represented as:
Feasible
Conditionally Feasible
Feasibility Restricted
Feasibility Uncertain
Infeasible
or:
Unable to Determine
within the applicable Prediction Horizon, Predictive Boundary, Prediction Basis, Predictive Assumptions, constraint structure, operational pathway, execution conditions, and outcome requirements.
It transforms:
Governed Feasibility Constraint Set + Governed Predictive Constraint Map + Governed Operational Pathway Assessment + Governed Execution & Outcome Feasibility Assessment
into:
Governed Prediction Feasibility Determination
Its foundational principle is:
Feasibility is a governed conclusion derived from the complete feasibility structure — not a label inferred from one favorable condition.
Operational Role
FSDM is the fifth and final internal governance space of the Prediction Feasibility Standard (PFES) .
FCIM establishes:
what constraints exist.
PCMM establishes:
how those constraints are connected.
OPAM establishes:
whether a viable operational pathway exists.
EOFM establishes:
whether that pathway can actually deliver the required outcome.
FSDM establishes:
what feasibility state the prediction may legitimately carry.
The focused operational question is:
Given the complete governed feasibility structure, what feasibility state can legitimately be assigned to the predicted outcome?
The primary output is:
Governed Prediction Feasibility Determination
Internal Module Flow
Feasibility Constraint Identification → Predictive Constraint Mapping → Operational Pathway Assessment → Execution & Outcome Feasibility → Feasibility State Determination
Current Position: Feasibility State Determination
Feasibility Determination
A Feasibility Determination is a governed conclusion concerning whether the predicted outcome is realistically achievable under the applicable conditions.
It must remain associated with:
a specific prediction; a specific predicted outcome; a specific Prediction Horizon; a specific Predictive Boundary; the feasibility information available at the time of determination.
Feasibility Determination ≠ Prediction Probability
FSDM does not determine how likely the outcome is.
It determines whether the outcome can realistically be achieved.
Feasibility Determination ≠ Prediction Validation
A prediction may be methodologically valid while the predicted outcome remains infeasible.
Feasibility State
A Feasibility State is the governed classification assigned to the predicted outcome after relevant feasibility conditions have been assessed.
Feasible
A predicted outcome may be classified as Feasible where:
no known material hard constraint prevents achievement;
a viable operational pathway exists; required execution capability is sufficiently available; required conditions can coexist; relevant dependencies can be satisfied within the applicable horizon; no unresolved feasibility condition materially prevents the outcome.
Feasible does not mean certain.
Feasible ≠ Certain
Conditionally Feasible
A predicted outcome is Conditionally Feasible where achievement is realistic only if one or more explicit conditions are satisfied.
Example:
Conditionally Feasible if regulatory approval is obtained by 30 June and required production capacity becomes operational by 1 September.
Conditional Feasibility Requires Explicit Conditions
A conditional state must not hide the conditions upon which feasibility depends.
Conditionally Feasible ≠ Feasible Without Qualification
Feasibility Restricted
A prediction may be Feasibility Restricted where the outcome remains achievable only with material restrictions affecting:
scale; scope; geography; timing; capacity; pathway; resources; operational conditions.
Example:
The predicted deployment is feasible for:
40 locations
but not for the predicted:
100 locations
within the same horizon.
Restricted Feasibility ≠ Full Feasibility
Feasibility Uncertain
A prediction may be classified as Feasibility Uncertain where material feasibility conditions are known but their future state or effect remains sufficiently uncertain to prevent an unqualified feasibility conclusion.
Feasibility Uncertainty ≠ Prediction Uncertainty
PPUS governs Predictive Uncertainty.
FSDM governs uncertainty concerning operational achievability.
Infeasible
A predicted outcome is Infeasible where one or more governed constraints, pathway limitations, execution limitations, or required conditions establish that the outcome cannot realistically be achieved under the applicable horizon and conditions.
Infeasible ≠ Impossible
The outcome may become feasible under:
a different horizon; different resources; different technology; different regulatory conditions; a different operational pathway; a changed Predictive Boundary.
Unable to Determine
A feasibility state of Unable to Determine applies where the governed information is insufficient, materially conflicting, or incomplete to support a legitimate determination.
Unable to Determine ≠ Feasible
Unable to Determine ≠ Infeasible
Insufficient information does not justify either conclusion.
Feasibility Qualification
Every feasibility state should carry any material qualification needed to interpret it correctly.
Qualified Feasible State
Example:
Feasible within the current infrastructure capacity and for deployment limited to Region A.
Unqualified Feasibility
An unqualified Feasible state should not be assigned where material unresolved conditions remain.
Feasibility Basis
The Feasibility Basis is the governed set of outputs and conditions supporting the determination.
It may include:
constraint set; constraint map; operational pathway; execution assessment; outcome thresholds; applicable assumptions; relevant operational conditions.
Feasibility Basis ≠ Prediction Basis
PBAS governs the Prediction Basis used to form the prediction.
FSDM governs the basis supporting the feasibility conclusion.
Feasibility Condition Set
A Feasibility Condition Set identifies the conditions that must hold for a particular feasibility state to remain legitimate.
Necessary Condition
A Necessary Condition must be satisfied for the relevant feasibility state to remain valid.
Supporting Condition
A Supporting Condition strengthens feasibility but is not independently required.
Necessary Condition ≠ Supporting Condition
Sufficient Condition
Where methodology supports it, a condition or combination of conditions may be sufficient to establish a particular feasibility conclusion.
Condition Interaction
Several individually satisfactory conditions may fail when combined.
Individually Satisfied Conditions ≠ Overall Feasibility by Default
Hard Constraint Determination
An active non-substitutable Hard Constraint may be sufficient to establish infeasibility under the applicable conditions.
Hard Constraint Exists ≠ Permanent Infeasibility
The state may change if the constraint changes.
Soft Constraint Composition
Multiple soft constraints may collectively prevent achievement.
No Single Hard Constraint ≠ Feasible
Constraint Resolution State
FSDM should distinguish whether material constraints are:
unresolved; mitigated; conditionally resolved; resolved; superseded; unable to determine.
Mitigated ≠ Resolved
Constraint Substitution State
Where an alternative removes one constraint but introduces another, the total feasibility structure must be assessed.
One Constraint Removed ≠ Feasibility Restored
Pathway State Integration
FSDM incorporates the state established by OPAM.
Relevant pathway states may include:
Viable
Conditionally Viable
Restricted
Fragile
Blocked
Incomplete
Unable to Determine
Viable Pathway ≠ Feasible Outcome by Default
Blocked Pathway
A blocked mandatory pathway may establish infeasibility unless a sufficiently viable alternative exists.
Alternative Pathway Requirement
Where the primary pathway is blocked, an alternative must be operationally available rather than merely imaginable.
Theoretical Alternative ≠ Feasibility Restoration
Execution State Integration
FSDM incorporates the state established by EOFM.
Relevant execution states may include:
Executable
Conditionally Executable
Restricted
Fragile
Infeasible
Unable to Determine
Executable Pathway ≠ Required Outcome Achievable by Default
Outcome State Integration
FSDM must account for whether execution can achieve the actual predicted outcome threshold.
Partial Achievement ≠ Full Feasibility
Scale Feasibility
A prediction may be feasible at one scale and infeasible at another.
Feasible at Scale A ≠ Feasible at Scale B
Scope Feasibility
Feasibility may depend upon the predicted scope.
Local Feasibility ≠ Full-Scope Feasibility
Temporal Feasibility
The predicted outcome must be achievable within the applicable Prediction Horizon.
Eventually Feasible ≠ Feasible Within Prediction Horizon
Horizon-Dependent State
A feasibility state is always horizon-relative where timing materially affects achievability.
Feasible at Horizon A ≠ Feasible at Horizon B
Boundary-Dependent State
Feasibility may differ across:
jurisdictions; organizations; systems; markets; populations; geographic regions.
Feasible in Boundary A ≠ Feasible in Boundary B
Resource Feasibility Integration
Resources must be available and accessible when required.
Available Somewhere ≠ Available to the Pathway
Capacity Feasibility Integration
Capacity must be sufficient for required execution.
Planned Capacity ≠ Feasibility-Creating Capacity Until Available
Authority Feasibility Integration
Required authority and permissions must remain accounted for.
Capability Without Authority ≠ Feasible Execution
Regulatory Feasibility Integration
A mandatory regulatory dependency may condition or prevent feasibility.
FSDM does not determine legal validity itself.
Technical Feasibility Integration
Technical capability is only one dimension of overall feasibility.
Technically Feasible ≠ Overall Feasible
Operational Feasibility Integration
The outcome must remain executable under actual operational requirements.
Technical Possibility ≠ Operational Achievability
Economic Feasibility Integration
Where financial or economic limits materially affect achievability, they become part of the feasibility determination.
Economic Feasibility ≠ Commercial Preference
Human Feasibility Integration
Where required human capability or behavior is materially necessary, the feasibility determination should preserve those dependencies.
Infrastructure Feasibility Integration
Required infrastructure must exist or become operational within the applicable pathway and horizon.
Infrastructure Planned ≠ Infrastructure Available
Interoperability Feasibility Integration
Where systems must work together, individual component capability is insufficient.
Components Feasible Individually ≠ Integrated Outcome Feasible
Feasibility Threshold
A Feasibility Threshold is a defined minimum condition required before a particular feasibility classification can be supported.
Threshold Satisfaction
Where a threshold is defined, the determination should preserve whether it is:
Satisfied
Conditionally Satisfied
Not Satisfied
Unable to Determine
Feasibility Margin
Feasibility Margin represents the operational distance between required conditions and limiting constraints or thresholds.
Positive Margin
Relevant capability exceeds the requirement.
Near-Zero Margin
The outcome may remain feasible but fragile.
Negative Margin
The requirement exceeds the governed capability.
Positive Margin in One Dimension ≠ Overall Feasibility Margin
Robust Feasibility
A predicted outcome is Robustly Feasible where reasonable variation in material operational conditions does not immediately cause the outcome to become infeasible.
Fragile Feasibility
Fragile Feasibility exists where the outcome remains achievable only with little tolerance for disruption or variation.
Feasible ≠ Robustly Feasible
Fragile ≠ Infeasible
Feasibility Sensitivity
Feasibility Sensitivity describes how strongly the feasibility state depends upon changes in material conditions.
High Sensitivity
Small changes may materially alter the feasibility state.
Low Sensitivity
Reasonable variation does not materially change the determination.
Feasibility Sensitivity ≠ Prediction Sensitivity
Dominant Feasibility Constraint
A Dominant Feasibility Constraint is the constraint or condition most materially limiting the feasibility state.
Dominant Constraint ≠ Only Constraint
Constraint Concentration
Where many feasibility dimensions depend upon one condition, the determination should preserve that concentration.
High Constraint Concentration ≠ Automatic Infeasibility
It may instead indicate fragility or dependency.
Feasibility Conflict
A Feasibility Conflict exists where sufficiently governed sources or assessments support materially different feasibility conclusions.
Conflict ≠ Average the Conclusions
Conflicting conclusions should remain attributable until reconciled or qualified.
Feasibility Evidence Limitation
Where feasibility depends upon insufficiently governed information, the limitation should remain visible.
Unknown Condition ≠ Satisfied Condition
Incomplete Feasibility Structure
Where a material component of feasibility governance is incomplete, FSDM should not manufacture a definitive conclusion.
Missing Input ≠ Positive Feasibility
Feasibility Determination Confidence
Where useful, the methodology may preserve confidence in the feasibility determination itself.
This must remain distinct from predictive confidence.
Feasibility Determination Confidence ≠ Prediction Confidence
Feasibility State Hierarchy
Feasibility states should not be treated as a simple linear ranking where context is lost.
For example:
Conditionally Feasible
may be stronger than:
Feasibility Uncertain
but only if its conditions are explicit and realistically satisfiable.
State Qualification Matters
The classification without its conditions may misrepresent the actual governed result.
Machine-Readable Feasibility State
The final state should be representable in machine-readable form where appropriate.
Example structure:
Prediction ID → Outcome → Horizon → Boundary → Feasibility State → Conditions → Dominant Constraints → Margin → Sensitivity → Historical Version
Feasibility State ≠ Free-Text Opinion
Historical Feasibility State
Every material feasibility determination should remain historically reconstructable.
Historical State Preservation
The record should preserve:
state; date; applicable horizon; applicable boundary; constraint conditions; pathway state; execution state; qualification; version.
Current Feasibility State ≠ Complete Feasibility History
Later Feasibility ≠ Earlier Feasibility
A predicted outcome that becomes feasible later must not be retroactively represented as feasible when the earlier prediction was made.
Later Capability ≠ Historical Feasibility
Feasibility State Change
A state may change because:
a constraint emerges; a constraint is removed; capacity changes; technology changes; authority is granted;
permission is withdrawn; infrastructure becomes available; an alternative pathway emerges; execution capability changes.
State Change Trigger
A material change may require reassessment.
Feasibility State Change ≠ Prediction Revision by Default
PMRS governs whether the prediction itself should be reviewed, revised, superseded, or withdrawn.
Feasibility Reassessment
A new feasibility determination should preserve the prior state rather than overwrite it.
Reassessment ≠ Historical Replacement
Superseded Feasibility State
A prior state may be superseded while remaining historically valid for its original context.
Current State ≠ Only Legitimate Historical State
Relationship to PFES
FSDM converts the preceding PFES module outputs into the final governed feasibility determination.
It is the decision layer of PFES.
Relationship to PPUS
PPUS governs Probability & Uncertainty.
FSDM does not modify probability because an outcome is feasible or infeasible.
Feasibility ≠ Probability Adjustment
A feasibility conclusion may trigger later prediction review through PMRS, but FSDM itself does not recalculate prediction probability.
Relationship to CPGS
Where Collective Prediction applies, the feasibility state may become an input to collective prediction governance.
Relationship to PCRS
The governed feasibility state should accompany the prediction into communication and reliance governance where material.
Relationship to PMRS
Material feasibility changes may create a trigger for prediction monitoring or revision.
PMRS owns that lifecycle decision.
Relationship to POFPS
POFPS later governs Prediction Outcome & Performance.
FSDM does not determine whether the predicted outcome actually occurred.
Feasible Prediction ≠ Successful Prediction
Infeasible Prediction ≠ Automatically Incorrect Prediction Methodology
An infeasible outcome may reveal a feasibility problem without necessarily proving that every other prediction-governance layer failed.
Relationship to ORA™
ORA™ governs Operational Reality.
FSDM consumes sufficiently governed operational conditions where necessary.
It does not establish reality itself.
Feasibility Determination ≠ Operational Reality Determination
Relationship to ADIT®
ADIT® governs evidence.
FSDM may rely upon evidence-governed inputs but does not determine evidence validity.
Relationship to VALIDOS™
VALIDOS™ governs validation.
Validated components or conditions may support feasibility determination.
Validation alone does not establish overall feasibility.
Validated Components ≠ Validated Feasibility of the Whole Outcome
Relationship to SIMULOS®
SIMULOS® may provide governed simulation results relevant to feasibility.
FSDM may consume those results.
Simulated Feasibility ≠ Governed Feasibility Determination by Default
Governance Requirements
FSDM requires that:
1. every feasibility determination remain associated with a specific Governed Prediction; 2. the predicted outcome remain explicit; 3. the applicable Prediction Horizon remain explicit; 4. the applicable Predictive Boundary remain explicit; 5. the Governed Feasibility Constraint Set remain traceable; 6. the Governed Predictive Constraint Map remain traceable; 7. the Governed Operational Pathway Assessment remain traceable; 8. the Governed Execution & Outcome Feasibility Assessment remain traceable; 9. Feasible remain distinguishable from Certain; 10. Conditional Feasibility require explicit conditions; 11. Conditional Feasibility remain distinguishable from unqualified Feasibility; 12. restricted feasibility remain distinguishable from full feasibility; 13. Feasibility Uncertainty remain distinguishable from Predictive Uncertainty; 14. Infeasible remain distinguishable from Impossible; 15. Unable to Determine remain available as a legitimate state; 16. Unable to Determine not be interpreted as Feasible; 17. Unable to Determine not be interpreted as Infeasible; 18. feasibility qualifications remain attached to the state; 19. material necessary conditions remain identifiable; 20. supporting conditions remain distinguishable from necessary conditions; 21. interacting conditions remain assessable; 22. active hard constraints remain identifiable; 23. absence of a hard constraint not establish feasibility by default; 24. soft constraint composition remain assessable; 25. mitigation remain distinguishable from resolution; 26. removal of one constraint not establish restored feasibility; 27. pathway state remain integrated into the determination; 28. theoretical alternative pathways not establish restored feasibility; 29. execution state remain integrated; 30. outcome threshold remain explicit; 31. partial achievement remain distinguishable from complete outcome feasibility; 32. scale-dependent feasibility remain explicit; 33. scope-dependent feasibility remain explicit; 34. horizon-dependent feasibility remain explicit; 35. boundary-dependent feasibility remain explicit; 36. planned capacity remain distinguishable from available capacity; 37. capability remain distinguishable from authority;
38. technical feasibility remain distinguishable from overall feasibility; 39. infrastructure planning remain distinguishable from operational availability; 40. interoperability requirements remain included where material; 41. feasibility thresholds remain governable; 42. feasibility margins remain representable where available; 43. robust and fragile feasibility remain distinguishable; 44. feasibility sensitivity remain representable where material; 45. dominant constraints remain identifiable where determinable; 46. constraint concentration remain preservable; 47. conflicting feasibility conclusions remain attributable; 48. unknown conditions not be treated as satisfied conditions; 49. incomplete feasibility structure not produce false certainty; 50. feasibility determination confidence remain distinct from Prediction Confidence; 51. feasibility states remain machine-readable where applicable; 52. historical feasibility states remain reconstructable; 53. later feasibility not overwrite earlier feasibility; 54. later capability not be treated as historical capability; 55. material state changes remain traceable; 56. reassessment preserve prior feasibility determinations; 57. feasibility state change remain distinct from prediction-level revision; 58. feasibility remain distinct from Probability; 59. feasibility remain distinct from Operational Reality determination; 60. feasibility remain distinct from outcome and performance determination.
Governance Logic
FSDM applies the following governance logic:
Governed Feasibility Constraint Set
Governed Predictive Constraint Map
Governed Operational Pathway Assessment
Governed Execution & Outcome Feasibility Assessment
Prediction Horizon
Predictive Boundary
Applicable Assumptions and Operational Conditions
↓
Material Constraints Confirmed
↓
Hard / Soft Constraint Structure Evaluated
↓
Constraint Interaction and Concentration Evaluated
↓
Necessary Conditions Confirmed
↓
Operational Pathway State Integrated
↓
Alternative Pathway Availability Assessed
↓
Execution State Integrated
↓
Outcome Threshold and Scope Assessed
↓
Scale Feasibility Assessed
↓
Temporal Feasibility Assessed
↓
Authority / Permission / Regulatory Conditions Assessed
↓
Technical / Operational / Infrastructure Conditions Integrated
↓
Feasibility Margin Assessed where determinable
↓
Fragility / Robustness Assessed
↓
Feasibility Sensitivity Assessed
↓
Material Unknowns and Conflicts Assessed
↓
Feasibility Qualification Established
↓
Feasibility State Determined
↓
Historical Feasibility State Preserved
↓
Governed Prediction Feasibility Determination
↓
Collective Prediction Governance where applicable OR Prediction Communication & Reliance
Where a legitimate final state cannot be established:
Feasibility State Determination Gap → Additional Feasibility Analysis / Condition Clarification / Constraint Resolution Assessment / Restricted Determination / Feasibility Uncertain / Unable to Determine
Minimum Implementation Framework
A minimum implementation of FSDM must establish:
A. Prediction Reference
The applicable Governed Prediction.
B. Predicted Outcome
The exact outcome being assessed.
C. Prediction Horizon
The horizon against which feasibility is determined.
D. Predictive Boundary
The scope within which the determination applies.
E. Constraint Set Reference
The applicable Governed Feasibility Constraint Set.
F. Constraint Map Reference
The applicable Governed Predictive Constraint Map.
G. Operational Pathway State
The applicable OPAM output.
H. Execution & Outcome State
The applicable EOFM output.
I. Necessary Conditions
Material conditions required for the determination.
J. Dominant Constraint / Limiting Condition
Where determinable.
K. Feasibility Qualification
Any scope, scale, timing, dependency, or conditional limitation.
L. Feasibility Margin / Fragility
Where materially determinable.
M. Feasibility State
At minimum:
Feasible / Conditionally Feasible / Feasibility Restricted / Feasibility Uncertain / Infeasible / Unable to Determine
N. Determination Rationale
A traceable explanation of why the state was assigned.
O. Historical Determination Record
The reconstructable state, conditions, version, and determination time.
Governance Outputs
FSDM may produce:
Governed Prediction Feasibility Determination; Feasibility State; Feasibility Qualification; Feasibility Basis Record; Feasibility Condition Set; Necessary Condition Record; Supporting Condition Record; Dominant Feasibility Constraint; Constraint Concentration Record; Feasibility Threshold State; Feasibility Margin; Robust Feasibility State; Fragile Feasibility State; Feasibility Sensitivity Record; Scale Feasibility State; Scope Feasibility State; Horizon Feasibility State; Boundary Feasibility State; Conditional Feasibility Record; Feasibility Restriction Record; Feasibility Uncertainty Record; Infeasibility Record; Unable-to-Determine Record; Feasibility Conflict Record; Feasibility State Determination Gap; Feasibility Determination Rationale; Feasibility State Change Record; historical feasibility state; Feasibility Determination Version.
The primary governed output is:
Governed Prediction Feasibility Determination
which may become an input to:
Collective Prediction Governance where applicable
or directly to:
Prediction Communication & Reliance.
Critical Distinctions
Feasibility Is a Governed Conclusion — Not a Label Inferred From One Favorable Condition
Feasibility Determination ≠ Prediction Probability
Feasibility Determination ≠ Prediction Validation
Feasible ≠ Certain
Conditionally Feasible ≠ Feasible Without Qualification
Restricted Feasibility ≠ Full Feasibility
Feasibility Uncertainty ≠ Prediction Uncertainty
Infeasible ≠ Impossible
Unable to Determine ≠ Feasible
Unable to Determine ≠ Infeasible
Feasibility Basis ≠ Prediction Basis
Necessary Condition ≠ Supporting Condition
Individually Satisfied Conditions ≠ Overall Feasibility by Default
Hard Constraint Exists ≠ Permanent Infeasibility
No Single Hard Constraint ≠ Feasible
Mitigated ≠ Resolved
One Constraint Removed ≠ Feasibility Restored
Viable Pathway ≠ Feasible Outcome by Default
Theoretical Alternative ≠ Feasibility Restoration
Executable Pathway ≠ Required Outcome Achievable by Default
Partial Achievement ≠ Full Feasibility
Feasible at Scale A ≠ Feasible at Scale B
Local Feasibility ≠ Full-Scope Feasibility
Eventually Feasible ≠ Feasible Within Prediction Horizon
Feasible at Horizon A ≠ Feasible at Horizon B
Feasible in Boundary A ≠ Feasible in Boundary B
Available Somewhere ≠ Available to the Pathway
Planned Capacity ≠ Feasibility-Creating Capacity Until Available
Capability Without Authority ≠ Feasible Execution
Technically Feasible ≠ Overall Feasible
Technical Possibility ≠ Operational Achievability
Economic Feasibility ≠ Commercial Preference
Infrastructure Planned ≠ Infrastructure Available
Components Feasible Individually ≠ Integrated Outcome Feasible
Positive Margin in One Dimension ≠ Overall Feasibility Margin
Feasible ≠ Robustly Feasible
Fragile ≠ Infeasible
Dominant Constraint ≠ Only Constraint
Conflict ≠ Average the Conclusions
Unknown Condition ≠ Satisfied Condition
Missing Input ≠ Positive Feasibility
Feasibility Determination Confidence ≠ Prediction Confidence
Feasibility State ≠ Free-Text Opinion
Current Feasibility State ≠ Complete Feasibility History
Later Feasibility ≠ Earlier Feasibility
Later Capability ≠ Historical Feasibility
Feasibility State Change ≠ Prediction Revision by Default
Reassessment ≠ Historical Replacement
Feasibility ≠ Probability Adjustment
Feasible Prediction ≠ Successful Prediction
Infeasible Prediction ≠ Automatically Incorrect Prediction Methodology
Feasibility Determination ≠ Operational Reality Determination
Validated Components ≠ Validated Feasibility of the Whole Outcome
Simulated Feasibility ≠ Governed Feasibility Determination by Default
Enterprise Application
FSDM gives organizations a governed decision layer for converting complex feasibility analysis into a clear, traceable, and reusable result.
Without FSDM, teams may possess:
constraint lists; dependency maps; pathway analyses; capacity assessments; execution simulations;
while still having no disciplined method for determining what the final feasibility state actually is.
FSDM creates that final governed conclusion.
Instead of reducing feasibility to:
yes / no
it preserves:
what is feasible, under which conditions, at what scale, within what horizon, subject to which constraints, with what margin, and according to which historical state.
Use Case 1 — The Project Is Feasible, but Only at Half the Predicted Scale
A company predicts deployment of:
200 autonomous units across 20 facilities within twelve months.
FCIM identifies capacity, integration, workforce, and regulatory constraints.
PCMM maps the dependencies.
OPAM confirms that a viable deployment pathway exists.
EOFM finds that the available integration and commissioning teams can realistically deploy only:
100 units across 10 facilities
within the stated horizon.
The critical governance question is:
Should the original prediction be classified as feasible simply because a smaller version of the outcome can be achieved?
FSDM establishes:
Feasibility Restricted
with explicit qualification:
Feasible for approximately 100 units across 10 facilities within the current Prediction Horizon; the full predicted outcome of 200 units across 20 facilities is not feasible under current execution capacity.
Partial Achievement ≠ Full Feasibility
Use Case 2 — Outcome Is Achievable Only if Two Critical Conditions Occur on Time
An energy company predicts that a new facility will become operational by:
December 2028.
The operational pathway is viable.
Execution capacity is sufficient.
However, the project depends upon:
regulatory approval by March 2027
and:
grid connection availability by January 2028.
If either condition is delayed beyond its threshold, the Prediction Horizon can no longer be achieved.
The critical governance question is:
Can the outcome legitimately be called feasible when its achievability depends upon two unresolved time-critical conditions?
FSDM determines:
Conditionally Feasible
and preserves both conditions as part of the governed feasibility state.
Conditionally Feasible ≠ Feasible Without Qualification
Canonical Boundary
FSDM governs the integration of governed constraint, constraint-mapping, operational-pathway, execution, outcome, scale, scope, timing, authority, permission, infrastructure, resource, and other material feasibility conditions into a final governed feasibility state for a specific predicted outcome. It governs feasibility qualification, conditionality, restriction, uncertainty, infeasibility, inability to determine, margins, fragility, sensitivity, dominant constraints, historical state, reassessment, and state change. It does not form the prediction, calculate probability, govern Predictive Uncertainty, establish Operational Reality, validate evidence, govern Collective Prediction composition, determine actual outcomes, assess predictive performance, or decide prediction-level revision.
FSDM governs:
what feasibility state the predicted outcome may legitimately carry under the applicable conditions.
It does not determine:
whether the predicted outcome will actually occur.
Canonical Closing Statement
Feasibility is not established because nothing obvious appears impossible.
FSDM converts constraints, pathways, execution capability, conditions, scale, timing, and operational limits into a traceable determination of what the predicted outcome can legitimately be called.
A prediction may remain uncertain and still be feasible; it may appear likely and still be infeasible. Governance must know the difference.