des-provero-validation

To convert data quality expectations into executable validation suites, you define a declarative provero.yaml configuration that maps DES expectations into Provero checks, generating structured evidence for phase-gate decisions.

Provero validation generates evidence for phase-gate decisions by running configured check suites that produce structured outputs, including reports, historical baselines, anomaly detection, and contract diff artifacts for Done Gate recommendations.

Yes, you can schedule data quality checks and alerts using Airflow integration to run CI-style validation workflows, executing Provero suites and collecting evidence artifacts on a recurring basis.

Validating Bronze, Silver, and Gold dataset layers requires applying Provero validation suites with explicit severity mapping across info, warning, critical, and blocker levels to gate data pipeline phases.

Yes, you need a declarative provero.yaml file to run contract diff and anomaly monitoring, along with correct connector access to data sources like DuckDB or PostgreSQL to generate evidence artifacts.

dbt model checks should stay as Provero validations when you require phase-gate evidence packs and historical baselines, whereas exporting to dbt suits model-level transformations within the pipeline.