Data Contracts

Versioned producer/consumer agreements: schema, semantics, SLAs and breaking-change policy. This path sequences the category's 13 resources by roadmap stage and composite score — work top-down inside each step.

Data Quality

1. Schema Change Contract Review 40.5 — Classify a schema change as safe, risky, or breaking — before it ships.
2. Data Contract Author 38.5 — Turn a vague producer/consumer agreement into an enforceable contract.
3. Schema drift 34.75 — Schema drift
4. Contracts as a Quality Gate 34.75 — Contracts as a Quality Gate
5. Author your first data contract 34.15 — Author your first data contract
6. Enforce contracts in CI with the schema change check 34.15 — Enforce contracts in CI with the schema change check

7 more on the category page.

Documented prerequisites, deduplicated: skill-sql-review, skill-schema-change-contract-review.

• Apply backward/forward compatibility rules to a diff
• Detect a breaking change hidden behind a "safe" rename
• Write a deprecation plan with dates
• Specify a freshness and completeness SLA
• Encode a contract as executable tests
• Define a breaking-change policy consumers can rely on
• Write all six parts of a contract for a real dataset
• Specify freshness and completeness numbers in the SLA

Security-flagged: Schema Change Contract Review, Data Contract Author, Schema drift, Contract Kit, Schema Reviewer, Data Contract Template, Data contract broken, Schema Change Check — review the security posture first. Verification on these records: 13 community. Nothing here is independently audited — the trust scan and your own review are the controls.

Phase 3 of the roadmap. Stage context: Data Quality · side-by-side comparison · all learning topics