SecondBrain
Ask the Brain
Index/Conceptupdated Sat May 30 2026 08:00:00 GMT+0800 (Philippine Standard Time)

Hallucination Laundering

hallucinationaccountabilityai-governancelegal-riskbrand-fodder

Hallucination Laundering

Martin Keen's coinage in Five AI Risks That Can Get You Fired (IBM Technology) — the act of taking plausibly-confident AI output and presenting it as one's own work without verification, thereby attaching human credibility to AI fabrication.

"What started out as just kind of disposable AI slop is now presented as fact with that employee's credibility to back it up."

The mechanism

  1. AI generates plausible-sounding content (newer models hallucinate less but still hallucinate)
  2. Employee copy-pastes into a work report
  3. Submits as their own
  4. Reader trusts the work because of the human author's reputation
  5. The fabrication is now "laundered" — disposable slop is now a load-bearing claim with a real name behind it

Anchor cases (Keen)

  • Legal: "Multiple cases of lawyers submitting AI generated court filings that were packed with fabricated case citations." (The well-known Mata v. Avianca line and its successors.)
  • Executive decisions: "Many cases of executives making major business decisions based on AI generated content that they never verified."

How it differs from Fluency Illusion

  • Fluency Illusion is about the reader — polished output reads like understanding even when the underlying knowledge isn't there. Cognitive science framing (recognition ≠ retrieval).
  • Hallucination laundering is about the author — willingly attaching credibility to unverified output. Governance / accountability framing.

Same root cause (LLMs confidently generate plausible but false content), different harms (the reader is fooled vs the author hides the seam).

Accountability

"If the AI writes it and it turns out to be wrong, whose name is on the document? It's not the AI. It's the person who submitted it. And that's the person who could end up getting fired."

This is the cleanest articulation in the wiki of why AI output is not a defense. Career-risk framing makes it concrete for individual contributors, not just CISOs.

Why it matters strategically

  • Verification is the unscaled work — if AI generates 10× as much output, the verification burden doesn't go away; it scales with it. Concentrates new value on judgment + attribution, complementing Code Is Free (implementation is no longer scarce).
  • Tool reflex isn't a defense — "the model told me" doesn't transfer accountability. The org's exposure rolls up through the person whose name is on the work.
  • Connects to AWARE Framework's observability pillar — if you can't reconstruct what the agent did and why, you also can't separate human judgment from AI assertion in the work product.

Sources