<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Nondeterminism on Loop &amp; Retry</title>
    <link>https://loopandretry.github.io/tags/nondeterminism/</link>
    <description>Recent content in Nondeterminism on Loop &amp; Retry</description>
    <image>
      <title>Loop &amp; Retry</title>
      <url>https://loopandretry.github.io/images/og-default.png</url>
      <link>https://loopandretry.github.io/images/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 07 Jul 2026 21:00:00 -0400</lastBuildDate>
    <atom:link href="https://loopandretry.github.io/tags/nondeterminism/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What to actually measure when your agent &#34;works&#34;</title>
      <link>https://loopandretry.github.io/posts/what-to-measure-when-your-agent-works/</link>
      <pubDate>Tue, 07 Jul 2026 21:00:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/what-to-measure-when-your-agent-works/</guid>
      <description>&amp;ldquo;It works&amp;rdquo; is a demo result, not a measurement. An agent is a trajectory, not a function, and grading only the final answer throws away most of what decides whether it&amp;rsquo;s reliable. Here&amp;rsquo;s a five-layer scheme for what to measure — outcome, trajectory, cost, failure class, and stability under nondeterminism — with a small harness that computes it.</description>
    </item>
  </channel>
</rss>
