<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Self-Healing on Truth-First Beacon — Paul Desai</title><link>https://beacon.activemirror.ai/tags/self-healing/</link><description>Recent content in Self-Healing on Truth-First Beacon — Paul Desai</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 14 Feb 2026 13:00:00 +0530</lastBuildDate><atom:link href="https://beacon.activemirror.ai/tags/self-healing/feed.xml" rel="self" type="application/rss+xml"/><item><title>Systems That Heal Themselves</title><link>https://beacon.activemirror.ai/reflections/systems-that-heal-themselves/</link><pubDate>Sat, 14 Feb 2026 13:00:00 +0530</pubDate><guid>https://beacon.activemirror.ai/reflections/systems-that-heal-themselves/</guid><description>&lt;p&gt;Monitoring tells you something broke. Self-healing fixes it before you notice.&lt;/p&gt;
&lt;p&gt;I got tired of waking up to dead services. Not catastrophic failures — the annoying kind. Ollama OOM&amp;rsquo;d at 3am and didn&amp;rsquo;t restart. A LaunchAgent lost its environment variable after a macOS update. A log file grew to 2GB because something was chatty. Small things that compound into a morning spent debugging instead of building.&lt;/p&gt;
&lt;p&gt;So I built a system that checks everything every five minutes and fixes what it can.&lt;/p&gt;</description></item></channel></rss>