Architecture Ecosystem: Structured Reality Standards™
Architecture Family: VALIDOS™ — Validation Governance Architecture
Parent Standard: Validation Reliance & Revalidation Standard (VRRS)
Operational Layer: Validation Reliance & Revalidation Layer
Category: AI & Interpretation
Subcategory: Validation Governance
Type: Parent Standard Module
Governed Space: Validation Reliance Monitoring, Dependency &
Change Propagation
Version: 1.0
Status: Canonical · Open Module
Effective Date: 12 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™)

Governed Space

Validation Reliance Monitoring, Dependency & Change Propagation

Canonical Definition

Validation Reliance Monitoring, Dependency & Change Propagation
Module (VRMDCPM) defines the governance framework for continuously
or periodically monitoring active Validation Reliance relationships,
identifying upstream and downstream dependencies, detecting changes
capable of affecting reliance legitimacy, and propagating Validation
State, applicability, object, condition, evidence, source,
dependency, context, consequence, and authorization changes through
affected reliance chains.

It establishes the operational continuity layer through which active
reliance remains synchronized with the validation reality that
continues to justify it.

Operational Role

VRMDCPM serves as the third internal governance space of the
Validation Reliance & Revalidation Standard (VRRS).

The preceding modules establish:

VRESM — Is reliance methodologically eligible and
sufficiently supported?

VRCAOCM — Under what authority, conditions, restrictions, and
controls may that reliance become operational?

VRMDCPM asks:

Once reliance is active, what must be monitored, what does this
reliance depend upon, and how must changes in the validation basis
propagate through the reliance relationship?

The governed progression is:

Active Reliance → Reliance Monitoring Baseline → Dependency Mapping
→ Change Detection → Change Relevance Assessment → Reliance Impact
Assessment → Change Propagation → Reliance Reassessment Signal

VRMDCPM does not determine the final revalidation scope.

It identifies when active reliance no longer cleanly matches the
validation basis that originally supported it.

Module Operational Space

VRMDCPM governs:

• active reliance monitoring,
• reliance-state monitoring,
• reliance-condition monitoring,
• reliance-scope monitoring,
• reliance-context monitoring,
• consequence monitoring,
• object-version monitoring,
• Validation State monitoring,
• applicability monitoring,
• authorization monitoring,
• reliance dependency mapping,
• upstream validation dependencies,
• downstream reliance dependencies,
• dependency criticality,
• reliance-chain mapping,
• change detection,
• change propagation,
• Validation State change propagation,
• object-change propagation,
• scope-change propagation,
• condition-change propagation,
• evidence-change propagation,
• source-change propagation,
• dependency-change propagation,
• authorization-change propagation,
• reliance-context change propagation,
• consequence-escalation propagation,
• monitoring blind spots,
• impact localization,
• cascading reliance effects,
• reliance reassessment signals,
• and reliance-monitoring traceability.

Module Function

VRMDCPM applies while operational reliance remains active,
conditional, partial, restricted, paused, or otherwise subject to
ongoing governance.

Its function is to prevent:

• downstream systems continuing to rely after upstream Validation State changes,
• object-version changes remaining invisible to relying actors,
• expired validation remaining embedded in operational dependencies,
• condition failure failing to propagate into reliance,
• reliance scope expanding without reassessment,
• downstream systems inheriting validation confidence indefinitely,
• hidden dependencies undermining reliance without detection,
• new evidence remaining disconnected from reliance decisions,
• source failure remaining trapped upstream,
• consequence escalation occurring without stronger validation review,
• and reliance chains becoming opaque after multiple system integrations.

Reliance Monitoring Baseline

Effective reliance monitoring requires a governed baseline.

VRMDCPM therefore establishes a Reliance Monitoring Baseline.

The baseline may include:

• Relying Actor,
• Validation Object,
• object version,
• current Validation State,
• Reliance Eligibility Status,
• Reliance Authorization,
• Reliance Purpose,
• Reliance Scope,
• Reliance Context,
• consequence level,
• conditions,
• restrictions,
• limitations,
• operational controls,
• dependencies,
• authorization validity,
• and revalidation status.

This baseline represents the operational reliance reality that
was approved.

Reliance Monitoring

Reliance Monitoring observes whether active reliance remains aligned
with the approved baseline.

Monitoring may be:

• continuous,
• periodic,
• event-triggered,
• risk-triggered,
• change-triggered,
• or hybrid.

Monitoring intensity should remain proportionate to reliance
criticality and system dynamism.

What Reliance Monitoring Watches

Relevant monitoring dimensions may include:

• Validation State,
• object identity,
• object version,
• configuration,
• purpose,
• scope,
• operating environment,
• population,
• autonomy level,
• authorization,
• conditions,
• restrictions,
• controls,
• evidence signals,
• source signals,
• dependency status,
• consequence,
• and expiration.

Validation State Monitoring

The current Validation State supporting reliance should
remain observable.

Relevant state changes include:

Validated → Conditionally Validated

Validated → Validation Suspended

Validated → Validation Expired

Validated → Revalidation Required

Conditionally Validated → Invalidated

or another lifecycle transition.

These changes may materially affect active reliance.

State Change Propagation

VALIDOS™ establishes:

Validation State Change → Reliance Reassessment Signal

where the changed state may affect reliance legitimacy.

A state transition should not remain isolated within validation
records while downstream actors continue unchanged.

Object-Version Monitoring

A relying actor may begin reliance on:

Object Version 4.2

while the operational system later updates to: Version 4.3

VRMDCPM monitors whether the relied-upon object remains the same
governed object version or an accepted equivalent.

Version Drift

Repeated minor version changes may create Reliance Version Drift.

Even where each update appears small, accumulated change may
undermine the original reliance basis.

Configuration Monitoring

Reliance may depend upon specific configuration.

Monitoring may include:

• enabled tools,
• system permissions,
• human oversight settings,
• safety controls,
• model parameters,
• memory settings,
• data connections,
• or external integrations.

Reliance Scope Monitoring

Active operational use may gradually exceed the authorized
reliance scope.

For example:

Authorized: Internal Decision Support

may gradually become:

Used for Customer-Facing Automated Decisions

VRMDCPM identifies this as a scope-change signal.

Reliance Context Monitoring

The same technical use may become materially different because
context changes.

Examples include:

• scale increases,
• human oversight decreases,
• decisions become irreversible,
• user population changes,
• jurisdiction changes,
• deployment becomes continuous,
• or operational dependency increases.

Consequence Monitoring

Reliance consequence may increase over time even where the object
and purpose remain nominally similar.

For example:

A model initially used for low-value transactions may later
influence very large financial exposure.

VRMDCPM monitors consequence escalation as a
validation-relevance signal.

Reliance Consequence Escalation

A Reliance Consequence Escalation occurs where the significance of
reliance failure materially increases beyond the assurance level
originally assessed.

This may trigger:

• Reliance Eligibility reassessment,
• stronger controls,
• authorization escalation,
• Validation Depth escalation,
• or revalidation.

Condition Monitoring

Continuing reliance conditions should remain observable.

Examples include:

• human oversight,
• required safety control,
• monitoring availability,
• specified environment,
• dependency status,
• object version,
• or required corroboration.

Condition Failure Propagation

When a mandatory reliance condition fails, VRMDCPM generates a
propagation signal to the operational reliance layer.

Possible responses may include:

• pause,
• restriction,
• suspension,
• fallback,
• escalation,
• or revalidation assessment.

Authorization Monitoring

Reliance Authorization may:

• expire,
• be modified,
• be suspended,
• be revoked,
• or be superseded.

VRMDCPM ensures authorization changes remain connected to
active reliance.

Authorization Change Propagation

A revoked authorization must not remain operationally active merely
because the Validation State itself remains Validated.

This preserves:

Validation Sufficiency

separately from:

Permission to Rely

Reliance Dependency

A Reliance Dependency is any upstream object, service, system,
control, evidence source, validation artifact, or operational
condition upon which active reliance materially depends.

Dependencies may be:

• validation dependencies,
• technical dependencies,
• data dependencies,
• source dependencies,
• infrastructure dependencies,
• human dependencies,
• or governance dependencies.

Upstream Validation Dependency

An upstream Validation Dependency is an object whose validation
condition materially supports another reliance relationship.

For example:

Validated Dataset → AI Model

or:

Validated Sensor → Autonomous Controller

or:

Validated Prediction Model → Decision Engine

Downstream Reliance Dependency

A downstream dependency is a person, system, or process that
materially relies upon the Validation Object.

For example:

AI Model → Recommendation Platform

Recommendation Platform → Human Decision

Human Decision → Operational Action

Reliance Dependency Map

VRMDCPM may create a Reliance Dependency Map identifying:

• Validation Object,
• Relying Actors,
• upstream validation dependencies,
• downstream systems,
• reliance purposes,
• reliance scopes,
• consequence levels,
• and dependency criticality.

Dependency Criticality

Not every dependency has equal significance.

A dependency may be:

Non-Critical

Supporting

Material

Critical

or another governed classification.

Critical dependencies may require faster change propagation.

Single Point of Validation Dependence

A reliance chain may depend heavily upon one validation object.

Where loss of that object's Validation State can undermine many
downstream systems, VRMDCPM may identify a:

Single Point of Validation Dependence

This becomes important for resilience and revalidation planning.

Reliance Chain

A Reliance Chain represents successive
validation-dependent relationships.

For example:

Validated Data

↓

Validated Model

↓

Authorized Decision Engine Reliance

↓

Autonomous Agent Reliance

↓

Operational Action Each layer can introduce new
governance requirements.

Reliance Chain Depth

Long reliance chains may amplify uncertainty, dependency, and
governance complexity.

VRMDCPM preserves chain depth rather than assuming validation
strength transfers unchanged across each downstream layer.

Validation Confidence Decay Across Chains

VALIDOS™ establishes:

Validation confidence should not be assumed to remain unchanged
across downstream transformations.

Each integration may introduce:

• new scope,
• new interpretation,
• new system behavior,
• new dependencies,
• new consequence,
• or new operational conditions.

Dependency Change

A dependency may change while the primary Validation Object
remains unchanged.

Examples include:

• API update,
• new model provider,
• sensor replacement,
• infrastructure migration,
• source change,
• dataset change,
• human-role change,
• or control-system change.

Dependency Change Propagation

Where a dependency materially changes, affected reliance
relationships should receive a change signal.

The required response depends upon:

• dependency criticality,
• change materiality,
• affected scope,
• and whether validation equivalence remains.

Evidence Change Propagation

New evidence may materially strengthen or weaken the current
reliance basis.

Examples include:

• adverse incident data,
• improved performance data,
• independent validation,
• newly discovered limitation,
• corrected measurement,
• or newly observed failure.

VRMDCPM propagates material evidence change into
reliance reassessment.

Source Change Propagation

Changes in Source Reliability may also affect reliance.

For example:

A decisive upstream source may become:

Conditionally Reliable

Unreliable

or:

Reliability Undetermined

VRMDCPM identifies which reliance relationships depend upon that
source-derived validation basis.

Applicability Change Propagation

A Validation State may remain active but lose applicability in
one domain.

For example:

Validated generally

but:

Validation Applicability Lost for Environment B

Downstream reliance within Environment B must be reassessed.

Restriction Change Propagation

A new restriction may narrow reliance.

For example:

New Restriction: No Autonomous Use

Any downstream autonomous system relying upon the object becomes
affected immediately.

Limitation Change Propagation

A newly identified limitation may not require full suspension but
may justify:

• additional oversight,
• reduced consequence,
• shorter reliance duration,
• or targeted revalidation.

Reliance Context Change

The Relying Actor itself may change the operational use.

Examples include:

• higher autonomy,
• broader population,
• higher stakes,
• more frequent use,
• larger scale,
• new jurisdiction,
• or new purpose.

VRMDCPM treats changes in reliance context as first-class
governance signals.

Reliance Drift

Reliance Drift is the progressive divergence between actual
operational reliance and the Reliance Authorization or
Eligibility basis.

Drift may involve:

• scope,
• purpose,
• autonomy,
• consequence,
• duration,
• population,
• environment,
• or controls.

Authorization Drift

Authorization Drift is a specific form of reliance drift where
actual use moves beyond formal authorization.

Reliance Creep

Reliance Creep occurs where systems or organizations gradually
become more dependent upon the Validation Object than
originally intended.

Examples include:

• advisory outputs become default decisions,
• manual review becomes nominal,
• backup systems are removed,
• transaction limits rise,
• or one validated model becomes a central infrastructure dependency.

Dependency Creep

Dependency Creep occurs where a system accumulates additional
upstream validation dependencies without corresponding
governance reassessment.

Change Signal

A Reliance Change Signal is an observed event indicating possible
divergence from the approved reliance basis.

Signals may come from:

• VSGS,
• system monitoring,
• incident records,
• authorization systems,
• dependency monitors,
• evidence updates,
• source updates,
• or operational analytics.

Change Signal vs Confirmed Reliance Change

VALIDOS™ distinguishes:

Reliance Change Signal

from:

Confirmed Material Reliance Change

A signal triggers assessment.

Confirmation establishes that the relevant change occurred.

Reliance Change Materiality

A confirmed change may be classified as:

Immaterial Reliance Change

No material impact on active reliance is expected.

Minor Reliance-Relevant Change

Limited governance response or monitoring may be sufficient.

Material Reliance Change

Formal reliance reassessment is required.

Critical Reliance Change

Immediate protective action may be required.

Materiality Undetermined

Available information is insufficient to classify the change.

Reliance Impact Assessment

A Reliance Impact Assessment asks:

• Which Relying Actors are affected?
• Which Reliance Purposes are affected?
• Which scopes are affected?
• Which downstream systems depend upon the changed object?
• Which conditions have changed?
• Does current authorization remain valid?
• Is Validation Depth still sufficient?
• Has consequence changed?
• Does reliance need restriction, suspension, or revalidation assessment?

Impact Localization

A change may affect only one portion of a Reliance Chain.

For example:

One environment may become unsupported while other environments
remain valid.

VRMDCPM localizes impact where possible rather than automatically
treating all downstream reliance as invalid.

Cascading Reliance Effect

A change in one Validation Object may produce multiple
downstream consequences.

This is a Cascading Reliance Effect.

For example:

Source Reliability Failure

↓

Validation State Reassessment

↓

Model Reliance Restricted

↓

Decision Engine Reliance Suspended

↓

Autonomous Process Fallback Activated

Propagation Priority

High-consequence or high-dependency changes may require
faster propagation.

A propagation priority may consider:

• criticality,
• number of downstream actors,
• consequence,
• immediacy,
• reversibility,
• and operational exposure.

Propagation Latency

Reliance governance should consider how long it takes for validation
changes to reach downstream relying actors.

Excessive propagation latency may allow invalid or unsupported
reliance to continue.

Critical Propagation Requirement

For critical reliance chains, certain validation-state changes may
require immediate propagation.

Examples include:

• Validation Invalidated,
• critical suspension,
• critical evidence compromise,
• or severe source failure.

Reliance Reassessment Signal

VRMDCPM may generate a formal Reliance Reassessment Signal when the
active reliance basis may no longer be sufficient.

Possible signals include:

No Reassessment Required

Reliance Review Recommended

Reliance Reassessment Required

Reliance Restriction Recommended

Reliance Suspension Recommended

Revalidation Assessment Required

These are governance signals, not final reliance decisions.

Revalidation Assessment Signal

Where the detected change appears capable of exceeding the existing
validation basis, VRMDCPM may generate:

Revalidation Assessment Required

The fourth VRRS module then determines:

What exactly must be revalidated?

Monitoring Blind Spot

A Reliance Monitoring Blind Spot exists where a material dependency,
validation-state condition, authorization change, or operational-use
dimension is insufficiently observable.

Blind spots may include:

• hidden third-party model updates,
• undocumented downstream use,
• inaccessible external dependency status,
• unlogged scope expansion,
• or unknown system configuration.

Monitoring Coverage

Reliance Monitoring Coverage may be:

Sufficient

Conditionally Sufficient

Partial

Insufficient

or:

Undetermined

Insufficient coverage may itself create reliance uncertainty.

Monitoring Freshness

Reliance monitoring information must remain sufficiently current for
the pace at which relevant conditions can change.

A monthly validation-state check may be insufficient for a system
that updates daily.

Monitoring Frequency

Monitoring frequency should correspond to:

• object update frequency,
• Reliance Criticality,
• dependency volatility,
• Validation State volatility,
• consequence,
• and operational scale.

Event-Triggered Propagation

Certain events may trigger immediate reliance reassessment.

Examples include:

• Validation State transition,
• object major-version change,
• critical incident,
• authorization revocation,
• condition failure,
• critical dependency update,
• source retraction,
• or state expiration.

Automated Change Propagation

Machine-readable validation and reliance records may permit
automatic propagation.

For example:

Validation State = Suspended

could automatically produce:

Affected Reliance Authorizations = Suspended where the authorization
rules require it.

AI-Assisted Impact Propagation

AI may assist with:

• dependency discovery,
• impact mapping,
• change summarization,
• affected-scope detection,
• reliance-chain analysis,
• and prioritization.

AI should not invent unobserved dependencies as facts.

Uncertain inferred dependencies must remain distinguishable from
confirmed ones.

Human Change Propagation

Human governance may remain necessary where:

• downstream dependencies are organizational,
• consequence is contextual,
• scope relationships are complex,
• or authorization rules require judgment.

Reliance Monitoring Record

A formal record may preserve:

• Relying Actor,
• Validation Object,
• current Validation State,
• Reliance Authorization,
• Monitoring Baseline,
• monitored dimensions,
• dependencies,
• dependency criticality,
• detected changes,
• change materiality,
• affected downstream actors,
• propagation actions,
• impact assessment,
• reassessment signals,
• revalidation signals,
• monitoring blind spots,
• monitoring time,
• and sufficient traceability.

Dependency Record

A Reliance Dependency Record may preserve:

• Dependency Identifier,
• dependency type,
• upstream object,
• downstream actor,
• reliance purpose,
• affected scope,
• criticality,
• Validation State dependency,
• conditions,
• change sensitivity,
• and propagation rule.

Reliance Impact Map

A Reliance Impact Map may represent:

Changed Validation Object

↓

Affected Validation States

↓

Affected Relying Actors

↓

Affected Reliance Authorizations

↓

Affected Decisions / Systems / Operations

This supports rapid response to validation change.

Minimum Implementation Framework

1. Establish Reliance Monitoring Baseline

Preserve the approved active reliance relationship.

2. Identify Reliance Dependencies

Map upstream validation dependencies and downstream relying actors.

3. Classify Dependency Criticality

Determine which dependencies can materially affect
reliance legitimacy.

4. Establish Monitoring Dimensions

Monitor relevant:

• Validation State,
• object version,
• configuration,
• conditions,
• authorization,
• scope,
• context,
• consequence,
• evidence,
• sources,
• and dependencies.

5. Detect Change Signals

Identify changes relative to the approved reliance baseline.

6. Verify Material Changes

Confirm significant signals where possible.

7. Assess Reliance Change Materiality

Classify the impact potential of the change.

8. Perform Reliance Impact Assessment

Identify affected actors, scopes, authorizations, and
downstream systems.

9. Propagate Change

Communicate or machine-propagate material validation changes through
affected reliance chains.

10. Generate Reassessment Signal

Determine whether:

• no action,
• review,
• reassessment,
• restriction,
• suspension,
• or revalidation assessment

is required.

11. Preserve Monitoring & Dependency Traceability

Maintain the complete monitoring, dependency, change, impact, and
propagation history.

Governance Outputs

VRMDCPM may produce:

• Reliance Monitoring Baseline,
• Validation Reliance Monitoring Record,
• Reliance Monitoring Plan,
• Reliance Monitoring Dimension Register,
• Reliance Monitoring Coverage Assessment,
• Reliance Monitoring Blind Spot Record,
• Reliance Monitoring Freshness Assessment,
• Validation State Change Signal,
• Object Version Change Signal,
• Configuration Change Signal,
• Reliance Scope Change Signal,
• Reliance Context Change Signal,
• Reliance Consequence Escalation Record,
• Reliance Condition Failure Signal,
• Authorization Change Signal,
• Reliance Dependency Map,
• Reliance Dependency Record,
• Upstream Validation Dependency Map,
• Downstream Reliance Dependency Map,
• Dependency Criticality Assessment,
• Single Point of Validation Dependence Record,
• Reliance Chain Map,
• Reliance Chain Depth Record,
• Dependency Change Record,
• Evidence Change Propagation Record,
• Source Change Propagation Record,
• Applicability Change Propagation Record,
• Restriction Change Propagation Record,
• Reliance Drift Record,
• Authorization Drift Record,
• Reliance Creep Record,
• Dependency Creep Record,
• Reliance Change Materiality Assessment,
• Reliance Impact Assessment,
• Reliance Impact Map,
• Cascading Reliance Effect Record,
• Change Propagation Record,
• Propagation Priority Record,
• Reliance Reassessment Signal,
• Reliance Restriction Signal,
• Reliance Suspension Signal,
• Revalidation Assessment Required Signal,
• and Reliance Change Traceability Record.

Use Case 1 — AI Model Shared Across Multiple Systems

Scenario

One Validated AI model is used by:

• an internal research tool,
• a customer-support platform,
• a financial decision engine,
• and an autonomous workflow agent.

The model's Validation State changes:

Validated → Conditionally Validated

because a newly identified failure mode requires human review for
high-consequence outputs.

Application

VRMDCPM uses the Reliance Dependency Map to identify all downstream
relying systems.

Result

The impact differs by context:

• internal research may remain eligible,
• customer support may require additional review,
• financial automated decisions may require suspension,
• autonomous workflow use may require reassessment or revalidation.

One upstream state change therefore produces differentiated
downstream governance rather than one universal response.

Use Case 2 — Healthcare AI Dependency Change

Scenario

A diagnostic AI relies upon an external laboratory-data service that
was part of the validated configuration.

The service materially changes its data-processing methodology.

Application

VRMDCPM detects a Dependency Change and identifies which validation
and reliance relationships depend upon that service.

Result

A Revalidation Assessment Required signal is generated for the
affected diagnostic pathway rather than assuming the unchanged AI
model remains fully validated in the new dependency reality.

Use Case 3 — Autonomous Financial Agent

Scenario

An autonomous financial agent was authorized to rely upon a
validated prediction model for transactions below a defined
exposure limit.

Over time, the organization gradually increases transaction size
without formally updating the reliance authorization.

Application

VRMDCPM detects:

Reliance Consequence Escalation

and:

Authorization Drift

Result

The active reliance relationship receives:

Reliance Reassessment Required

and potentially:

Validation Depth Escalation / Revalidation Assessment Required

before the higher-consequence use can continue legitimately.

Architectural Position

Validation Reliance Monitoring, Dependency & Change Propagation is
the third internal governance space of the Validation Reliance &
Revalidation Standard (VRRS).

The progression now becomes:

Reliance Eligibility & Sufficiency → Reliance Conditions &
Authorization → Reliance Monitoring, Dependency & Change Propagation
VRESM establishes:

Can validation support the reliance?

VRCAOCM establishes:

How may that reliance become operational and controlled?

VRMDCPM establishes:

Does the active reliance still match the validation basis, what does
it depend upon, and how do validation-relevant changes propagate
through the reliance chain?

The next VRRS governance stage can then ask:

Given the detected material change or Revalidation Assessment
Required signal, what exactly has changed, which parts of previous
validation remain reusable, and what scope and depth of revalidation
are now required?

The VRRS progression therefore continues:

Reliance Eligibility & Sufficiency → Reliance Conditions &
Authorization → Reliance Monitoring, Dependency & Change Propagation
→ Revalidation Scope, Delta & Validation Reuse → Revalidation
Execution, Renewal & Reliance Continuity

Foundational Principle

Reliance remains legitimate only while changes in the validation
basis, the relied-upon object, the relying context, and the
dependency chain remain visible enough to propagate to every
materially affected reliance relationship.

Canonical Closing Statement

Validation Reliance Monitoring, Dependency & Change Propagation
Module establishes the operational continuity layer of VALIDOS™
reliance governance by monitoring active reliance, mapping upstream
and downstream validation dependencies, detecting object, state,
condition, authorization, evidence, source, context, consequence,
and dependency change, assessing materiality, localizing impact, and
propagating validation-relevant changes through reliance chains.
VRMDCPM ensures that operational reliance cannot remain frozen while
the validation reality supporting it changes and creates the
governed connection through which material upstream change becomes
downstream review, restriction, suspension, or revalidation
assessment wherever continued reliance may no longer be
legitimately supported.

→ Validation Reliance & Revalidation Standard

→ About Validation Reliance & Revalidation Standard