Run summary
- Date
- 2026-07-13
- Digest model
-
claude-sonnet-4-6· 49,958 in · 6,365 out - Sources
- 52/104 ok · 16 failed · 0 blocked · 36 empty
- Items
- 157 fetched · 157 sent to LLM
- Duration
- 447.2 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
157
items after dedup
Considered
157
reached an LLM · 100.0% of previous · 100.0% of start
Published
31
in this issue · 19.7% of previous · 19.7% of start
Fetch stats
52 ok 36 empty 16 failed 0 blocked
| Source | Status | Fresh | Kept | ms | Notes |
|---|---|---|---|---|---|
| Alpha Signal | ok-discovered | 12 | 12 | 3596 | |
| Marginal Revolution (Tyler Cowen) | ok | 12 | 12 | 222 | |
| STAT News | ok | 12 | 12 | 1404 | |
| r/MachineLearning | ok | 12 | 12 | 775 | |
| r/ExperiencedDevs | ok | 12 | 12 | 543 | |
| Simon Willison | ok | 11 | 11 | 206 | |
| Hacker News (front page) | ok | 11 | 11 | 160 | |
| Sabine Hossenfelder | ok | 6 | 6 | 1396 | |
| Maxinomics | ok | 6 | 6 | 1430 | |
| Dwarkesh Patel (YouTube) | ok | 5 | 5 | 1599 | |
| Kyla Scanlon | ok | 4 | 4 | 1604 | |
| OpenAI News | ok-discovered | 3 | 3 | 2273 | |
| Mo Bitar (YouTube) | ok-discovered | 3 | 3 | 3091 | |
| Patrick Boyle | ok | 3 | 3 | 1501 | |
| Rowan Cheung | ok | 3 | 3 | 1502 | |
| Y Combinator (YouTube) | ok | 3 | 3 | 1496 | |
| a16z (YouTube) | ok | 3 | 3 | 1509 | |
| Cloudflare Blog | ok | 2 | 2 | 324 | |
| Vercel Blog | ok | 2 | 2 | 956 | |
| Conversable Economist (Timothy Taylor) | ok | 2 | 2 | 74 | |
| Two Minute Papers | ok | 2 | 2 | 652 | |
| Latent Space | ok | 2 | 2 | 105 | |
| Fireship | ok | 2 | 2 | 994 | |
| Noahpinion (Noah Smith) | ok | 2 | 2 | 92 | |
| Astral Codex Ten (Scott Alexander) | ok | 2 | 2 | 392 | |
| Interconnects (Nathan Lambert) | ok | 1 | 1 | 255 | |
| The Pragmatic Engineer | ok | 1 | 1 | 115 | |
| PostHog Engineering | ok | 1 | 1 | 401 | |
| Stripe Engineering | ok-html-fallback | 1 | 1 | 2296 | |
| Discord Engineering | ok-html-fallback | 1 | 1 | 1933 | |
| Not Boring (Packy McCormick) | ok | 1 | 1 | 106 | |
| The Generalist (Mario Gabriele) | ok | 1 | 1 | 197 | |
| Tomasz Tunguz | ok | 1 | 1 | 96 | |
| Bessemer Atlas | ok-html-fallback | 1 | 1 | 2937 | |
| AI Explained | ok | 1 | 1 | 9 | |
| Ben Felix | ok | 1 | 1 | 1509 | |
| Internet of Bugs | ok | 1 | 1 | 1571 | |
| CodeEmporium | ok | 1 | 1 | 1136 | |
| Money & Macro | ok | 1 | 1 | 1487 | |
| Neural Breakdown with AVB | ok | 1 | 1 | 1627 | |
| Net Interest (Marc Rubinstein) | ok | 1 | 1 | 138 | |
| Hugging Face Blog | ok | 1 | 1 | 148 | |
| Dwarkesh Patel | ok | 1 | 1 | 142 | |
| The Ezra Klein Show | ok | 1 | 1 | 460 | |
| Works in Progress | ok | 1 | 1 | 1145 | |
| Artificial Analysis | ok-html-fallback | 0 | 0 | 2586 | |
| Shopify Engineering | ok-html-fallback | 0 | 0 | 3493 | |
| Anthropic News | ok-html-fallback | 0 | 0 | 7305 | |
| LangChain Blog | ok-html-fallback | 0 | 0 | 2202 | |
| Out-Of-Pocket | ok-html-fallback | 0 | 0 | 1894 | |
| Asimov Press | ok-html-fallback | 0 | 0 | 1749 | |
| Andrej Karpathy (GitHub) | ok-html-fallback | 0 | 0 | 2127 | |
| Sebastian Raschka | no-items | 0 | 0 | 150 | |
| Chip Huyen | no-items | 0 | 0 | 157 | |
| Eugene Yan | no-items | 0 | 0 | 170 | |
| The Batch (deeplearning.ai) | html-error | 0 | 0 | 1749 | Request failed with error code 403 |
| Data Science Weekly | rss-error | 0 | 0 | 2132 | Request failed with error code 403 |
| Google AI / DeepMind | no-items | 0 | 0 | 162 | |
| Fly.io Blog | no-items | 0 | 0 | 248 | |
| All Things Distributed (Werner Vogels) | no-items | 0 | 0 | 126 | |
| Kwokchain (Kevin Kwok) | no-items | 0 | 0 | 63 | |
| Above the Crowd (Bill Gurley) | no-items | 0 | 0 | 54 | |
| Elad Gil | no-items | 0 | 0 | 1627 | |
| Hunter Walk | no-items | 0 | 0 | 103 | |
| a16z News | no-items | 0 | 0 | 61 | |
| Sequoia Capital | no-items | 0 | 0 | 59 | |
| AVC (Fred Wilson) | no-items | 0 | 0 | 2953 | |
| Fierce Pharma | no-items | 0 | 0 | 109 | |
| Fierce Biotech | no-items | 0 | 0 | 148 | |
| Health Tech Nerds | no-items | 0 | 0 | 3424 | |
| In The Pipeline (Derek Lowe) | html-error | 0 | 0 | 2076 | Request failed with error code 403 |
| Ground Truths (Eric Topol) | rss-error | 0 | 0 | 2077 | Request failed with error code 403 |
| Rock Health Insights | no-items | 0 | 0 | 543 | |
| Andrej Karpathy (YouTube) | no-items | 0 | 0 | 180 | |
| Decoding Bio | rss-error | 0 | 0 | 2037 | Request failed with error code 403 |
| Robert Wachter | rss-error | 0 | 0 | 2039 | Request failed with error code 403 |
| Yannic Kilcher | no-items | 0 | 0 | 231 | |
| Acquired | no-items | 0 | 0 | 180 | |
| r/LocalLLaMA | rss-error | 0 | 0 | 3391 | Request failed with error code 429 |
| r/LLMDevs | rss-error | 0 | 0 | 2787 | Request failed with error code 429 |
| r/ClaudeAI | rss-error | 0 | 0 | 2776 | Request failed with error code 429 |
| r/pharmacy | rss-error | 0 | 0 | 2980 | Request failed with error code 429 |
| r/devops | rss-error | 0 | 0 | 3052 | Request failed with error code 429 |
| r/biotech | rss-error | 0 | 0 | 3044 | Request failed with error code 429 |
| r/medicine | rss-error | 0 | 0 | 3029 | Request failed with error code 429 |
| r/pharmaindustry | rss-error | 0 | 0 | 2028 | Request failed with error code 429 |
| r/biotechnology | rss-error | 0 | 0 | 3521 | Request failed with error code 429 |
| DeepLearningAI | no-items | 0 | 0 | 1403 | |
| Anthropic (YouTube) | no-items | 0 | 0 | 1492 | |
| Practical Engineering | no-items | 0 | 0 | 1447 | |
| The Robot Brains Podcast | no-items | 0 | 0 | 1533 | |
| 3Blue1Brown | no-items | 0 | 0 | 1411 | |
| Bits about Money (Patrick McKenzie) | no-items | 0 | 0 | 209 | |
| Apricitas Economics (Joseph Politano) | no-items | 0 | 0 | 119 | |
| Liberty Street Economics (NY Fed) | no-items | 0 | 0 | 270 | |
| Bank Underground (Bank of England) | no-items | 0 | 0 | 218 | |
| Hannah Fry | no-items | 0 | 0 | 1507 | |
| Lilian Weng | no-items | 0 | 0 | 35 | |
| Google Research Blog | no-items | 0 | 0 | 243 | |
| Dan Luu | no-items | 0 | 0 | 1120 | |
| Meta AI Research | no-items | 0 | 0 | 1844 | |
| Klement on Investing | rss-error | 0 | 0 | 2045 | Request failed with error code 403 |
| Made of Bugs (Nelson Elhage) | no-items | 0 | 0 | 338 | |
| Brendan Gregg | no-items | 0 | 0 | 424 |
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.