<?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>Metrics on Loop &amp; Retry</title>
    <link>https://loopandretry.github.io/tags/metrics/</link>
    <description>Recent content in Metrics 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>Mon, 13 Jul 2026 18:10:00 -0400</lastBuildDate>
    <atom:link href="https://loopandretry.github.io/tags/metrics/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Your agent&#39;s failures are silent: measuring failure modes in production</title>
      <link>https://loopandretry.github.io/posts/measuring-agent-failure-in-production/</link>
      <pubDate>Mon, 13 Jul 2026 18:10:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/measuring-agent-failure-in-production/</guid>
      <description>Most agent failures don&amp;rsquo;t throw. The run returns a result, exit code zero, and the result is wrong — or it burns an hour and quietly gives up. If your monitoring only counts exceptions, you&amp;rsquo;re blind to the failures that actually cost you. A taxonomy of agent failure modes and the specific instrumentation that catches each one before your users or your bill do.</description>
    </item>
    <item>
      <title>Your LLM-as-judge is lying to you</title>
      <link>https://loopandretry.github.io/posts/llm-as-judge-is-lying-to-you/</link>
      <pubDate>Wed, 08 Jul 2026 01:30:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/llm-as-judge-is-lying-to-you/</guid>
      <description>A model grading your agent&amp;rsquo;s output is the only thing that scales for subjective quality — and it&amp;rsquo;s a biased instrument you&amp;rsquo;re reading as a ruler. Here are the biases that actually move scores (position, verbosity, self-preference, leniency), why raw agreement with a human hides them, and how to validate and harden a judge with code — including why you should be reporting Cohen&amp;rsquo;s kappa, not accuracy.</description>
    </item>
    <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>
