Run summary
- Date
- 2026-06-29
- Digest model
-
claude-sonnet-4-6· 40,255 in · 6,157 out - Sources
- 52/104 ok · 19 failed · 0 blocked · 33 empty
- Items
- 124 fetched · 124 sent to LLM
- Duration
- 350.4 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
124
items after dedup
Considered
124
reached an LLM · 100.0% of previous · 100.0% of start
Published
83
in this issue · 66.9% of previous · 66.9% of start
Fetch stats
52 ok 33 empty 19 failed 0 blocked
| Source | Status | Fresh | Kept | ms | Notes |
|---|---|---|---|---|---|
| Marginal Revolution (Tyler Cowen) | ok | 12 | 12 | 341 | |
| STAT News | ok | 12 | 12 | 225 | |
| r/MachineLearning | ok | 12 | 12 | 762 | |
| Hacker News (front page) | ok | 12 | 12 | 2519 | |
| Simon Willison | ok | 9 | 9 | 145 | |
| Vercel Blog | ok | 5 | 5 | 974 | |
| a16z (YouTube) | ok | 5 | 5 | 1504 | |
| a16z News | ok | 4 | 4 | 299 | |
| Dwarkesh Patel (YouTube) | ok | 4 | 4 | 1648 | |
| Y Combinator (YouTube) | ok | 4 | 4 | 1348 | |
| Sabine Hossenfelder | ok | 3 | 3 | 1497 | |
| Noahpinion (Noah Smith) | ok | 3 | 3 | 114 | |
| PostHog Engineering | ok | 2 | 2 | 301 | |
| The Generalist (Mario Gabriele) | ok | 2 | 2 | 176 | |
| Latent Space | ok | 2 | 2 | 100 | |
| Mo Bitar (YouTube) | ok-discovered | 2 | 2 | 2910 | |
| Hugging Face Blog | ok | 2 | 2 | 204 | |
| Interconnects (Nathan Lambert) | ok | 1 | 1 | 213 | |
| Sebastian Raschka | ok | 1 | 1 | 121 | |
| Google AI / DeepMind | ok | 1 | 1 | 164 | |
| Cloudflare Blog | ok | 1 | 1 | 385 | |
| Stripe Engineering | ok-html-fallback | 1 | 1 | 2172 | |
| Discord Engineering | ok-html-fallback | 1 | 1 | 1936 | |
| Not Boring (Packy McCormick) | ok | 1 | 1 | 140 | |
| Tomasz Tunguz | ok | 1 | 1 | 177 | |
| Hunter Walk | ok | 1 | 1 | 116 | |
| Bessemer Atlas | ok-html-fallback | 1 | 1 | 3954 | |
| Andrej Karpathy (YouTube) | ok | 1 | 1 | 69 | |
| Yannic Kilcher | ok | 1 | 1 | 540 | |
| Patrick Boyle | ok | 1 | 1 | 1507 | |
| Kyla Scanlon | ok | 1 | 1 | 1428 | |
| Fireship | ok | 1 | 1 | 1508 | |
| Ben Felix | ok | 1 | 1 | 1512 | |
| DeepLearningAI | ok | 1 | 1 | 1451 | |
| The Robot Brains Podcast | ok | 1 | 1 | 1499 | |
| Rowan Cheung | ok | 1 | 1 | 1673 | |
| Practical Engineering | ok | 1 | 1 | 1369 | |
| Money & Macro | ok | 1 | 1 | 1506 | |
| 3Blue1Brown | ok | 1 | 1 | 1497 | |
| Hannah Fry | ok | 1 | 1 | 1712 | |
| Net Interest (Marc Rubinstein) | ok | 1 | 1 | 128 | |
| Liberty Street Economics (NY Fed) | ok | 1 | 1 | 242 | |
| Google Research Blog | ok | 1 | 1 | 215 | |
| Dwarkesh Patel | ok | 1 | 1 | 135 | |
| Astral Codex Ten (Scott Alexander) | ok | 1 | 1 | 418 | |
| Works in Progress | ok | 1 | 1 | 621 | |
| Artificial Analysis | ok-html-fallback | 0 | 0 | 2707 | |
| Shopify Engineering | ok-html-fallback | 0 | 0 | 2959 | |
| LangChain Blog | ok-html-fallback | 0 | 0 | 2382 | |
| Out-Of-Pocket | ok-html-fallback | 0 | 0 | 3724 | |
| Asimov Press | ok-html-fallback | 0 | 0 | 1798 | |
| Andrej Karpathy (GitHub) | ok-html-fallback | 0 | 0 | 2207 | |
| Eugene Yan | no-items | 0 | 0 | 103 | |
| Chip Huyen | no-items | 0 | 0 | 231 | |
| Alpha Signal | html-error | 0 | 0 | 1553 | Request failed with error code 403 |
| The Batch (deeplearning.ai) | html-error | 0 | 0 | 1659 | Request failed with error code 403 |
| Data Science Weekly | rss-error | 0 | 0 | 2133 | Request failed with error code 403 |
| The Pragmatic Engineer | no-items | 0 | 0 | 202 | |
| OpenAI News | html-error | 0 | 0 | 1538 | Request failed with error code 403 |
| Fly.io Blog | no-items | 0 | 0 | 385 | |
| All Things Distributed (Werner Vogels) | no-items | 0 | 0 | 203 | |
| Kwokchain (Kevin Kwok) | no-items | 0 | 0 | 163 | |
| Conversable Economist (Timothy Taylor) | no-items | 0 | 0 | 875 | |
| Above the Crowd (Bill Gurley) | no-items | 0 | 0 | 117 | |
| Elad Gil | no-items | 0 | 0 | 1640 | |
| Sequoia Capital | no-items | 0 | 0 | 129 | |
| AVC (Fred Wilson) | no-items | 0 | 0 | 2521 | |
| Fierce Pharma | no-items | 0 | 0 | 168 | |
| Fierce Biotech | no-items | 0 | 0 | 65 | |
| Health Tech Nerds | no-items | 0 | 0 | 3259 | |
| In The Pipeline (Derek Lowe) | html-error | 0 | 0 | 2252 | Request failed with error code 403 |
| Ground Truths (Eric Topol) | rss-error | 0 | 0 | 2041 | Request failed with error code 403 |
| Rock Health Insights | no-items | 0 | 0 | 255 | |
| Decoding Bio | rss-error | 0 | 0 | 2055 | Request failed with error code 403 |
| Robert Wachter | rss-error | 0 | 0 | 2054 | Request failed with error code 403 |
| Two Minute Papers | no-items | 0 | 0 | 632 | |
| Acquired | no-items | 0 | 0 | 197 | |
| Anthropic News | no-items | 0 | 0 | 18746 | |
| r/ClaudeAI | rss-error | 0 | 0 | 2327 | Request failed with error code 429 |
| r/LLMDevs | rss-error | 0 | 0 | 2804 | Request failed with error code 429 |
| r/LocalLLaMA | rss-error | 0 | 0 | 3016 | Request failed with error code 429 |
| r/ExperiencedDevs | rss-error | 0 | 0 | 2265 | Request failed with error code 429 |
| r/medicine | rss-error | 0 | 0 | 2993 | Request failed with error code 429 |
| r/devops | rss-error | 0 | 0 | 3001 | Request failed with error code 429 |
| r/biotech | rss-error | 0 | 0 | 2997 | Request failed with error code 429 |
| AI Explained | no-items | 0 | 0 | 10 | |
| r/pharmacy | rss-error | 0 | 0 | 3008 | Request failed with error code 429 |
| r/pharmaindustry | rss-error | 0 | 0 | 3006 | Request failed with error code 429 |
| r/biotechnology | rss-error | 0 | 0 | 3006 | Request failed with error code 429 |
| Internet of Bugs | no-items | 0 | 0 | 1652 | |
| Anthropic (YouTube) | no-items | 0 | 0 | 1506 | |
| CodeEmporium | no-items | 0 | 0 | 1633 | |
| Maxinomics | no-items | 0 | 0 | 1320 | |
| Neural Breakdown with AVB | no-items | 0 | 0 | 1518 | |
| Bits about Money (Patrick McKenzie) | no-items | 0 | 0 | 229 | |
| Apricitas Economics (Joseph Politano) | no-items | 0 | 0 | 233 | |
| Bank Underground (Bank of England) | no-items | 0 | 0 | 141 | |
| Lilian Weng | no-items | 0 | 0 | 84 | |
| Meta AI Research | no-items | 0 | 0 | 1120 | |
| The Ezra Klein Show | no-items | 0 | 0 | 676 | |
| Dan Luu | no-items | 0 | 0 | 585 | |
| Brendan Gregg | no-items | 0 | 0 | 618 | |
| Klement on Investing | rss-error | 0 | 0 | 2521 | Request failed with error code 403 |
| Made of Bugs (Nelson Elhage) | no-items | 0 | 0 | 351 |
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.