Review the migration artifact contract

Payne prepares one immutable PostgreSQL compatibility transformation for the official finance_revenue_close consumer. Generation is bound to the current gate, analysis, interpretation, evidence and capability versions, exact lineage path, replacement schema, consumer context, and contract checksum.

Validation checks PostgreSQL parsing, read-only statement safety, allowed source relations and fields, expected outputs, known type and nullability evidence, and fixture execution/output. not-proven is preserved for facts the fixture cannot establish, including business meaning and production performance.

Lifecycle boundary

Prepared for review, accepted, applied, and verified are separate states. Artifact preparation does not change a repository, DataHub, or a gate. Application requires the exact accepted checksum and current evidence binding.

Recover a failed artifact

Start with the first failed validation row. Provider or evidence failures require a fresh run after recovery. An immutable failed candidate remains available for inspection; preparing again creates a new candidate. If stored bytes no longer match the checksum, restore a trusted Payne artifact volume or prepare a new artifact—never edit the record to force a pass.

Recovery is complete when a new immutable candidate shows every required static and fixture check as passed, preserves any honest not-proven limitations, and returns to Prepared for review. A passing candidate is still not accepted, applied, or verified.