Validation profile reference

Built-in version-1 profiles cover table, view, stored_procedure, function, etl_job, and report. Each contains exactly one requirement for all nine readiness tracks and marks it required or not applicable.

Tracks and verdicts

Tracks: inventory, target_design, code, data_movement, deployment, functional_parity, non_functional, business_acceptance, and cutover_readiness.

Verdicts: pending, passed, failed, stale, and waived. not_applicable is profile applicability, not a verdict.

Validation providers

experiments, lakebridge_reconcile, harness, runway, radar, and external. Business acceptance is produced by a separate natural-person decision.

Parity depth

Parity evidence increases from row_count to aggregates, sampled_rows, and full_checksum. A stronger label requires its supporting fields. Parity depth never claims deployment, security, operability, business acceptance, or cutover readiness.

Run fa profiles --json for the canonical digest and exact required tracks of each installed profile.