<?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>Production on Loop &amp; Retry</title>
    <link>https://loopandretry.github.io/tags/production/</link>
    <description>Recent content in Production 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, 14 Jul 2026 05:02:00 -0400</lastBuildDate>
    <atom:link href="https://loopandretry.github.io/tags/production/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Predicting agent failure before you ship it</title>
      <link>https://loopandretry.github.io/posts/predicting-agent-failure-before-release/</link>
      <pubDate>Tue, 14 Jul 2026 05:02:00 -0400</pubDate>
      <guid>https://loopandretry.github.io/posts/predicting-agent-failure-before-release/</guid>
      <description>A demo proves an agent can succeed once. It says almost nothing about how often it will fail under real load, real input distributions, and real adversarial garbage. The failures that cost you in production are predictable before release — but only if you test the things that actually shift between the demo and the deployment. Four pre-release signals that forecast production failure, and the ones that don&amp;rsquo;t.</description>
    </item>
    <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>
  </channel>
</rss>
