Contract Validation Pipeline AI Prompt

Build an automated contract validation pipeline that verifies produced data meets all contract commitments before it is made available to consumers.

Data contract: {{contract_name}}

1. Validation gate architecture:
   - Produce data to a staging location (not the production table)
   - Run all contract validations against the staging data
   - Only promote to production if ALL blocking validations pass
   - If any blocking validation fails: halt, alert producer, do not expose data to consumers

2. Schema validation:
   - All required columns are present
   - All column data types match the contract definition
   - No unexpected new columns (flag as warning — possible unplanned schema evolution)

3. Semantic validation:
   - Primary key is unique and non-null
   - All NOT NULL columns have no nulls
   - All categorical columns contain only contract-defined values
   - Business rule assertions: {{business_rules}}

4. Freshness validation:
   - MAX(event_timestamp) is within the contract-defined freshness window
   - Row count is within ±{{tolerance}}% of the expected count for this time period

5. Promotion to production:
   - Atomic swap: rename staging table to production (or INSERT OVERWRITE the partition)
   - Log promotion: contract_name, run_id, validation_results, promotion_timestamp
   - Notify downstream consumers that fresh data is available (via event or polling endpoint)

6. Consumer-facing freshness endpoint:
   - GET /contracts/{{contract_name}}/freshness → returns: last_updated, row_count, validation_status
   - Consumers can poll this endpoint to know when new data is ready

Return: validation pipeline code, promotion logic, freshness endpoint spec, and consumer notification design.