I Built RuntimeWire: A One-Person, Mostly-Autonomous AI Newsroom
Ryan Merket has created RuntimeWire, a one-person, mostly-autonomous AI newsroom that covers tech news. The publication automates the process of ingesting, curating, and publishing stories, allowing it to operate continuously. Merket's approach combines engineering with journalism, focusing on efficiency and automation to deliver timely news.
- ▪RuntimeWire is a real-time tech publication run by a single person using automation.
- ▪The publication's pipeline includes ingesting stories, curating them, and publishing approved content.
- ▪Merket's system pulls in stories from various sources and uses models to classify and score them.
Hacker News (AI / LLM) files mainly under ai. We currently carry 3,344 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Medium |
| Canonical URL | https://blog.ryanmerket.com/how-i-built-runtimewire-a-one-person-mostly-autonomous-ai-newsroom-994319fd76da |
| Publication time | Fri, 29 May 2026 19:53:13 +0000 |
| Retrieval time | 2026-05-29T20:00:03.801Z |
| Last seen | 2026-05-29T20:00:41.828Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | m5UVO95h2E5_ |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
How I Built RuntimeWire: A One-Person, Mostly-Autonomous AI NewsroomRyan Merket10 min read·Just now--ListenShareThere’s a particular kind of madness that sets in when you decide to build a newsroom by yourself. Not a blog. A newsroom — something that wakes up before you do, reads the entire startup and AI firehose, decides what matters, writes it up, makes a video about it, narrates that video, posts it to YouTube and X, drops an episode into a podcast feed, and emails a recap to subscribers. All before you’ve had coffee.That’s RuntimeWire.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Medium.
Discussion
0 commentsMore from Medium
