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-09
Digest model
claude-sonnet-4-6 · 38,517 in · 6,198 out
Sources
49/104 ok · 18 failed · 0 blocked · 37 empty
Items
133 fetched · 133 sent to LLM
Duration
310.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
133
items after dedup
Considered
133
reached an LLM · 100.0% of previous · 100.0% of start
Published
84
in this issue · 63.2% of previous · 63.2% of start

Fetch stats

49 ok 37 empty 18 failed 0 blocked
Source Status Fresh Kept ms Notes
Alpha Signal ok-discovered 12 12 2023
Vercel Blog ok 12 12 890
Marginal Revolution (Tyler Cowen) ok 12 12 343
STAT News ok 12 12 172
r/MachineLearning ok 12 12 815
Simon Willison ok 9 9 310
Hugging Face Blog ok 7 7 196
Latent Space ok 4 4 66
Liberty Street Economics (NY Fed) ok 4 4 86
Cloudflare Blog ok 3 3 276
Dwarkesh Patel (YouTube) ok 3 3 1499
Rowan Cheung ok 3 3 1627
Maxinomics ok 3 3 1425
Sabine Hossenfelder ok 3 3 1499
The Pragmatic Engineer ok 2 2 297
Tomasz Tunguz ok 2 2 157
Kyla Scanlon ok 2 2 1651
Fireship ok 2 2 1528
Practical Engineering ok 2 2 1409
a16z (YouTube) ok 2 2 1606
Google AI / DeepMind ok 1 1 170
Fly.io Blog ok 1 1 319
PostHog Engineering ok 1 1 313
Stripe Engineering ok-html-fallback 1 1 2108
Discord Engineering ok-html-fallback 1 1 2145
Conversable Economist (Timothy Taylor) ok 1 1 336
All Things Distributed (Werner Vogels) ok 1 1 120
Bessemer Atlas ok-html-fallback 1 1 6251
Two Minute Papers ok 1 1 1098
Mo Bitar (YouTube) ok-discovered 1 1 2447
AI Explained ok 1 1 10
Patrick Boyle ok 1 1 1508
Ben Felix ok 1 1 1520
Anthropic (YouTube) ok 1 1 1591
CodeEmporium ok 1 1 1591
Y Combinator (YouTube) ok 1 1 1454
Noahpinion (Noah Smith) ok 1 1 116
Bank Underground (Bank of England) ok 1 1 157
Google Research Blog ok 1 1 270
The Ezra Klein Show ok 1 1 427
Astral Codex Ten (Scott Alexander) ok 1 1 410
Works in Progress ok 1 1 1090
Artificial Analysis ok-html-fallback 0 0 2603
Shopify Engineering ok-html-fallback 0 0 2884
LangChain Blog ok-html-fallback 0 0 2216
Out-Of-Pocket ok-html-fallback 0 0 1922
Anthropic News ok-html-fallback 0 0 11974
Asimov Press ok-html-fallback 0 0 2276
Andrej Karpathy (GitHub) ok-html-fallback 0 0 2099
Interconnects (Nathan Lambert) no-items 0 0 329
Sebastian Raschka no-items 0 0 196
Chip Huyen no-items 0 0 325
Eugene Yan no-items 0 0 193
The Batch (deeplearning.ai) html-error 0 0 1861 Request failed with error code 403
Data Science Weekly rss-error 0 0 2149 Request failed with error code 403
OpenAI News html-error 0 0 1538 Request failed with error code 403
Not Boring (Packy McCormick) no-items 0 0 110
Kwokchain (Kevin Kwok) no-items 0 0 83
The Generalist (Mario Gabriele) no-items 0 0 170
Above the Crowd (Bill Gurley) no-items 0 0 60
Elad Gil no-items 0 0 1760
Hunter Walk no-items 0 0 67
a16z News no-items 0 0 325
Sequoia Capital no-items 0 0 144
AVC (Fred Wilson) no-items 0 0 2221
Fierce Pharma no-items 0 0 147
Fierce Biotech no-items 0 0 67
Health Tech Nerds no-items 0 0 2674
Ground Truths (Eric Topol) rss-error 0 0 2288 Request failed with error code 403
In The Pipeline (Derek Lowe) html-error 0 0 2784 Request failed with error code 403
Andrej Karpathy (YouTube) no-items 0 0 79
Rock Health Insights no-items 0 0 466
Robert Wachter rss-error 0 0 2254 Request failed with error code 403
Decoding Bio rss-error 0 0 2289 Request failed with error code 403
Acquired no-items 0 0 239
Yannic Kilcher no-items 0 0 1610
r/LLMDevs rss-error 0 0 2752 Request failed with error code 429
r/ClaudeAI rss-error 0 0 2691 Request failed with error code 429
r/LocalLLaMA rss-error 0 0 3431 Request failed with error code 429
r/ExperiencedDevs rss-error 0 0 2658 Request failed with error code 429
r/medicine rss-error 0 0 2946 Request failed with error code 429
r/devops rss-error 0 0 2996 Request failed with error code 429
r/biotech rss-error 0 0 2995 Request failed with error code 429
r/pharmacy rss-error 0 0 3002 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 3005 Request failed with error code 429
Internet of Bugs no-items 0 0 1503
DeepLearningAI no-items 0 0 1368
The Robot Brains Podcast no-items 0 0 1675
Money & Macro no-items 0 0 1409
Neural Breakdown with AVB no-items 0 0 1500
3Blue1Brown no-items 0 0 1499
Hannah Fry no-items 0 0 1396
Net Interest (Marc Rubinstein) no-items 0 0 91
Apricitas Economics (Joseph Politano) no-items 0 0 188
Bits about Money (Patrick McKenzie) no-items 0 0 286
Lilian Weng no-items 0 0 53
Hacker News (front page) no-items 0 0 1277
Dwarkesh Patel no-items 0 0 158
Meta AI Research no-items 0 0 1159
Dan Luu no-items 0 0 1064
Brendan Gregg no-items 0 0 1078
Klement on Investing rss-error 0 0 2690 Request failed with error code 403
Made of Bugs (Nelson Elhage) no-items 0 0 291

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.