<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog on Jakob Bauers</title><link>https://www.jbauers.com/blog/</link><description>Recent content in Blog on Jakob Bauers</description><generator>Hugo</generator><language>en</language><atom:link href="https://www.jbauers.com/blog/index.xml" rel="self" type="application/rss+xml"/><item><title>Why this boundary</title><link>https://www.jbauers.com/blog/why-this-boundary/</link><pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.jbauers.com/blog/why-this-boundary/</guid><description>&lt;p&gt;For most of my career the interesting failures lived in infrastructure. A cache misconfigured. A credential scoped too broadly. A blast radius nobody had drawn on a whiteboard until it was already on fire. The work was rarely about the clever part; it was about the boundaries, who can reach what, under which conditions, and what happens when something goes wrong.&lt;/p&gt;
&lt;p&gt;AI agents do not change that. They remove the human pause that used to hide it. A person investigating an incident queries the rows they need. An agent investigating the same incident pulls the whole table, because nothing told it not to, and nothing in the moment slowed it down. The exposure was always there. The agent just exercises it at full speed.&lt;/p&gt;</description></item></channel></rss>