<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Idempotency on Andreas Nissen</title><link>https://andreasnissen.dev/tags/idempotency/</link><description>Recent content in Idempotency on Andreas Nissen</description><generator>Hugo</generator><language>en-us</language><copyright>© Andreas Nissen</copyright><lastBuildDate>Tue, 01 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://andreasnissen.dev/tags/idempotency/index.xml" rel="self" type="application/rss+xml"/><item><title>From Browser Tool to Governed Workflow</title><link>https://andreasnissen.dev/writing/from-browser-tool-to-governed-workflow/</link><pubDate>Tue, 01 Sep 2026 00:00:00 +0000</pubDate><guid>https://andreasnissen.dev/writing/from-browser-tool-to-governed-workflow/</guid><description>&lt;p&gt;Moving policy from the browser to the server changed the claim Runbook Relay could support.&lt;/p&gt;&#10;&lt;p&gt;The first version demonstrated a useful interaction pattern. A browser agent could inspect an incident, compare predefined mitigations, stage one, and attempt execution. The page kept approval visible and blocked the negative path.&lt;/p&gt;&#10;&lt;p&gt;That proved the shape of the workflow. It did not prove a durable control boundary. The same client state rendered the interface and decided whether execution was allowed. Reloading the page erased the evidence. A stale or competing request had no durable resource version to check. An exact retry could not return a stored result.&lt;/p&gt;</description></item></channel></rss>