Data Contracts and SLA Management AI Prompt

Implement data contracts and SLA management for data products in this cloud platform.

Data producers: {{producers}}
Data consumers: {{consumers}}
Current issues: {{issues}} (schema breaking changes, missed SLAs, undocumented changes)

1. What is a data contract:
   A data contract is a formal agreement between a data producer (team that writes the data) and data consumers (teams that read it). It specifies:
   - Schema: column names, types, and semantic meaning
   - Quality: expected null rates, value distributions, referential integrity
   - SLA: freshness (max hours since last update), availability (uptime %)
   - Versioning: how schema changes are communicated and backward compatibility

2. Data contract specification (YAML):
   apiVersion: v1
   kind: DataContract
   id: orders.v1
   producer: payments-team
   owner: payments-data@company.com
   schema:
     - name: order_id
       type: bigint
       nullable: false
       unique: true
     - name: amount_usd
       type: numeric(10,2)
       nullable: false
       minimum: 0
   sla:
     freshness_hours: 2
     availability_percent: 99.5
   versioning:
     current: 1.2.0
     breaking_change_policy: 30-day notice required

3. Tooling:
   - Data Contract CLI (open-source): validate data against contracts, publish to catalog
   - Soda Core: run quality checks defined in contracts
   - dbt + Elementary: enforce schema contracts via model contracts; test quality via tests

4. SLA monitoring:
   - Freshness check: query MAX(updated_at) per table; alert if > SLA threshold
   - Availability: monitor pipeline success rate; alert on consecutive failures
   - Quality score: % of tests passing per data product; publish in the catalog
   - SLA breach report: weekly report of SLA breaches per team, with trend

5. Governance process:
   - Contract registration: new data products must register a contract before GA
   - Breaking change process: 30-day notice + migration guide for all consumers
   - Deprecation: deprecated products sunset after 90 days with active consumer notification

Return: data contract YAML schema, tooling recommendation, SLA monitoring implementation, and governance process.