How this issue was assembled

Every digest is drafted by an autonomous pipeline. No human edits before publication. This page shows the issue's run telemetry and candidate decisions alongside the pipeline's current source registry and editorial instructions.

Run summary

Date
2026-07-06
Digest model
claude-sonnet-4-6 · 43,871 in · 5,864 out
Sources
46/104 ok · 17 failed · 0 blocked · 41 empty
Items
133 fetched · 133 sent to LLM
Duration
254.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
133
items after dedup
Considered
133
reached an LLM · 100.0% of previous · 100.0% of start
Published
50
in this issue · 37.6% of previous · 37.6% of start

Fetch stats

46 ok 41 empty 17 failed 0 blocked
Source Status Fresh Kept ms Notes
Simon Willison ok 12 12 103
Alpha Signal ok-discovered 12 12 2982
Marginal Revolution (Tyler Cowen) ok 12 12 351
STAT News ok 12 12 277
r/MachineLearning ok 12 12 953
Dwarkesh Patel (YouTube) ok 11 11 1510
Hacker News (front page) ok 6 6 3458
Sabine Hossenfelder ok 5 5 1343
Latent Space ok 4 4 146
Kyla Scanlon ok 4 4 1498
Vercel Blog ok 3 3 704
Conversable Economist (Timothy Taylor) ok 3 3 75
Rowan Cheung ok 3 3 1637
Noahpinion (Noah Smith) ok 3 3 69
a16z (YouTube) ok 3 3 1698
Not Boring (Packy McCormick) ok 2 2 65
Two Minute Papers ok 2 2 212
Money & Macro ok 2 2 1628
Maxinomics ok 2 2 1363
Astral Codex Ten (Scott Alexander) ok 2 2 116
Stripe Engineering ok-html-fallback 1 1 1981
Discord Engineering ok-html-fallback 1 1 1769
The Generalist (Mario Gabriele) ok 1 1 73
a16z News ok 1 1 65
Bessemer Atlas ok-html-fallback 1 1 4618
Yannic Kilcher ok 1 1 48
Mo Bitar (YouTube) ok-discovered 1 1 2867
AI Explained ok 1 1 6
Patrick Boyle ok 1 1 13
Fireship ok 1 1 6
Ben Felix ok 1 1 1512
CodeEmporium ok 1 1 1372
The Robot Brains Podcast ok 1 1 1660
3Blue1Brown ok 1 1 1359
Hannah Fry ok 1 1 1629
Net Interest (Marc Rubinstein) ok 1 1 249
Hugging Face Blog ok 1 1 191
The Ezra Klein Show ok 1 1 281
Cloudflare Blog ok 0 0 335
Artificial Analysis ok-html-fallback 0 0 2306
Shopify Engineering ok-html-fallback 0 0 2625
LangChain Blog ok-html-fallback 0 0 2179
Out-Of-Pocket ok-html-fallback 0 0 1846
Asimov Press ok-html-fallback 0 0 1705
Andrej Karpathy (GitHub) ok-html-fallback 0 0 2201
Anthropic News ok-html-fallback 0 0 17282
Interconnects (Nathan Lambert) no-items 0 0 161
Sebastian Raschka no-items 0 0 90
Eugene Yan no-items 0 0 187
Chip Huyen no-items 0 0 465
The Batch (deeplearning.ai) html-error 0 0 1651 Request failed with error code 403
Data Science Weekly rss-error 0 0 2040 Request failed with error code 403
Google AI / DeepMind no-items 0 0 282
The Pragmatic Engineer no-items 0 0 151
Fly.io Blog no-items 0 0 175
OpenAI News no-items 0 0 2448
PostHog Engineering no-items 0 0 291
All Things Distributed (Werner Vogels) no-items 0 0 43
Kwokchain (Kevin Kwok) no-items 0 0 59
Tomasz Tunguz no-items 0 0 129
Above the Crowd (Bill Gurley) no-items 0 0 89
Elad Gil no-items 0 0 1676
Hunter Walk no-items 0 0 85
Sequoia Capital no-items 0 0 67
AVC (Fred Wilson) no-items 0 0 2576
Fierce Pharma no-items 0 0 48
Fierce Biotech no-items 0 0 49
Health Tech Nerds no-items 0 0 3904
In The Pipeline (Derek Lowe) html-error 0 0 2830 Request failed with error code 403
Ground Truths (Eric Topol) rss-error 0 0 2179 Request failed with error code 403
Rock Health Insights no-items 0 0 249
Andrej Karpathy (YouTube) no-items 0 0 51
Decoding Bio rss-error 0 0 2038 Request failed with error code 403
Robert Wachter rss-error 0 0 2039 Request failed with error code 403
Acquired no-items 0 0 117
r/LocalLLaMA rss-error 0 0 3059 Request failed with error code 429
r/LLMDevs rss-error 0 0 2963 Request failed with error code 429
r/ClaudeAI rss-error 0 0 2715 Request failed with error code 429
r/ExperiencedDevs rss-error 0 0 2298 Request failed with error code 429
r/devops rss-error 0 0 3004 Request failed with error code 429
r/medicine rss-error 0 0 2997 Request failed with error code 429
r/biotech rss-error 0 0 3000 Request failed with error code 429
r/pharmacy rss-error 0 0 3007 Request failed with error code 429
r/biotechnology rss-error 0 0 3003 Request failed with error code 429
r/pharmaindustry rss-error 0 0 3141 Request failed with error code 429
DeepLearningAI no-items 0 0 1504
Anthropic (YouTube) no-items 0 0 1498
Internet of Bugs no-items 0 0 1651
Practical Engineering no-items 0 0 1351
Neural Breakdown with AVB no-items 0 0 1643
Y Combinator (YouTube) no-items 0 0 1500
Bits about Money (Patrick McKenzie) no-items 0 0 240
Apricitas Economics (Joseph Politano) no-items 0 0 171
Liberty Street Economics (NY Fed) no-items 0 0 273
Bank Underground (Bank of England) no-items 0 0 230
Lilian Weng no-items 0 0 23
Google Research Blog no-items 0 0 283
Dwarkesh Patel no-items 0 0 117
Meta AI Research no-items 0 0 1404
Dan Luu no-items 0 0 536
Works in Progress no-items 0 0 978
Brendan Gregg no-items 0 0 471
Klement on Investing rss-error 0 0 2208 Request failed with error code 403
Made of Bugs (Nelson Elhage) no-items 0 0 2185

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.