The idea
A data pipeline depends on promises made by its source: which fields exist, how records are identified and when updates become available. A source contract makes those assumptions visible. It is especially useful when the producer and the analysis team work independently.
Design choice
Document required fields, valid ranges, ownership and expected delivery timing. Separate a structural failure from an unusual but valid business value. Decide how a consumer learns about a planned breaking change.
Worked example
A daily stock feed promises a stable item identifier and a snapshot timestamp. A missing feed is reported separately from a valid snapshot containing zero stock.
Before you ship
- Identify the source owner
- Distinguish absent from empty deliveries
- Agree on change notification
Examples are illustrative. Adapt the checks to your own environment.