Data Quality, Contracts & ObservabilityThe Airbnb quality arc, contracts from discourse to production, validation frameworks, and SLOs for data.The most editorially distinctive cohort — data contracts are the debate this newsletter helped shape. Production anchors: Airbnb's Wall→Quality-Score arc, Uber's operational excellence program, Meta's Table Compare, GoCardless and Whatnot shipping contracts for real.Week 3: Validation frameworks & WAPWrite-Audit-Publish, table comparison, and the coverage-vs-noise tradeoff every validation framework has to price.

Figure 1 — Write-Audit-Publish. By the end of this week you can read this as a guarantee map: what the audit gate makes structurally impossible, and what still slips past it

A teammate ships a pipeline change on Tuesday. The job runs green Tuesday night, Wednesday night, every night. The following Monday, finance reports that a key number has been off by 12% since — you check the deploy log — Tuesday. Nothing failed. Nothing alerted. The uncomfortable realization: green meant the job ran. Nobody ever claimed it was right. What would a system that actually verified *rightness* look like?This week is that system: staging data before consumers can touch it, diffing changed logic against production before it ships, and the layer of failures no written rule can catch.After this week you canThe full week 3 brief is part of LeetData Pro.Case studies

Dropbox — Balancing quality and coverage with our data validation framework

LinkedIn — Scalable Automated Config-Driven Data Validation with ValiData

Meta — Table Compare: Safeguarding Data Integrity at Meta

Checkout.com — Testing & Monitoring the Data Platform at Scale

Expedia — Chill Your Data with Iceberg Write Audit Publish

Adam Bellemare & Thomas Betts — The End of the Bronze Age: Rethinking the Medallion Architecture

Exercises

Week 3 check: Validation & WAP

The Backfill That Skipped the Audit

The Silent Nulls

The Upstream Schema Change