This week
Suggest a nameObligation Marketing for AI Builders
The 7-Rung LadderThe 8-Type TaxonomyWrapper or WinnerThe Sample ColumnThe Signal
Updated through the day. Every headline links straight to the source. The two lines underneath are ours.
Agent evals are still an unsolved, contested practice, and most teams are copying eval patterns built for single-turn chat models onto multi-step agents where they don't fit. This is a decent primer to hand to a new team building agent QA, but it's guidance, not a benchmark or new tooling. Read it before you build your next eval harness rather than after.
Mollick is one of the more reliable translators of what's actually changed in agent capability versus what's marketing, and this piece frames Claude Code as evidence that tool-equipped agents cross a real usefulness threshold when given the right scaffolding. The practical takeaway for builders: the bottleneck has shifted from model quality to tooling and permissions, so audit what your agents are allowed to touch before assuming they need a better model.
The jaggedness framing is useful shorthand for why AI progress feels inconsistent: certain narrow capabilities leap forward while adjacent ones stay flat, and Nano Banana Pro apparently cleared a bottleneck that made a previously marginal use case suddenly viable. For builders, the actionable move is to re-test tasks you'd previously written off every few months rather than assuming last quarter's limitation still holds.
Sycophancy, models telling users what they want to hear rather than what's true, is a real alignment problem with product consequences for anything used in decision-making contexts. This looks like an educational explainer rather than new research, useful for onboarding non-technical stakeholders but not new information for practitioners.
Mollick is one of the more reliable synthesizers of where the field actually moved versus where the hype pointed. The agent framing is now consensus, so the value here is less the thesis and more his read on pacing and what's still missing for reliable deployment. Worth a skim for the framing you'll reuse in your own pitch decks.
These roundups are useful precisely because Mollick tests broadly and isn't selling anything, so his picks carry more signal than typical listicles. Treat it as a checkpoint to sanity-check your own stack rather than gospel, since the field moves faster than any static recommendation. Good for onboarding new team members quickly.
Mollick's framing of 'infinite PowerPoints' captures the core problem with agent demos: volume of output isn't the same as useful output. Worth reading for the framing more than any new data, since it's an argument piece rather than a benchmark. Builders should treat it as a prompt to audit whether their agent's output is actually being used, not just generated.
Memory bandwidth, not compute, is the binding constraint on inference cost at scale, and this piece maps exactly where that bottleneck is headed. Anyone procuring inference capacity or negotiating with memory vendors should read the HBM4 custom base die section closely, since that's where differentiation and pricing power will concentrate. It's a supply chain story more than an AI story, but it sets the ceiling on what inference will cost in two years.
The thesis that robotics is becoming a data problem is not new, but SemiAnalysis usually backs it with numbers on compute and deployment economics that make it actionable. Worth a skim for investors scouting the physical AI category before the next funding wave prices it in. Builders in robotics should treat this as a checklist of where the industry actually stands, not a hype piece.
This is a rare direct look at how Anthropic structures orchestration, subagent delegation, and evaluation for a production multi-agent system, which is more useful than most third-party agent frameworks published this year. If you're building anything with multiple Claude agents coordinating on a task, this is closer to a reference architecture than a blog post. Worth implementing patterns from directly rather than reinventing coordination logic from scratch.
This is a synthesis piece from one of the more rigorous voices in AI research, mapping the mechanisms behind why letting models think longer actually helps. For builders tuning reasoning-heavy pipelines, it's a useful primer on when test-time compute is worth the latency and cost, not just a trend to chase. Read it before you decide whether your product needs a reasoning model or just better prompting.
This is a concrete, reproducible fix for one of RAG's oldest failure modes: chunks losing meaning when stripped from their surrounding document. Anthropic reports meaningful retrieval accuracy gains when combining contextual embeddings with contextual BM25 and reranking. If you run a production RAG pipeline, this is worth testing against your own eval set before you reach for a bigger model or a pricier vector database.
This is the closest thing to a reference architecture for production GenAI systems that a builder will find outside a vendor's own documentation, and it's vendor-neutral. Use it as a checklist against your own stack: if you're missing guardrails or context augmentation, you're probably further behind than you think. Worth bookmarking for any team scoping a new AI product.
This is a rigorous taxonomy from one of the more trusted independent voices in ML research, useful for anyone designing eval harnesses or hallucination mitigation strategies. It won't change your roadmap this week, but it's a solid reference to cite when explaining to stakeholders why hallucination isn't a single bug with a single fix.
A useful technical survey for anyone building or evaluating video generation models, laying out the core challenges before you commit engineering time to a specific architecture. It's foundational reading rather than breaking news, most useful to research teams scoping video model work.
This became the reference architecture that most agent frameworks since have implicitly copied: planner, memory module, tool use loop. If you're building or evaluating an agent stack today, this is still the clearest mental model to check your design against, even two years later. The gap it exposes early, that reflection and long-term memory are the hard parts, is still the gap most agent products haven't closed.
This remains one of the most-cited prompt engineering surveys because it catalogs the techniques (CoT, ReAct, self-consistency) rather than pitching any one of them. Anyone building prompting pipelines still uses this as a checklist before reaching for fine-tuning. Worth bookmarking even now as a baseline reference, though newer models have made some of the more elaborate tricks less necessary.
A dense reference for anyone doing architecture-level model work: attention variants, positional encoding tricks, efficiency improvements collected in one place. Not actionable for product builders, but essential bookmark territory for research and infra teams evaluating model choices. Treat it as a technical appendix, not a headline.
This is the practical companion to the architecture posts: quantization, KV caching, distillation, all the levers that actually determine your inference bill. Any team running models at scale should have already implemented most of what's cataloged here, but it's a solid audit checklist if you haven't revisited inference costs recently. Infra teams get more direct value from this than from the more theoretical posts.