Your conformity file under attack: the red team finds what you missed
The short answer
A file that has never been attacked is an essay
Every Annex IV slot can hold a document and the file can still be hollow, exactly as the Denver brief was full and false at once. Governance is what survives a motivated reader, not what reads well to its author.
What you will be able to do
- Analyze your own conformity file the way a hostile examiner does: decompose it into its claims and artifacts, trace each strong claim back to a dated source, and identify the pages that do not hold.
- Run the seven-move red-team pass against a governance file (citation check, purpose drift, date sweep, necessity probe, seam check, single-point-of-failure, backdating smell) and find the weakest page before an adversary does.
- Distinguish the five hostile readers who open your file (regulator, opposing counsel, investigative journalist, plaintiff's technical expert, board or insurer) and predict which page each opens first and why.
- Rank the findings you produce by severity (fatal, structural, cosmetic) so you fix the sanction-level problem before the typo, instead of the reverse.
- Use a current AI model as a red-team seat to surface candidate weaknesses at speed, while verifying every finding by hand, because the model that attacks your file can also hallucinate a weakness or miss a real one.
- Produce a red-team findings report against your Module 3 conformity file, the artifact that (see Topic 11.2) defends, (see Topic 11.6) rebuilds from, and the capstone board inspects in (see Topic 13.2).
- Apply the honest-gap rule under fire: when the attack finds a hole, mark it and date the fix today, never backdate, because a discovered fabrication converts a compliance gap into the kind of fraud finding that ended the Denver filing.
The ideas, one by one
The citation check is the first move because it is the attacker's first move
Take your strongest claim, try to walk it back to a dated, versioned source, and the ones that will not trace are your fake citations. The MyPillow lawyers were sanctioned because they never ran this check and met a reader who did.
Run the file from five seats and seven moves
The regulator, opposing counsel, the journalist, the plaintiff's expert, and the board each open a different page first; the seven moves (citation check, purpose drift, date sweep, necessity probe, seam check, single point of failure, backdating smell) are what you do when you get there. Coverage is the point.
Rank findings by what they cost, not by how easy they are
Fatal findings (illegal use, fabrication, full purpose drift) end you regardless of the rest; structural findings are untraceable load-bearing claims; cosmetic findings never decide an audit. Fix fatal first, always.
Use the AI seat for speed and the human for truth
A current model finds candidate weaknesses fast and does not care that you wrote the file, but it confabulates, so every finding it gives you is a lead you verify by hand. Trusting its output unverified recreates the exact failure the module is about.
The gap is survivable; the fabrication is not
When the attack finds a hole, mark it and date the fix today, never backdate. A single discovered fabrication converts the whole file from presumed-honest to presumed-suspect, which is why the Denver sanction was for the false filing, not the weak argument.
The red-team findings report is proof of a discipline, so show it
A dated, ranked, honestly blunt list of your own file's weaknesses, with fixes and owners, is the strongest evidence a board can see that your governance catches its own gaps. Hiding it reads as concealment; showing it reads as maturity.
Attack the strongest page first
Your instinct points to the section you already worry about, but that page is hedged and probably honest; the page you are proudest of is the one where an unchecked claim hides, because pride made you bold. The attacker opens the confident page first, so you should too.
The pass improves the file, not the system
If the honest finding is that the system cannot be justified at this scale or use, no better-written page fixes it; a beautifully defended file for an indefensible system hides the real problem. Keep a fatal finding fatal, and send it up the chain, not into softer language.
Build the pass into a cadence, not a panic
A file that survived an attack a year ago has not survived the year of retrains, new uses, and moving law since. Re-attack on a schedule, on every substantial change, and on every external trigger, and let at least one pass before an audit come from someone who did not build the file.
A good review leaves you unsettled, not reassured
A proofread confirms tidiness and comforts you; a real attack finds things and unsettles you. If your pass made you feel better about the file, you did not attack it. The uneasy feeling of having found a problem is the feeling of governance working, and it is the whole reason to run the pass before someone else does.
Listen to it
The same lesson, talked through by two hosts as episode 84 of the podcast.
Real cases
1. The MyPillow filing: the file that failed the citation check (United States, 2025). This is the module's anchor and the cleanest illustration of the whole discipline. In a defamation case brought by Eric Coomer against Mike Lindell in the United States District Court in Denver, Colorado, attorneys Christopher Kachouroff and Jennifer DeMaster filed a motion in February 2025 that contained more than two dozen defective citations, including references to cases that did not exist and quotations that were never written, produced with the help of a generative AI tool. Opposing scrutiny and the court checked the citations one by one, and they collapsed. Kachouroff admitted at a hearing that he had used generative AI to draft the motion, and on 7 July 2025 Judge Nina Y. Wang sanctioned each attorney 3,000 US dollars (NPR, 10 July 2025; The Colorado Sun, 7 July 2025). The failure was not the tool. It was submitting a file whose strongest pages had never been checked to a reader who would check them all. That reader is the one you are learning to be, against your own file. And the motivated reader does not stop reading: in May 2026 Judge Wang sanctioned Kachouroff again, 5,000 US dollars this time, over another materially incorrect citation in the same litigation, and her court now requires an AI-use certification with filings (Colorado Politics, 8 May 2026). Once your file fails the check, every later page you file is read with the first failure in mind.
2. The same pattern elsewhere, owned by the sibling program. Three events treated fully in the AI Data Governance program belong to this exact failure class, and they are named here as pointers only. Mata v. Avianca (United States, 2023): the first famous citation collapse, where a brief researched with ChatGPT carried six judicial decisions that did not exist and the court sanctioned counsel 5,000 US dollars. Deloitte's Australian government report (Australia, 2025): a consulting file for the Department of Employment and Workplace Relations found to contain references to academic papers that did not exist and a fabricated court quotation, ending in a partial refund and a revised report disclosing generative AI use. Air Canada's chatbot defense (Canada, 2024): a legal position, not a document, attacked the same way, when the tribunal rejected the argument that the chatbot was a separate entity and held the airline responsible for everything on its website (Moffatt v. Air Canada, 2024 BCCRT 149). Different sector, different country, identical lesson: the motivated reader is the ordinary adversary the situation always contained.
3. Pointers to attacks owned elsewhere in this program. The same failure class appears at other points in your training, each owned by its own topic. Michael Cohen fed his own lawyer fake AI-generated cases that reached a federal filing before being caught (see Topic 1.5). Motivated users jailbroke a dealership's chatbot into indefensible positions a governance file would have to answer for (see Topic 4.3). Use those as reference, not as this topic's centerpiece; the point they share is that a governed artifact is only as strong as it is under a reader who is trying to break it.
What the pattern teaches. Read the anchor and the pointers together and the shape is identical across a courtroom in Colorado, a court in New York, a government contract in Australia, and a tribunal in British Columbia. In each, someone produced a document or a position that carried the shape of authority: confident, formatted, plausible. In each, the failure was invisible until one motivated reader did the work the author assumed no one would, and then it was total, because a single proven falsehood or a single collapsed position taints everything around it. And in each, the reader who did the work was not exotic; it was the ordinary adversary the situation always contained, opposing counsel, a court, a researcher, a tribunal. Your conformity file lives in exactly this world. The only variable you control is whether the motivated reader is you, this week, at your own desk, or someone with power over you, later, in a room you do not control. This whole topic is the argument for choosing the first.
Where people go wrong
Mistake 1: Polishing the language instead of checking the claims. The strongest temptation before an audit is to make the file read better. Better prose does not survive the citation check; a traced claim does. Frances almost spent her weekend on wording and would have walked into the exact finding an auditor opens with. Attack the claims, not the sentences.
Mistake 2: Reviewing as yourself, being careful. "I read it carefully and it is fine" is not a red-team pass, because the author cannot see the author's gaps. Careful reading by the person who wrote it produces the same blind spots it produced the first time. You need a real change of role: a named hostile persona, a peer swap, or an AI seat with verification. Distance is structural, not a matter of trying harder.
Mistake 3: Trusting the AI red team's findings without checking them. Using a model to attack your file is smart; treating its output as the final report is the MyPillow failure one level up. The model confabulates: it invents weaknesses that are not there and misses ones that are. Every model-surfaced finding is a lead you verify by hand. If you skip the verification, you have replaced your judgment with a tool's, which is the habit this whole module exists to break.
Mistake 4: Treating all findings as equal. A red-team report that lists a typo next to a prohibited-use problem, with no severity ranking, will get the typo fixed and the fatal finding missed, because flat lists get worked top to bottom. Rank every finding fatal, structural, or cosmetic before you fix anything, and prove you looked hardest where it hurt most.
Mistake 5: Making the backdating smell go away by backdating. When move seven flags a page that looks too clean to be contemporaneous, the fix is never to fabricate the metadata that would make it look real. That converts a survivable gap into a fraud finding, the precise error that turned a weak brief into a sanction in Denver. Mark the gap, date the fix today, cite any real contemporaneous traces honestly, and never forge the timeline. In practice the honest trace is a one-line note attached to the page, written like this: "This analysis was originally discussed in the [name the real meeting or decision, for example the March model-review meeting]; this document was written on [today's date] to formalize that record for the file." Use the template only when a real contemporaneous trace exists to cite; if none does, the honest note is simply that the document is new, dated today, written in response to the review.
Mistake 6: Stopping at the first finding. Finding one problem feels like progress and tempts you to fix it and declare victory. A clean-looking file that gives up a structural finding in twenty minutes has more where that came from. Run all seven moves, from all five seats, to the end. The finding you skip because you were tired is the one the auditor opens with.
Mistake 7: Hiding the report instead of showing it. Some governance leads run the red-team pass and then bury the findings, reasoning that a written list of weaknesses is a liability. The opposite is true: a red-team findings report with dated fixes is the strongest evidence of a functioning governance process, and its absence is what a mature board reads as either negligence or concealment. The report is proof of diligence. Show it.
Mistake 8: Attacking your documents but never your defenses. A file is not only its pages; it is the positions you will take when challenged. If your unspoken defense is "we are only the deployer" or "the model made that decision, not us," attack that position as hard as any claim, because a defense that sounds clean until a decision-maker examines it fails exactly as Air Canada's "the chatbot is a separate entity" failed at tribunal. Voice each defense aloud in the adversary's seat and ask whether it survives an unfriendly examiner.
Mistake 9: Hardening the file for a system that should change. The pass improves the file, not the system. If the honest finding is that the necessity case cannot be made, the fix is not a more persuasive necessity page; it is a change to the system, its scale, or its use. A beautifully defended file for an indefensible system hides the real problem behind good paperwork, which is a worse outcome than a rough file that told the truth.
Mistake 10: Running the pass once and calling the file done. A conformity file is a living document; the model gets retrained, the use expands, and the law moves. A file that survived an attack a year ago has not survived the year. Build the pass into a cadence (scheduled, on every substantial change, and on every external trigger) rather than treating it as a one-time gate before a single audit.
Questions people ask
- What is red team?
- A group that deliberately adopts an adversary's goals and methods to find the weaknesses in something before a real adversary does. Here, you red-teaming your own conformity file. More on Red team
- What is red-team findings report?
- The artifact this topic produces: a dated, ranked list of every weakness the attack surfaced, each with the page it hits, why it fails, its severity, and the fix with an owner and date.
- What is citation check?
- The first attack move: taking a strong claim and trying to walk it all the way back to a dated, versioned artifact that proves it. Claims that will not trace are the file's fake citations.
- What is conformity file?
- The single evidence pack for a high-risk AI system, structured on the EU AI Act's Annex IV, assembled in (see Topic 5.6) and attacked in this topic. More on Conformity file
- What is purpose drift?
- The gap between a system's stated intended purpose and what it actually does today; when the real use moves outside the stated purpose, the file defends a system the organization is no longer running. It is the finding class the attacker most often escalates to fatal, because a file cannot defend a use the system has moved outside of. More on Purpose drift
Keep going
This lesson builds AI evaluation and testing design, and that page shows the roles that hire for it. Every Certified AI Governance Professional (CAIGP) lesson.
Watch the lesson and prove it
Proving it happens inside the program: watch, explain it in your own words, and it goes on a record employers can check.
Watch the lesson and prove it →