Hyperlocal News Aggregator - Build Without a Newsroom

On this page

• How the aggregation model works
• The coverage gap problem
• The durability question
• How Wire fits the pipeline
• What to configure
• wire.yml
• Prompt overrides
• What Wire includes by default
• Limitations
• Quick start

Local newspapers closed at a rate of 2.5 per week from 2005 to 2024. The survivors cannot afford reporters for every beat. What has emerged in their place is not a replacement for journalism but a new layer beneath it: automated aggregation that handles feed ingestion, deduplication, and content scheduling so that human editors can focus on original work.

The proof of concept is already at scale. Patch's PatchAM, as reported by Columbia Journalism Review in early 2026, operates across 14,000 communities with nearly one million subscribers. Its infrastructure can expand to 30,000 communities. A single subscriber triggers generation for that zip code. No editorial staff per community. Patch has been profitable since its 2014 acquisition by Hale Global, running on national advertising from brands including T-Mobile.

Warren St. John, CEO of Patch, described the model plainly: "This is a utility. This is not the high church of journalism. This is about creating a foothold in a relationship and meeting a need."

Wire's content pipeline is built for exactly this pattern: automated monitoring, AI evaluation, and human-quality synthesis, without proprietary infrastructure. Local news is one of Wire's core use cases for automated content operations.

How the aggregation model works

Patch's architecture establishes the template Wire operators replicate: zip-code-scoped content, multi-source feed ingestion, trigger-based generation, and ad-supported monetization with no per-community editorial staff. The business case is proven and for-profit. Patch has not taken nonprofit funding.

Gannett applies the same approach in Boston suburbs, using AI to produce hyperlocal content for local sites. McClatchy's Tacoma News Tribune rewrites local stories with AI and redistributes them as national content. The Plain Dealer/Cleveland.com introduced "AI rewrite specialists" as a staff category, institutionalizing AI-assisted workflows as a defined role rather than an ad hoc tool.

The Associated Press held internal discussions in March 2026 about AI-written articles versus human reporters. Aimee Rinehart, Senior Product Manager for AI at the AP, wrote in an internal Slack message: "Many editors would prefer an AI-written article to a human-written one."

Wire operators building on this model are not replacing journalists. They are building the aggregation layer that sits below editorial.

The coverage gap problem

Automated source selection produces blind spots. CJR reporting found that Patch's Frederick, Maryland newsletter contained no content from the local daily (Frederick News-Post) or the regional Baltimore Banner, despite both actively covering the area. St. John confirmed this was not intentional: the algorithm's source selection is incomplete rather than curated.

For Wire operators, this maps directly to the build verification and source validation functions. The pipeline needs checks that flag missing expected sources, not just checks that confirm content was generated. Wire's build gates refuse thin content and broken links to removed sources. Extending that logic to flag absent expected feeds is the configuration work that separates a reliable aggregator from one that silently misses half the beat.

The durability question

The Reuters Institute's 2025 Generative AI and News report found that readers can identify AI-generated news and prefer human writing, even as media literacy declines overall. Felix Simon, author of the report, framed the core risk: "Can newsletters deliver something of value to people that they cannot easily get elsewhere for free?"

Patch's model works at launch volume. Whether subscribers stay when they recognize the content as automated is an open question the 2025 report raises but does not resolve with retention data. Only two news outlets in the country have opted out of PatchAM aggregation, per CJR reporting, suggesting content licensing norms for hyperlocal are permissive enough to support this model at scale. Subscriber loyalty over time remains unproven.

How Wire fits the pipeline

Wire's news intelligence pipeline covers the aggregation layer end to end.

news monitors RSS feeds, local government sites, and community sources for each beat: education, public safety, business, development. Wire searches the web, evaluates relevance, and flags stories worth covering. refine integrates new developments into existing stories. A zoning decision covered last month gets updated when the city council votes. The story enriches over time instead of being a one-shot article.

newsweek produces weekly community roundups across all beats. "This Week in [Town]" reports, fully cited, ready to publish or distribute as a newsletter. Citation enforcement runs throughout: every story cites its source. Meeting minutes, press releases, and public records get linked. Wire refuses to build unsourced stories.

St. John described the editorial philosophy behind Patch's curation: "People don't want everything about their community, they want the most important things." Wire's relevance evaluation applies the same filter before content reaches the page.

The enrichment loop is Wire's most distinctive feature for local news. A story about a new business opening starts as a create from web research. Three months later, news finds their first health inspection. refine integrates it. Six months later, news catches a community award. refine adds it. The article grows into a comprehensive profile without a reporter touching it. Patch ended its human-curated newsletter predecessor in 2023 because it was not financially viable. The automated enrichment model replaced it directly.

What to configure

wire.yml

Organize by beat:

nav:
  - index.md
  - Education:
    - Overview: education/index.md
  - Public Safety:
    - Overview: public-safety/index.md
  - Business:
    - Overview: business/index.md
  - Development:
    - Overview: development/index.md

Set extra.wire.refresh_days per beat. Public safety refreshes daily. Business weekly. Development bi-weekly.

Prompt overrides

Create a _styleguide.md for local journalism voice:

• Inverted pyramid: most important fact first.
• Name people, places, and dates. "The city council" is not good enough. "The Springfield City Council, in its March 18 session" is.
• Link to primary documents: meeting minutes, court filings, permits.
• No editorializing. Report facts. Let readers draw conclusions.

The location disambiguation problem is real at scale. St. John noted that his team hears "it's the wrong Springfield" at least single-digit times a week. Explicit geographic scoping in prompts and feed configuration prevents this before it reaches readers.

What Wire includes by default

Wire generates an RSS feed for reader subscriptions, llms.txt for AI news aggregators, a search index for natural-language queries like "what happened at the school board meeting," JSON-LD NewsArticle schema, and a sitemap for Google News consideration. These outputs require no additional configuration.

For operators replacing a WordPress-based local site, the WordPress migration guide covers traffic preservation during the transition.

Limitations

Wire does not handle tips, reader submissions, or real-time breaking news. For tips, pair with a form service. For breaking news, post to social media and create the Wire article after the facts are established. Wire is the archive that enriches over time, not the first-alert channel. The same enrichment loop powers competitive intelligence for business operators and niche blogs for independent publishers.

Quick start