The 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.
Treating data like a product with an error budget: SLO platforms, burn-aware alerting, and incident practice that communicates before consumers notice.
A stakeholder tells you, with feeling: "the dashboard must never be late." You nod, because arguing feels worse. It's late twice that quarter anyway — each time an escalation, a tense thread, a promise to "prioritize stability." Nothing structurally changes, because "never" is not a number: you can't budget against it, staff against it, or even say whether this quarter was better than last. What number would let you *engineer* this relationship instead of repeatedly apologizing inside it?
The final week imports that number — SRE's SLI/SLO/error-budget machinery — and adapts it to the failure mode data has that servers don't.
The full week 4 brief is part of LeetData Pro.
