posts · 2026-06-29

This piece connects several recent events into a clean narrative: Anthropic's Fable 5 got blocked three days after launch, the Pentagon had already labeled Anthropic a supply-chain risk, and the Trump administration swung from hands-off to heavy-handed. The authors use China's 2020 crackdown on Jack Ma and Ant Group as a warning that the US is now hurting itself. I'd discount this a bit — it's an op-ed, not investigative reporting, and a lot of the details are secondhand from public coverage. The post doesn't spell out Fable 5's technical specs, the specific jailbreak evidence, or what the actual sticking points in the negotiation are. But the core argument holds: when you turn export controls on your own leading AI company without clear explanation, you erode trust with both talent and allies. The article flags that foreign researchers are reconsidering their career plans and allies are questioning whether they can rely on US models — those two threads matter more than any single access block. Don't read this as 'the US is doomed.' The authors themselves note that US legal protections and deep capital markets make an Alibaba-style two-thirds market cap wipeout unlikely. The more useful take: trust between the government and labs is burning down fast, and rebuilding it is a lot harder than signing an executive order.

I clicked because the author shares two copy-pasteable prompts, not just hand-waving about first principles. The first forces the AI to rebuild reasoning from base facts instead of analogies—it once surfaced a hidden traffic-routing flaw that triggered a full rewrite. The second makes the AI attack the code as a malicious user, catching OOM infinite loops and future-timestamp pollution that manual review would likely miss. Together they create a generate-then-verify loop; the project handled 10M+ requests last week. I'd save both prompts and try them immediately, but note: the post only gives paraphrased descriptions, not the full prompt text, and results probably depend heavily on your task type.

This piece is worth your time because it reverse-engineers a classic AI PR case using the hardest evidence available: ECMWF's public operational data. When DeepMind dropped GraphCast in November 2023, Chinese tech media ran with 'crushed' and 'dominated.' But ECMWF's effective forecast days curve—publicly tracked since the 1980s—gains roughly 0.15 days per year, and 2023 shows no jump. Technical Memorandum TM 918 plots GraphCast as a parallel line above the main curve, not a turning point on it. The '90% win rate across 1,380 metrics'? That's 6 variables × 37 pressure levels × multiple lead times, counted repeatedly. A single-variable advantage gets multiplied across dimensions, inflating the headline number while the end metric—actual forecast days—doesn't budge. What's more telling: none of the 15 Chinese articles quoted an independent meteorologist. In English media, only New Scientist interviewed one—Ian Renfrew from UEA—who pointed out GraphCast doesn't do data assimilation, the most compute-heavy step (50-67% of the workload). It feeds on pre-processed data from other systems. Later releases GenCast and WeatherNext 2 pushed win rates to 97% and 99%, but the baseline quietly shifted from ECMWF's operational system to the team's own previous model. The post leaves you with a practical checklist: when you see 'crushed' headlines, find the end business metric, count truly independent sources, and check whether the field has public long-term monitoring. Weather does. Most AI verticals don't.

This piece is worth opening because it names a pain point a lot of builders hit: when an agent polls task status for more than 30 seconds, the model often hallucinates task names or prematurely declares completion. MCP 2026's Tasks primitive hands the state machine (created → working → three terminal states) to deterministic host code, leaving the model to only initiate tasks and interpret final results. Tool developers get a three-state execution.taskSupport flag (forbidden / optional / required) to decide sync vs async per tool—the protocol doesn't force a one-size-fits-all choice. Tasks is still experimental. Failure restart semantics and push mechanisms aren't finalized, so don't rip out working systems yet. But the architectural principle applies now: before writing any prompts, separate reasoning from orchestration. Lock down orchestration with hard code; let the model handle reasoning in a self-correcting loop.

Tunguz lays out a cost structure that's hard to ignore: Anthropic burns $2M per employee on compute, while the top 1% of software companies spend $89k per engineer and the median spends $137 a year. The gap is wild. He maps three 2029 scenarios. Bear case: token prices keep falling 10x/year and open-weight models close the quality gap, so AI spend settles at 41% of engineer salary. Bull case: agentic workflows drive a 24x jump in token consumption, and the whole market converges to Anthropic's current 230% ratio — $596k per engineer per year. I'd discount the precision a bit. All three paths lean on Ramp's spending index and Goldman's token forecast, but the post doesn't say which one to model for 2027. The Bull case also assumes frontier model prices hold steady and supply stays tight, which already feels shaky in mid-2026. The real question isn't the exact number. It's what happens when the AI bill starts looking like another headcount. Do you ration tokens per role, or do you hire fewer people and run more agents? That tradeoff is the thing to watch.