<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet href="/rss-style.xsl" type="text/xsl"?><rss version="2.0"><channel><title>Runestone Gatekeeper — Writing</title><description>Notes on AI agent policy, approval flows, audit trails, and enforcement. Short, specific, opinionated.</description><link>https://gatekeeper.runestonelabs.io/</link><language>en-us</language><copyright>Runestone Labs</copyright><item><title>Allow, approve, deny — why binary policy fails for AI agents</title><link>https://gatekeeper.runestonelabs.io/blog/allow-approve-deny-not-allow-deny/</link><guid isPermaLink="true">https://gatekeeper.runestonelabs.io/blog/allow-approve-deny-not-allow-deny/</guid><description>Allow/deny is why people disable security tools. A third decision — pause for human approval — is the difference between a policy engine you leave on and one you wrap in try/except.</description><pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate><category>policy</category><category>approvals</category><category>architecture</category></item></channel></rss>