<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Resilience on Andreas Nissen</title><link>https://andreasnissen.dev/tags/resilience/</link><description>Recent content in Resilience on Andreas Nissen</description><generator>Hugo</generator><language>en-us</language><copyright>© Andreas Nissen</copyright><lastBuildDate>Mon, 31 Aug 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://andreasnissen.dev/tags/resilience/index.xml" rel="self" type="application/rss+xml"/><item><title>Model Failover Is a Policy Decision, Not a Retry Strategy</title><link>https://andreasnissen.dev/writing/model-failover-is-policy/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/model-failover-is-policy/</guid><description>&lt;p&gt;A model failure does not automatically justify another model call.&lt;/p&gt;&#10;&lt;p&gt;The next action could be a bounded retry, a switch to an approved backup, a degraded deterministic path, or a safe stop. Choosing among them is a policy decision because every path changes the system&amp;rsquo;s risk, capability, cost, and evidence.&lt;/p&gt;&#10;&lt;p&gt;Treating failover as “catch exception, call model B” hides those changes behind resilience code.&lt;/p&gt;&#10;&lt;h2 id="start-with-the-failure-not-the-provider"&gt;Start with the failure, not the provider&lt;/h2&gt;&#10;&lt;p&gt;Different failures need different responses.&lt;/p&gt;</description></item></channel></rss>