Validation Method Suitability Module (VMSM)
Architecture Ecosystem: Structured Reality Standards™
Architecture Family: VALIDOS™ — Validation Governance Architecture
Parent Standard: Validation Method Standard (VMTS)
Operational Layer: Validation Method Governance Layer
Category: AI & Interpretation
Subcategory: Validation Governance
Type: Parent Standard Module
Governed Space: Validation Method Suitability
Version: 1.0
Status: Canonical · Open Module
Effective Date: 8 August 2026
Compatibility: OOF® Methodology OS™ · GOA™ · OBIDENITY® · INTEGROS®
· ORA™ · AGA™ · AIG® · CLIA® · MGIA™ · ASGA™ · RIS™
AI-Readable: Yes
Authority: OOF®
Protection: MIP® — Methodological Intellectual Property
Canonical Language: English (UCL™)
Canonical Definition
Validation Method Suitability Module (VMSM) defines the governanceframework for determining whether an Eligible Validation Method is
methodologically appropriate, proportionate, capable, and
sufficiently aligned with the specific Validation Object, Validation
Criteria, Validation Purpose, Validation Scope, required Validation
Depth, operating conditions, uncertainty profile, and intended
Validation Determination.
It establishes the conditions under which methodological eligibility
becomes Validation Method Suitability for a specific governed
validation context.
Operational Role
VMSM governs the suitability-assessment stage of ValidationMethod governance.
The preceding Validation Method Eligibility Module determines
whether a candidate method may legitimately enter
formal consideration.
VMSM asks the more demanding question:
Is this eligible method actually fit for this validation?
The governed progression is: Eligible Validation Method → Object Fit
→ Criterion Fit → Scope Fit → Depth Fit → Context Fit → Capability
Assessment → Suitability Determination
A method should not proceed toward selection merely because it is
recognized, established, standardized, available, or commonly used.
Module Operational Space
VMSM governs:- method-object suitability,
- method-criterion suitability,
- method-purpose suitability,
- method-scope suitability,
- method-depth suitability,
- contextual suitability,
- operational suitability,
- population suitability,
- methodological capability,
- sensitivity suitability,
- uncertainty suitability,
- method proportionality,
- method coverage,
- applicability boundaries,
- suitability limitations,
- conditional suitability,
- suitability comparison,
- suitability determination,
- and suitability traceability.
Module Function
VMSM applies to methods that have passed the minimumeligibility gate.
Its function is to prevent:
- eligible methods being assumed suitable by default,
- standardized methods being used outside their intended context,
- familiar methods being preferred despite weak criterion alignment,
- methods being transferred between incompatible Validation Objects,
- shallow methods being used for high-depth validation,
- methods incapable of detecting material conditions being treated as sufficient,
- population-specific methods being generalized without justification,
- contextual limitations being ignored,
- and method selection occurring without an explicit assessment of validation fitness.
Eligibility and Suitability Are Different
VALIDOS™ preserves the distinction:Eligibility asks whether a method can legitimately be considered.
Suitability asks whether that method can legitimately perform the
required validation role.
For example:
A statistical method may be entirely legitimate.
That does not mean it is sufficient to validate:
- causal claims,
- physical safety,
- source provenance,
- governance authority,
- contextual appropriateness,
- or operational behavior
unless its methodological capabilities actually correspond to
those conditions.
Therefore:
Method Legitimacy ≠ Validation Fitness
Method-to-Object Suitability
VMSM assesses whether the method is appropriate for the actualValidation Object established under VALIDOS™.
Suitability may depend upon:
- object type,
- object complexity,
- object configuration,
- object state,
- object version,
- object observability,
- object accessibility,
- object dependencies,
- and object operating environment.
A method suitable for one version or configuration of an object may
not automatically remain suitable after material change.
Method-to-Criterion Suitability
Every method must be assessed against the Validation Criterion it isexpected to examine.
VMSM asks:
- Can the method observe the relevant characteristic?
- Can it distinguish meaningful differences?
- Can it evaluate the applicable threshold?
- Can it support the required acceptance or rejection logic?
- Can it expose relevant uncertainty?
- Can it generate or evaluate information sufficient for later determination?
A method that cannot answer the criterion's underlying validation
question is not suitable for that criterion.
Method-to-Purpose Suitability
The same method may be suitable for one Validation Purpose butinsufficient for another.
For example, a lightweight analytical review may be suitable for:
preliminary screening
but unsuitable for:
high-consequence deployment authorization.
VMSM therefore evaluates method suitability relative to the purpose
for which the resulting validation will be used.
Method-to-Scope Suitability
Validation Scope defines the boundaries of the validation mandate.VMSM determines whether the method can operate meaningfully within
those boundaries.
A method may be suitable for:
- one subsystem but not the complete system,
- one population but not another,
- one operational environment but not another,
- one lifecycle phase but not continuous operation.
Methodological coverage must therefore correspond to the approved
Validation Scope.
Method-to-Depth Suitability
Required Validation Depth materially affects method suitability.A method capable of establishing a basic condition may be
insufficient for deeper validation requiring:
- stronger evidence,
- greater precision,
- broader scenario coverage,
- independent corroboration,
- adversarial examination,
- higher confidence,
- or more extensive operational testing.
VMSM therefore assesses whether the methodological capability is
proportionate to the required Validation Depth.
Contextual Suitability
Methods operate within contexts.Relevant conditions may include:
- jurisdiction,
- environment,
- population,
- operating mode,
- system scale,
- language,
- culture,
- physical conditions,
- temporal conditions,
- regulatory environment,
- or deployment context.
A method validated in one context cannot automatically be assumed
suitable in another.
Contextual transfer requires justification.
Methodological Capability
VMSM evaluates what the method can actually establish.Capability may include the ability to:
- detect a condition,
- measure a characteristic,
- distinguish states,
- compare alternatives,
- identify deviations,
- estimate uncertainty,
- test robustness,
- reproduce behavior,
- expose failure modes,
- or support a particular type of inference.
The method's claimed role must not exceed its demonstrated or
defensibly established methodological capability.
Sensitivity Suitability
A method may be generally appropriate but insufficiently sensitiveto detect differences that matter to the Validation Criterion.
VMSM therefore considers whether the method can distinguish:
- acceptable from unacceptable conditions,
- meaningful deviations,
- boundary cases,
- rare but material failures,
- or other validation-relevant differences.
Insufficient sensitivity may make an otherwise eligible method
unsuitable or only conditionally suitable.
Uncertainty Suitability
Some Validation Criteria require explicit treatment of uncertainty.VMSM assesses whether the method can adequately:
- identify uncertainty,
- quantify or characterize uncertainty where required,
- distinguish uncertainty from observed variation,
- and support interpretation relative to applicable thresholds.
A method that produces a single apparently precise result while
concealing material uncertainty may be unsuitable for a validation
requiring uncertainty-aware determination.
Method Proportionality
Validation methodology should be proportionate to:- risk,
- consequence,
- complexity,
- Validation Depth,
- intended reliance,
- reversibility,
- and operational significance.
VMSM prevents both:
under-validation, where the method is insufficient for the
consequence environment,
and:
methodological overreach, where unnecessary complexity creates cost
or delay without materially improving validation confidence.
Method Coverage
One method may cover:- one criterion,
- several criteria,
- part of a criterion,
- or a defined subset of the Validation Scope.
VMSM requires the actual coverage to be explicit.
A method's presence within the Validation Method Framework must not
imply coverage beyond what it can legitimately examine.
Suitability Limitations
A method may be suitable while still carrying limitations.For example:
Suitable for normal operating conditions, but not validated for
extreme environments.
or:
Suitable for performance evaluation, but insufficient for
causal determination.
These limitations must remain attached to the suitability
determination and propagate into later method selection and
validation governance.
Conditional Suitability
VMSM may classify a method as suitable only underspecified conditions.
Conditions may include:
- additional corroboration,
- restricted operating range,
- specific configuration,
- independent review,
- minimum sample size,
- defined population,
- required calibration,
- complementary method,
- or another governance condition.
Conditional suitability must not later be represented simply as
unrestricted suitability.
Suitability Comparison
Where multiple eligible methods could examine the same criterion,VMSM may compare their relative suitability.
Comparison may consider:
- criterion alignment,
- object alignment,
- depth capability,
- sensitivity,
- robustness,
- uncertainty handling,
- contextual applicability,
- limitations,
- reproducibility,
- resource proportionality,
- and independence potential.
VMSM does not automatically select the highest-scoring method.
It establishes the governed suitability basis upon which method
selection can subsequently occur.
Suitability Determination
An Eligible Validation Method may receive a suitability statussuch as:
Suitable
The method is sufficiently appropriate for the defined
validation role.
Conditionally Suitable
The method is suitable only under explicit conditions
or limitations.
Suitability Undetermined
Available information is insufficient to establish suitability.
Unsuitable
The method cannot legitimately perform the proposed validation role.
Suitability status must remain linked to the specific Validation
Object, criteria, scope, depth, and context assessed.
Minimum Implementation Framework
1. Establish Proposed Validation RoleIdentify precisely which Validation Object, criteria, scope, and
methodological function the method is expected to support.
2. Assess Object and Criterion Fit
Determine whether the method is capable of meaningfully examining
the actual Validation Object and relevant Validation Criteria.
3. Assess Purpose, Scope, and Depth Fit
Determine whether methodological capability corresponds to the
intended use, validation boundaries, and required Validation Depth.
4. Assess Context, Sensitivity, and Uncertainty
Determine whether the method remains appropriate under the
applicable operational conditions and can detect and characterize
validation-relevant differences.
5. Assess Proportionality and Limitations
Determine whether the method is proportionate to the validation
consequence and identify material limitations or conditions.
6. Establish Suitability Status
Classify the method as:
- Suitable,
- Conditionally Suitable,
- Suitability Undetermined,
- or Unsuitable.
7. Preserve Suitability Traceability
Maintain:
- Method Identifier,
- proposed validation role,
- relevant Validation Object,
- applicable Validation Criteria,
- Validation Purpose,
- Validation Scope,
- required Validation Depth,
- contextual conditions,
- capability assessment,
- sensitivity assessment,
- uncertainty assessment,
- limitations,
- conditions,
- suitability status,
- version,
- and sufficient lifecycle traceability.
Suitability Is Role-Specific
A critical VALIDOS™ rule is:Validation Method Suitability is not a universal property of
a method.
A method can simultaneously be:
Suitable for Criterion A,
Conditionally Suitable for Criterion B,
and:
Unsuitable for Criterion C.
Suitability must therefore remain attached to the specific
validation role rather than becoming a permanent label applied to
the method itself.
Suitability Change Governance
A previous suitability determination may become invalid whenmaterial conditions change.
Triggers may include:
- Validation Object modification,
- changed Validation Criteria,
- changed Validation Scope,
- increased Validation Depth,
- changed operating environment,
- new methodological evidence,
- discovered limitations,
- new failure modes,
- or changed intended reliance.
Material changes require proportionate reassessment.
Suitability and Method Selection
VMSM does not make the final method-selection decision.It establishes which methods are methodologically fit for the
required validation roles and under what conditions.
The architectural transition is:
Eligible Methods → Suitability Assessment → Suitable Method Set →
Method Selection
This prevents selection from being driven primarily by convenience,
cost, organizational preference, or expected outcome.
Use Case 1 — Medical AI Validation
ScenarioA statistical benchmark method has been established as eligible for
evaluating a diagnostic AI system.
The method was developed using one patient population, while the
intended deployment includes materially different populations.
Application
VMSM evaluates population applicability and determines that the
method is not universally suitable for the complete
Validation Scope.
Result
The method may be classified as Conditionally Suitable for the
represented population while additional methodological coverage is
required for others.
Use Case 2 — Autonomous System Validation
ScenarioSimulation is proposed for validating an autonomous system
before deployment.
Simulation is an eligible validation method and can examine
thousands of operational scenarios.
Application
VMSM determines that simulation provides strong suitability for
scenario coverage but cannot independently establish all relevant
real-world operational conditions.
Result
Simulation remains suitable for defined criteria but may require
complementary real-world validation methods for complete
methodological coverage.