Jaco van der Laan

Lineage & governance

Governance at the Point of Consumption

Most quality and policy checks fire at ingestion. The failure that hurts happens at the moment of use — when a dashboard, app or AI agent reads the data and acts.

Ask most teams where their data quality lives and they point at the front door: validation at ingestion, checks in the pipeline, a certified layer. All correct, all necessary — and all upstream of the moment that actually matters. Data doesn't cause damage when it enters; it causes damage when it is used. The dashboard that drives a decision, the app that shows a customer a number, the AI agent that reads a value and acts on it — that is where a stale or wrong figure turns into a wrong outcome, and it is precisely where almost no one is checking. The reassuring sentence that hides the gap is "the data passed all its quality checks last quarter." Quality is not a quarterly snapshot; it is a property of the data at the instant of consumption. A row that was valid at ingestion can be stale by the time a dashboard serves it, superseded by the time an agent retrieves it, or correct in isolation but wrong for this decision in this moment. Governance that only guards the entrance certifies that the data was fine when it arrived — a claim that gets weaker every hour it sits. This reframes governance from retrospective to inline. The traditional model is after-the-fact: audit the lineage, review the access logs, run the human review cycles, catch the problem next quarter. The point-of-consumption model enforces at the decision point: policy, access and quality checked at the exact moment the data is read, so a bad value is caught before it becomes a bad action rather than reconstructed afterward. It is the difference between a smoke detector and a fire report. For an AI-native platform this stops being optional. When the consumer is a human analyst, a slightly stale number is usually survivable — they sanity-check, they notice. When the consumer is an autonomous agent, there is no sanity-check between the data and the action; the point of consumption is the last line of defense. Which is the whole argument: build the checks where the data is used, not only where it enters, because that is where the cost lands.

← All concepts & vocabulary