Most data pipelines ship without a contract. No defined freshness guarantee. No agreed row count tolerance. No documented owner. No stated downstream dependency. And when something breaks, everyone finds out at the same time — when the business report is wrong.

This session makes the case for treating pipeline SLAs the way backend engineers treat API contracts: as a first-class engineering artifact that gets defined before the pipeline ships, not retrofitted after the first incident. We'll walk through what a meaningful data SLA actually contains — freshness windows, volume tolerances, quality thresholds, blast radius documentation, and escalation paths — and how to operationalize them across a team without turning every pipeline into a bureaucratic exercise.