<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Runtime-Governance on M.F.Borman</title><link>https://www.mfborman.nl/tags/runtime-governance/</link><description>Recent content in Runtime-Governance on M.F.Borman</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 27 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.mfborman.nl/tags/runtime-governance/feed.xml" rel="self" type="application/rss+xml"/><item><title>What loop engineering needs before it runs in a regulated estate</title><link>https://www.mfborman.nl/articles/what-loop-engineering-needs-in-a-regulated-estate/</link><pubDate>Sat, 27 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/articles/what-loop-engineering-needs-in-a-regulated-estate/</guid><description>The loop can write correct code unattended. What it can&amp;rsquo;t do is grant itself permission — and in a regulated estate that gap is a gate, not a better checker.</description></item><item><title>What breaks when governance becomes load-bearing</title><link>https://www.mfborman.nl/posts/2026-03-17-what-breaks-when-governance-becomes-load-bearing/</link><pubDate>Tue, 17 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/posts/2026-03-17-what-breaks-when-governance-becomes-load-bearing/</guid><description>Moving AI governance into the execution layer is the right structural move. What gets less attention is what breaks when you do it.</description></item><item><title>Failure modes belong in the execution layer, not in documentation</title><link>https://www.mfborman.nl/posts/2026-03-10-failure-modes-as-system-constraints/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://www.mfborman.nl/posts/2026-03-10-failure-modes-as-system-constraints/</guid><description>A documented failure mode gets reviewed. A system constraint gets enforced. The difference is whether governance scales with headcount or with the system.</description></item></channel></rss>