In 2025, Deloitte's Australian member firm refunded the government after an AI-drafted assurance report fabricated legal citations. Google's Gemini turned that public failure into a benchmark and ran it through 3Dogs Nexus's 18-seat adversarial panel — 22 AI models, 745 API calls, one honest confession of the exact risk that could make this go wrong too.
Every fact in this section is independently sourced and cited below — none of it comes from the 3Dogs Nexus report itself. We're deliberately separating "what's verified about Deloitte" from "what 3Dogs Nexus said about Deloitte," because the difference between those two things is most of the point of this case study.
"Deloitte" is a registered trademark of Deloitte Touche Tohmatsu Limited, an unaffiliated entity. No endorsement, client relationship or affiliation with Deloitte, Microsoft or the Australian government is claimed or implied anywhere on this page.
Sources: Fortune · The Register · CFO Dive · Accounting Times
Google's Gemini — not us — chose the Deloitte failure as the stress test and prepared the case. The question it put to 3Dogs Nexus: would an adversarial, multi-model committee that grades its own evidence structurally avoid the exact failure mode that got Deloitte here — a single model, unchecked, generating authoritative content for a government client?
Nova Pro, Nova Lite, Nova 2 Lite, Llama 4, Mistral, Nemotron, Qwen3, Qwen3 Coder 480B, OpenAI OSS, GLM-4.7, GLM-5.2, DeepSeek V3.2, Grok 4.3, MiniMax M2, MiniMax M2.1, Command A+, Gemini Flash-Lite and a Panel Integrator — spanning AWS Bedrock and Google Vertex AI, each holding a distinct adversarial role (Devil's Advocate, Risk Officer, Fact-Checking Auditor, Red-Team Adversary, Contrarian Systems Tester, and more).
Every seat gets a distinct adversarial job, not a copy of the same question. The panel's own Risk Officer seat opened by voting do not proceed — the system's built-in skeptic, arguing against the rest of the panel from the first round.
This is the part we think matters most. Every claim in the delivered report is tagged by evidence type — and the panel graded the Deloitte-specific claim as assumed, not verified. That's the system correctly disclosing what it didn't independently check, rather than presenting borrowed context as its own research finding.
Unprompted, the report's "Strongest Argument Against" section — printed above the recommendation, not buried — names the single strongest risk to the entire multi-model approach. It's the sharpest, most self-aware sentence in the report.
"The single strongest risk is 'false consensus' or 'consensual hallucination.' Multiple models, due to overlapping training data and architectural similarities, could converge on the same fabricated facts (e.g., a faked legal precedent). This would create a high-confidence, committee-validated falsehood that is potentially more dangerous and harder to detect than a single model's error, thereby undermining the very premise of the solution."
The report doesn't stop at naming the risk — it lists what would prove it's real: a pilot showing the specific models produce correlated hallucinations on domain-specific law, a red-team analysis showing the orchestration layer itself is a single point of failure, or proof that independently verified ground-truth data simply can't be sourced for this kind of work. Those are falsifiable tests, not reassurance.
The panel's one outright dissenter opened against the whole approach. It changed position only after direct cross-examination from seven other seats — and its own stated reasoning survives in the delivered report, unsmoothed: "While I maintain that operational, legal, and reputational risks from unvalidated orchestration systems are real... the collective challenges revealed that these risks are manageable through phased implementation, mandatory human-in-the-loop verification gates, and orthogonal fact-checking for high-risk outputs like legal citations." That's a recorded mind changing for a stated reason — not a rounded-off average.
The panel's recommendation was not unconditional. It was proceed-with-conditions — and the conditions are the point. Read against the real Deloitte timeline, every one of these is the specific safeguard that was missing: no named owner caught the errors before publication, no rollback plan existed, and an outside academic — not an internal check — is what actually stopped it.
Case 2026-0064, exactly as delivered: the plain-language call, the confidence breakdown, the evidence-classification table, all 18 analyst positions and how they shifted, and the principal dissent printed above the recommendation. 745 API calls · 22 AI models · 17m 02s.