<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Remediation Skills on Truth-First Beacon — Paul Desai</title><link>https://beacon.activemirror.ai/tags/remediation-skills/</link><description>Recent content in Remediation Skills on Truth-First Beacon — Paul Desai</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 02 Apr 2026 13:45:48 +0530</lastBuildDate><atom:link href="https://beacon.activemirror.ai/tags/remediation-skills/feed.xml" rel="self" type="application/rss+xml"/><item><title>Sovereign Systems Require Operational Resilience</title><link>https://beacon.activemirror.ai/reflections/sovereign-systems-require-operational-resilience/</link><pubDate>Thu, 02 Apr 2026 13:45:48 +0530</pubDate><guid>https://beacon.activemirror.ai/reflections/sovereign-systems-require-operational-resilience/</guid><description>&lt;p&gt;The model is interchangeable, but operational resilience is not - it&amp;rsquo;s the backbone of any sovereign system.&lt;/p&gt;
&lt;p&gt;I&amp;rsquo;ve spent the last year building and refining the architecture of our system, with a focus on creating a robust and resilient control plane. This has involved designing and implementing a phased approach to control plane development, with a strong emphasis on semantic readiness, dependency management, and session vs daemon scope. The goal is to create a system that can manage services, workflows, and dependencies effectively, even in the face of failures or errors.&lt;/p&gt;</description></item></channel></rss>