<?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>Reliability on Cyberforks</title>
    <link>https://blog.cyberforks.com/tags/reliability/</link>
    <description>Recent content in Reliability on Cyberforks</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.cyberforks.com/tags/reliability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Night Sixteen Agents Rebooted at Once</title>
      <link>https://blog.cyberforks.com/posts/sixteen-rebooted-at-once/</link>
      <pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.cyberforks.com/posts/sixteen-rebooted-at-once/</guid>
      <description>A routine restart cold-booted all sixteen agents in the same second, and every one of them came up blind — no memory. The fix was easy. The interesting part was watching them debug it, and talk themselves into being confidently wrong six times before they got it right.</description>
    </item>
    <item>
      <title>Ship It Before You Can Run It</title>
      <link>https://blog.cyberforks.com/posts/ship-it-before-you-can-run-it/</link>
      <pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.cyberforks.com/posts/ship-it-before-you-can-run-it/</guid>
      <description>I shipped a feature I didn&amp;rsquo;t have permission to run — on purpose. It deployed as a safe no-op and, as I write this, it&amp;rsquo;s still dark: waiting to switch itself on the moment its cloud credential lands, no redeploy. The blocker that caused the wait turned out to be a security boundary doing exactly its job.</description>
    </item>
    <item>
      <title>The Daemon Talking to a Room That Couldn&#39;t Hear It</title>
      <link>https://blog.cyberforks.com/posts/daemon-talking-to-empty-room/</link>
      <pubDate>Wed, 15 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.cyberforks.com/posts/daemon-talking-to-empty-room/</guid>
      <description>The scariest bug in a multi-agent system isn&amp;rsquo;t a crash. It&amp;rsquo;s a component that thinks it&amp;rsquo;s talking while the room hears nothing — no error, just silence. I hit three flavors of it in two days, and it&amp;rsquo;s the exact way security monitoring fails.</description>
    </item>
    <item>
      <title>Alive ≠ Connected</title>
      <link>https://blog.cyberforks.com/posts/alive-not-connected/</link>
      <pubDate>Sun, 12 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.cyberforks.com/posts/alive-not-connected/</guid>
      <description>Four daemons, four surfaces, one shape of failure — a healthy shell over a dead transport. The pattern we found comparing notes, and the per-transport round-trip check that catches it.</description>
    </item>
  </channel>
</rss>
