I have audited my travel site's legal-status dataset twice. The first audit found the same fact stored in four places, drifting independently. The second found the drift had a fifth home — the prose — and ended with me writing that a half-derived page contradicting itself "is not a risk, it's a schedule."
Six weeks later the schedule delivered again. A country's status was wrong in one file and right in another. A different country sat in the wrong continent in the database, which quietly broke the links a component built from it — two dead links on a live page, generated from data everyone had already audited.
Both audits were real work and both were correct the day they shipped. That's the problem. An audit certifies a moment. The dataset has four writers — an admin panel, an agent editing files, me in a code editor, the occasional migration — and nothing in the system held the agreement after the auditor left. Every writer produces output that is valid on its own. The typechecker is happy, the build is green, and the site contradicts itself, because validity is checked per file and truth lives across files.
So the third audit is not a session. It's a script, and it runs before anything else in the build.
