Article 01 ended with a shelf – the people and benchmarks I read to tell honest AI signal from sponsored noise. A shelf is a start. It is not yet a system: it does not tell you what each source is for, how often to check it, or who to tune out so the good signal can get through. This is the shelf turned into a working diet.
- Why "who should I follow" is the wrong question, and the sharper one: what job is this source the best in the world at.
- The five jobs a low-noise AI diet has to fill, and the one or two names that fill each – no duplicates, no padding.
- A weekly rhythm and a short mute list, because the discipline is as much what you stop reading as what you start.
Open any feed in 2026 and the loudest voice on AI is selling something. A course that gates the real content. A tool reviewed by the channel it sponsors. A post promising a six-figure income from five apps and no experience. The signal underneath is real and it matters more than it ever has – which is exactly why it is worth the work of digging it out from under the people whose actual product is your attention.
The Incentive Test
Before a source earns a place in your week, run it through three questions. They are the same questions I ask of a vendor benchmark, pointed at a person.
- What are they selling – and does the claim survive it? Everyone has an incentive; that is fine. The test is whether the insight still holds once you assume they want you to buy the thing. If the value evaporates without the sales pitch, it was the pitch.
- Do they grade themselves? The strongest credential is not being right – it is publishing predictions, then scoring them in public, or demonstrating every claim with running code. People who show their corrections are people who have a process. People who only ever announce are performing.
- Would this be worth reading with zero engagement? If a piece only makes sense as something designed to be shared – the screenshot, the hot take, the thread with a hook – it was built for the algorithm, not for you.
Five Jobs, Not Forty Follows
You do not need forty AI accounts. You need five jobs filled by people who are genuinely the best at them. Here is each job, what it is for, and the sources I trust to do it. The one-liners I gave in Article 01 said who they are; these say what to use them for.
-
AI Futures Projectblog.aifutures.orgThe AI-2027 team. Read it when you want a forecast that comes with a published self-grading rather than a confident year.
-
Don't Worry About the Vase · Zvithezvi.substack.comThe most exhaustive weekly digest there is. Read it when you want one place that already separated this week's claims from the evidence.
-
Peter Wildefordblog.peterwildeford.comA professional forecaster reading the same news you do, with calibration. Read it for the probability behind a headline.
-
METR Time Horizonsmetr.orgIf you track one capability number, track this one: how long a task a model finishes on its own. The field's closest thing to a speedometer.
-
Epoch AIepochai.substack.comThe measurement layer – compute trends, chip economics, training-run data. Where the supply-side constraints are actually quantified.
-
Artificial Analysisartificialanalysis.aiIndependent price, speed, and quality across every major provider. The comparison spreadsheet you would otherwise build by hand.
-
OpenRouter Rankingsopenrouter.ai/rankingsReal usage share across hundreds of models and apps – what people actually pay to run, which beats any vendor slide.
-
Scale SEAL + LMArenalabs.scale.com · lmarena.aiPrivate, uncontaminated eval sets and blind human-preference voting. The two defences against a model trained to ace the test.
-
Ahead of AI · Sebastian Raschkamagazine.sebastianraschka.comLLM research explained for engineers who build. The cleanest bridge between the papers and your codebase.
-
Interconnects · Nathan Lambertinterconnects.aiPost-training, RLHF, and open models from someone who does the work. Where to learn how a model is actually made good after pre-training.
-
Friendly Paper Reviewfriendlypaperreview.comWalks through significant papers without assuming you have read the last fifty. The antidote to abstract-only knowledge.
-
Hyperdimensional · Dean W. Ballhyperdimensional.coAI policy taken seriously and explained clearly – how the rules of this technology are actually being made, and what that means for builders.
-
Import AI · Jack Clarkimportai.substack.comAn Anthropic co-founder's weekly on policy and capabilities. A decade of consistent signal – read the framing, hold the source in mind.
A note on that last job: the labs themselves are worth reading, with a rule attached. Weight their operational numbers – the ones describing their own engineering reality – above their predictions about the future, which always point the same direction as their fundraising. I followed that rule when I cited the labs in Where This Is Going: their internal metrics earned trust, their timelines earned a discount.
A Diet, Not a Drip
Sources are half the problem. The other half is cadence – matching how often you check something to how fast it actually changes. Capability does not move hourly, so reading it hourly only buys you anxiety. This is the rhythm I keep.
What to Mute
A signal map is also a map of what to ignore. These are the genres I have learned to tune out – not because the people are bad, but because the format is built to convert attention, not to inform it.
- The sponsored reviewer. If the tool pays the channel, the review is an ad with production values. Useful as a demo, worthless as a verdict.
- The urgency merchant. "You are already behind. Buy now." Manufactured urgency is the oldest sales tactic there is; AI just gave it a new coat of paint.
- The never-scored oracle. The permanent bull and the permanent doomer both make loud, dateless predictions and never grade a past one. Confidence without a track record is theatre.
- The screenshot. A clever exchange with a chatbot is an anecdote, not a capability. One impressive output proves a model can, never that it reliably will.
In a field this loud, your edge is not how much you consume – it is how well you choose. Curate your inputs the way you curate your code reviews: a few trusted sources, read closely, beat a thousand you skim and a hundred you never should have let in.