A researcher used AI to draft a literature review. The citations looked right, real journals, real authors, plausible DOIs. The researcher read the draft, made some language edits, and submitted it.
Three of the 40 citations were backwards, real papers cited to support claims they actually contradicted. The researcher did not catch them because the abstracts sounded relevant. The reviewer did.
The paper was not retracted. But the revision letter cited all three misaligned references, and the reviewer’s credibility assessment of the entire methodology section dropped accordingly. The paper was resubmitted. It took six months longer than it should have.
The AI did not fail. The researcher who trusted it without verifying it did.
The Liability Is Not in Using AI
The liability is in the gap between what AI produces and what the human expert confirms before signing off.
Across every domain where AI-assisted expert work has entered the workflow, the pattern is the same:
In research: 40% of AI-generated references contain errors. Only 26.5% are entirely correct. The researcher who uses AI to draft a literature review and does not verify the citations is publishing with a 40% error rate in their references, most of them invisible to manual review because the papers exist and the DOIs resolve.
In law: 156 documented lawyer sanctions for AI hallucinations. Attorneys who used AI to prepare filings, briefs, and expert reports without verifying the citations, case references, and regulatory citations that the AI produced. The sanctions range from fines to adverse inference instructions to evidence exclusion.
In compliance: A compliance team uses AI to draft a response to an auditor’s finding. The response cites internal policies and regulatory requirements. Two of the cited policies have been superseded. The auditor issues a new finding: the response demonstrates a lack of current policy awareness. The original finding stands, and a second one is added.
The tool is not the risk in any of these cases. The absence of verification is.
The tool isn’t the risk. The absence of verification is.
The Cost Scales With the Stakes
Unverified AI work is cheap to produce and expensive to correct. The correction cost is not linear, it is exponential to the stakes.
| Domain | Verification Cost | Unverified Error Cost | Ratio |
|---|---|---|---|
| Research paper (40 citations) | ~$4.40 for full verification | 6-month resubmission cycle, damaged credibility | 10,000x+ |
| Expert report (Daubert-excluded) | Fraction of report cost | $50K+ in replacement fees, lost settlement positioning | 100,000x+ |
| Compliance response | Minutes of systematic check | Second auditor finding, potential enforcement action | 1,000x+ |
| Grant proposal (R01) | ~$4.40 for citation verification | Missed funding cycle, 6-month delay to resubmission | 10,000x+ |
The verification cost is essentially flat across domains, it is the cost of running the document through systematic checks. The error cost vary by orders of magnitude depending on what is at stake.
The researcher who skips verification to save $4.40 is risking a 6-month resubmission cycle. The expert witness who skips verification to save an hour is risking a $50,000 exclusion. The compliance officer who skips verification to save a morning is risking a second auditor finding.
None of these people are careless. They are unverified. The distinction matters because carelessness is a character judgment. Lack of verification is a process gap, and process gaps can be closed.
What Verification Looks Like Across Domains
The verification step is different in each domain. The principle is the same: check before it reaches the stakeholder.
For researchers: Citation verification, existence (DOIs resolve), polarity (literature treats the paper as supporting or contradicting), and alignment (the paper’s actual finding matches the claim). The Trust Stack runs all three checks and produces an audit trail.
For legal teams: Citation accuracy, methodology verifiability, case reference resolution, and the structured vulnerability scan across the six axes that opposing counsel targets. The Contradiction Register surfaces each vulnerability before the report is filed.
For compliance teams: Policy currency verification, regulatory reference accuracy, internal consistency across the response document, and traceable evidence chains for every claim made. The verification log becomes the audit trail that the auditor can review.
For grant writers: Citation alignment, methodology-design fit, power analysis verification, and adversarial pre-review that simulates study section scrutiny. The Gate determines whether the proposal is ready for submission.
Each domain has its own failure modes. None of them are caught by the human reading the AI output and saying “looks fine.” The human reader scans for relevance, not accuracy. They catch the obviously fabricated citation. They miss the backwards one.
The Verification Gap Is a Design Problem
Most organizations that use AI for expert work have not designed the verification step into their workflow. They added the tool. They did not add the check.
The researcher who has an AI writing tool but no citation verification system has a production system without quality control. The legal team that has an AI research tool but no methodology verification process has a drafting engine without a safety net. The compliance team that has an AI policy tool but no audit trail generation has a response generator without evidence.
Adding AI to an expert workflow without adding verification is like adding a manufacturing line without adding quality inspection. The output volume increases. The error rate increases with it. And the errors are the expensive kind, the ones that reach the external world before anyone catches them.
The organizations that use AI for expert work responsibly have one thing in common: they designed the verification step into the workflow before they scaled the AI usage. The verification is not an afterthought. It is part of the production process.
If your organization uses AI for expert work and the verification step is “someone reads it,” the cost of the first error will exceed the cost of building verification into the workflow by orders of magnitude. Request an architectural audit.