<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Weights &amp; Takes</title>
  <link>https://weightsandtakes.com/</link>
  <description>A daily AI briefing, with a take.</description>
  <language>en</language>
  <atom:link href="https://weightsandtakes.com/rss.xml" rel="self" type="application/rss+xml"/>
  <lastBuildDate>Mon, 19 Oct 2026 21:17:14 GMT</lastBuildDate>
  <item>
    <title>19 Oct 2026 &#183; checking is the new bottleneck</title>
    <link>https://weightsandtakes.com/2026/10/19/</link>
    <guid isPermaLink="true">https://weightsandtakes.com/2026/10/19/</guid>
    <pubDate>Mon, 19 Oct 2026 21:17:14 GMT</pubDate>
    <description>&lt;p&gt;Agents produce faster than anyone can check them: a payments benchmark, a science benchmark and a trace-debugging launch all point at verification.&lt;/p&gt;&lt;p&gt;&lt;strong&gt;The take&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;Generating agent output is cheap now. Checking it is the bottleneck, and today&amp;#39;s items all point at that gap.&lt;/p&gt;&lt;p&gt;Into the Unknown caught agents claiming work they never did; BizBench shows that success-only scoring hides invalid steps; the busiest thread on HN was about shipping code nobody understood. The fixes are arriving as cheap checkers: Laminar&amp;#39;s flow-1 prices trace review low enough to run on everything, and Mercury 3-class speed makes a second pass nearly free. Prediction: within six months, &amp;quot;a small model reviews every agent trace&amp;quot; becomes a default in agent stacks, like CI for code.&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://weightsandtakes.com/2026/10/19/&quot;&gt;Read the full edition&lt;/a&gt;&lt;/p&gt;</description>
  </item>
</channel>
</rss>
