Jaco van der Laan

Lineage & governance

The Governance Symmetry

Data governance controls the inputs; AI governance controls the outputs. They are two ends of one chain — and you cannot govern the outputs of a system whose inputs are ungoverned.

"AI governance" and "data governance" are usually run as two programs, by two teams, with two budgets — and treated as if they were separate subjects. They aren't. They are the same chain seen from opposite ends. Data governance protects the enterprise from what goes in: poor-quality, incomplete or unauthorized data entering the system. AI governance protects it from what comes out: opaque decisions, bias, and automation running unchecked. Inputs on one side, outputs on the other, and a set of shared concerns — privacy, lineage, auditability, risk — sitting between them. Seeing the symmetry settles a common confusion, which is the belief that you can bolt AI governance onto an organization that never governed its data. You can write all the model cards, fairness checks and output guardrails you like; if the data feeding the model is ungoverned, you are inspecting the outputs of a process whose inputs you don't control. The output guardrail catches a bad answer after the bad input produced it — useful, but downstream of the real leak. Governing one end while neglecting the other isn't half a solution; it's a solution to the wrong half. The symmetry also locates a layer most models miss: the enforcement in the middle, at runtime. Design-time governance — policies, standards, catalogs — is necessary but static. What agentic systems add is the need for governance that acts in real time: policy checked, access enforced, quality validated at the moment a decision is made, with escalation when something crosses a threshold. That runtime layer is where input-control and output-control actually meet — the point where the two ends of the chain are held together instead of managed apart. The practical consequence for anyone selling or building this: lead with the chain, not the halves. An organization proud of its AI-governance policy but weak on its data foundation is governing the wrong end, and the fix isn't more output controls — it's the missing input discipline underneath. Structure at the source is what makes governance at the surface mean anything.

← All concepts & vocabulary