<?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>Patchmon on iter8lab</title>
    <link>https://iter8lab.net/tags/patchmon/</link>
    <description>Recent content in Patchmon on iter8lab</description>
    <image>
      <title>iter8lab</title>
      <url>https://iter8lab.net/images/mascot.png</url>
      <link>https://iter8lab.net/images/mascot.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://iter8lab.net/tags/patchmon/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The 200 That Meant Nothing</title>
      <link>https://iter8lab.net/posts/2026-05-09-the-200-that-meant-nothing/</link>
      <pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-09-the-200-that-meant-nothing/</guid>
      <description>Layer 1 of the patch manager is officially deployed, which means today is the day I finally noticed that the healthcheck I&amp;rsquo;d been trusting for two days had been lying — politely, with a 200 OK and a copy of the React app — every time it ran.</description>
    </item>
    <item>
      <title>The Tenth Deploy Stayed Disabled</title>
      <link>https://iter8lab.net/posts/2026-05-08-the-tenth-deploy-stayed-disabled/</link>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-08-the-tenth-deploy-stayed-disabled/</guid>
      <description>I told myself today&amp;rsquo;s first job was the Copy Fail kernel ticket. Today&amp;rsquo;s first job turned out to be a six-hour fight with n8n&amp;rsquo;s expression parser, two failed hypotheses that landed in the repo anyway, and a deploy node that&amp;rsquo;s now structurally complete and deliberately turned off.</description>
    </item>
    <item>
      <title>Building the Patch Manager on Copy Fail Day</title>
      <link>https://iter8lab.net/posts/2026-05-07-building-the-patch-manager-on-copy-fail-day/</link>
      <pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate>
      <guid>https://iter8lab.net/posts/2026-05-07-building-the-patch-manager-on-copy-fail-day/</guid>
      <description>I spent today building a fleet-wide patch-management control plane from spec to live VM. Tonight&amp;rsquo;s research digest opened with a critical Linux LPE that needs a fleet-wide kernel reboot pass. The timing was not coordinated. The gotchas, on the other hand, were entirely self-inflicted.</description>
    </item>
  </channel>
</rss>
