All posts
Governance and AI readiness

Auditors do not want
your architecture diagram

By Woodfrog · 6 min read · Accurate as of

The document everyone prepares is rarely the thing that gets asked for. What gets asked for is narrower, more specific, and much harder to produce after the fact.

The question is always about one field

The request is not to explain the platform. It is closer to: this number in this report, on this date, where did it come from, who could see it, and what changed it between the source system and here.

A diagram cannot answer that. A diagram describes how the system was intended to work, which is a claim about the past made by somebody who was not watching. What answers it is a record the pipeline produced while it was running.

Why hand-maintained lineage fails

Documented lineage is accurate on the day it is written and decays from then on. Somebody adds a join, somebody else swaps a source, a column gets renamed during a migration, and none of those changes make it back into the document because updating it is nobody's job and nothing breaks when they do not.

The failure is quiet, which is the problem. You do not discover the document is wrong until you are relying on it in front of somebody whose job is to find out.

What generated lineage gives you

When the platform records every hop as it happens, the answer to the field-level question is a lookup. You can show the source table, each transformation applied, when each one ran, and what the value was at each stage.

The same record answers the impact question in the other direction. When a source system is about to change, you can list everything downstream that will be affected before it breaks, rather than finding out from whoever notices first.

The part people underestimate

Access history matters as much as data history. Knowing where a number came from is half the answer. The other half is who was able to see it, which means the platform has to have been enforcing access rather than trusting each tool to enforce its own.

If access was enforced in five different places, the honest answer to an auditor is that you would have to check five systems and hope none of them had an exception. That answer is worse than no answer, because it tells them exactly where to look next.

On these comparisons. Billing models are stable and publicly documented, and that is what is described here. Specific list prices are not, because they move and because real contracts are commonly well below list at volume, so ask any vendor what they would actually quote you. Reviewed August 2026, next review February 2027.
Next step

See it on your own data.

Thirty minutes on the half you came for. Bring the report that breaks every month, or the decision you never settled.