Run summary
- Date
- 2026-05-15
- Digest model
-
claude-sonnet-4-6· 16,351 in · 3,040 out - Sources
- 50/68 ok · 1 failed · 0 blocked · 17 empty
- Items
- 252 fetched · 150 sent to LLM
- Duration
- 98.7 s
- User-Agent
evanalbright-digest/0.1
Retention funnel
The article path from collection to publication. Source tier is not a stage, quota, or automatic inclusion rule; it is a weak ranking and trust prior shown in the diagnostic tables below.
Fetched
252
items after dedup
Considered
150
reached an LLM · 59.5% of previous · 59.5% of start
Published
27
in this issue · 18.0% of previous · 10.7% of start
Fetch stats
50 ok 17 empty 1 failed 0 blocked
| Source | Status | Fresh | Kept | ms | Notes |
|---|---|---|---|---|---|
| Simon Willison | ok | 12 | 12 | 102 | |
| OpenAI News | ok-discovered | 12 | 12 | 1851 | |
| Endpoints News | ok | 12 | 12 | 407 | |
| STAT News | ok | 12 | 12 | 211 | |
| r/MachineLearning | ok | 12 | 12 | 906 | |
| r/ClaudeAI | ok | 12 | 12 | 1390 | |
| r/LocalLLaMA | ok | 12 | 12 | 1484 | |
| r/LLMDevs | ok | 12 | 12 | 1513 | |
| r/medicine | ok | 12 | 12 | 781 | |
| r/biotech | ok | 12 | 12 | 1436 | |
| r/ExperiencedDevs | ok | 12 | 12 | 1553 | |
| r/devops | ok | 12 | 12 | 1812 | |
| r/pharmacy | ok | 12 | 12 | 1344 | |
| Vercel Blog | ok | 9 | 9 | 297 | |
| Hacker News (front page) | ok | 8 | 8 | 301 | |
| The Economist — Finance & Economics | ok | 7 | 7 | 98 | |
| Latent Space | ok | 7 | 7 | 154 | |
| Stratechery (Ben Thompson) | ok | 5 | 5 | 49 | |
| Mo Bitar (YouTube) | ok-discovered | 5 | 5 | 3005 | |
| r/biotechnology | ok | 5 | 5 | 1572 | |
| Tomasz Tunguz | ok | 4 | 4 | 148 | |
| Two Minute Papers | ok | 4 | 4 | 1391 | |
| r/pharmaindustry | ok | 4 | 4 | 1729 | |
| Data Science Weekly | ok | 3 | 3 | 69 | |
| The Pragmatic Engineer | ok | 3 | 3 | 74 | |
| Cloudflare Blog | ok | 3 | 3 | 392 | |
| Google AI / DeepMind | ok | 2 | 2 | 221 | |
| Not Boring (Packy McCormick) | ok | 2 | 2 | 91 | |
| Ground Truths (Eric Topol) | ok | 2 | 2 | 90 | |
| Andrej Karpathy (YouTube) | ok | 2 | 2 | 227 | |
| Yannic Kilcher | ok | 2 | 2 | 1330 | |
| Interconnects (Nathan Lambert) | ok | 1 | 1 | 121 | |
| The Batch (deeplearning.ai) | ok-html-fallback | 1 | 1 | 1782 | |
| Alpha Signal | ok-html-fallback | 1 | 1 | 2059 | |
| Artificial Analysis | ok-html-fallback | 1 | 1 | 1759 | |
| Stripe Engineering | ok-html-fallback | 1 | 1 | 1827 | |
| Shopify Engineering | ok-html-fallback | 1 | 1 | 2029 | |
| Discord Engineering | ok-html-fallback | 1 | 1 | 1685 | |
| LangChain Blog | ok-html-fallback | 1 | 1 | 1853 | |
| Hunter Walk | ok | 1 | 1 | 89 | |
| Bessemer Atlas | ok-html-fallback | 1 | 1 | 2210 | |
| a16z News | ok-html-fallback | 1 | 1 | 2046 | |
| Anthropic News | ok-html-fallback | 1 | 1 | 9133 | |
| Health Tech Nerds | ok-html-fallback | 1 | 1 | 2040 | |
| Out-Of-Pocket | ok-html-fallback | 1 | 1 | 1845 | |
| Decoding Bio | ok | 1 | 1 | 69 | |
| In The Pipeline (Derek Lowe) | ok-html-fallback | 1 | 1 | 1779 | |
| Asimov Press | ok-html-fallback | 1 | 1 | 1735 | |
| Andrej Karpathy (GitHub) | ok-html-fallback | 1 | 1 | 2452 | |
| BioCentury | ok-html-fallback | 1 | 1 | 3044 | |
| Sebastian Raschka | no-items | 0 | 0 | 109 | |
| Eugene Yan | no-items | 0 | 0 | 77 | |
| Chip Huyen | no-items | 0 | 0 | 484 | |
| Fly.io Blog | no-items | 0 | 0 | 119 | |
| Netflix TechBlog | rss-error | 0 | 0 | 230 | The XML document is not well-formed |
| PostHog Engineering | no-items | 0 | 0 | 191 | |
| All Things Distributed (Werner Vogels) | no-items | 0 | 0 | 50 | |
| The Diff (Byrne Hobart) | no-items | 0 | 0 | 79 | |
| The Generalist (Mario Gabriele) | no-items | 0 | 0 | 116 | |
| Kwokchain (Kevin Kwok) | no-items | 0 | 0 | 109 | |
| Above the Crowd (Bill Gurley) | no-items | 0 | 0 | 67 | |
| Elad Gil | no-items | 0 | 0 | 1766 | |
| AVC (Fred Wilson) | no-items | 0 | 0 | 2454 | |
| Fierce Pharma | no-items | 0 | 0 | 85 | |
| Fierce Biotech | no-items | 0 | 0 | 78 | |
| Robert Wachter | no-items | 0 | 0 | 63 | |
| Rock Health Insights | no-items | 0 | 0 | 498 | |
| Acquired | no-items | 0 | 0 | 111 |
Style rules
Hard punctuation and phrase rules applied to all generated prose.
# Style — hard rules for every paragraph
These rules apply to all generated prose (digest paragraphs and study why-lines). They are mechanically enforced; output that violates them will be repaired or rejected.
## Punctuation: forbidden
- **No em-dash (—).** Not anywhere. Use semicolons, commas, periods, or parentheses.
- **No en-dash (–) as punctuation.** Only acceptable when part of an established numeric range that you are quoting verbatim from a source.
- **No double-hyphen (`--`) used as a dash substitute.** Same intent as the em-dash; same ban.
- **No standalone hyphens used as punctuation.** Hyphens are only legal as part of a hyphenated compound word that already exists in the language (`co-founder`, `self-hosted`, `mid-cap`). They are never legal as a beat or pause in a sentence.
If you find yourself reaching for any of those, you have probably written a run-on. The fix is usually to split the sentence at a semicolon or period.
## Phrases to avoid (AI-slop list)
Do not use these unless you are quoting them verbatim from a source you are summarising. The list is maintained alongside this file in `prompts/slop-blocklist.txt` and is checked programmatically.
- "load-bearing" (overused metaphor)
- "delve" / "delves into" / "delving"
- "moreover" / "furthermore" (as paragraph openers)
- "in today's fast-paced..."
- "game-changing" / "game-changer"
- "navigating the landscape"
- "tapestry"
- "intricate" (as a default adjective)
- "underscores" (as in "this underscores the importance of")
- "key takeaway"
- "ushering in"
- "transformative"
- "robust" (as filler)
- "leverage" (as a verb, when "use" works)
- "synergy"
- "comprehensive" (as filler)
- "in the realm of"
- "a testament to"
- "stands as a beacon"
- "navigate the complexities"
- "harness the power of"
- "unlock the potential"
- "the rise of"
- "in an era where"
- "paradigm shift"
If a source actually contains one of those phrases, you may quote it but you must put it in quotes and attribute it.
## Voice
- **Write like a journalist reporting news, not a critic weighing articles.** Tell the reader what happened, what was claimed, what the numbers are. Do not describe the article itself.
- Past tense for events. Present tense for ongoing dynamics. Future tense only when actually speculating.
- One thought per sentence. If a sentence has three clauses, it is at least two sentences.
- No "exciting", "huge", "massive", "ground-breaking", "incredible". Skeptical neutral by default.
- Skip the editorial throat-clearing ("It is worth noting that..."; "What's interesting here is..."). State the thing.
- Numbers in numerals (`$2.1B`, `15 minutes`). Years written in full (`2026`, not `'26`).
- No exclamation points.
## Forbidden: meta-commentary about the article
These constructions describe the article instead of reporting its content. They are banned.
- "The piece is technical but the payoff is concrete..."
- "The volume is the story."
- "An eventful month by Lambert's own description..."
- "The piece uses X as the worked example..."
- "This is a careful statistical argument dressed as a cultural essay..."
- "Raschka's coverage is among the clearest explanations of..."
- "The piece does not claim X; it claims Y." (talking about what the article does)
Banned patterns:
- Any sentence whose subject is "the piece", "the post", "the article", "the essay", "the coverage", "the analysis", "the argument", "the take", "this piece", "this post".
- Any sentence that grades the article ("worth reading", "useful", "clearer than most", "among the best", "more useful than most takes").
- Any reference to the writing itself ("dressed as a cultural essay", "technical but concrete", "tight argument", "careful piece").
**Write what the author said or what happened, not how the author said it. The author is a source; you are reporting their claim, not reviewing their prose.**
Examples:
- Bad: "Lambert's companion piece argues that open ecosystems have a compounding property."
- Good: "Lambert argues that open ecosystems compound. Fine-tunes, evals, and tooling built on open weights accumulate publicly, so the marginal cost of the next improvement falls for everyone."
- Bad: "The piece uses China's high-participation release culture as the worked example."
- Good: "China's high-participation release culture is the example Lambert leans on. Gemma 4, DeepSeek V4, Kimi K2.6, MiMo 2.5, and GLM-5.1 all shipped within weeks."
- Bad: "Raschka's coverage is among the clearest explanations of why per-token inference costs have been falling."
- Good: "Raschka traces falling per-token inference costs to three changes: KV cache sharing across layers, multi-head compression, and compressed attention over long contexts."
## Colons: use sparingly
You cannot use the em-dash, so do not now lean on the colon as a pause or pivot. A colon introduces a list, a definition, or a direct quote. It is not a dramatic beat or a "here comes the payoff" reveal.
- Bad: "The piece is technical but the payoff is concrete: these changes are what allow..."
- Bad: "The core issue is verification lag: in science, the feedback loop can take decades."
- Good: Use two sentences. "The core issue is verification lag. In science, the feedback loop can take decades."
If a sentence has more than one colon, rewrite it. If a colon sits between two complete independent clauses, it is almost always wrong; use a period.
## When in doubt
Read the sentence aloud. If you would never say it out loud to a friend, rewrite it. If a semicolon is the answer, use the semicolon. If a sentence would be better as two sentences, make it two sentences.