# Compatibility Validation Policy

## Purpose
Define how Automated Decision Systems qualifies self-serve governance adapters against declared runtime, adapter, and policy versions.

## Audience
- Operators and release teams
- Enterprise buyers evaluating governed runtime support
- Security and assurance reviewers

## Validation Scope
Validation applies to a declared combination of:
- runtime version
- adapter version
- policy pack or governance pack version
- supporting evidence and reason-code contract

## Minimum Validation Requirements
- Deterministic allow, deny, and constrain behavior
- Expected fail-safe posture for high-risk actions
- Trace and reason-code verification
- Evidence structure and version-stamp verification
- Regression checks for known high-impact scenarios

## Validation States
- `REVIEWED_ENFORCEMENT`: governed behavior is backed by current validation evidence
- `LOCKDOWN_ONLY`: conservative posture only; full enforced claims are not made
- `UNSUPPORTED`: no governance claims for the declared version combination

## Publication Rule
Only combinations backed by current validation evidence may be published as reviewed compatibility rows.

## Revalidation Triggers
Revalidation is required when runtime, adapter, policy, evidence structure, or known governance behavior changes materially.