<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="/feed.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Notes from the AI Operating Layer</title>
    <link>https://lenaschaefer.me/writing/</link>
    <atom:link href="https://lenaschaefer.me/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Compliance, agentic operations, cross-border decisions and the financial questions behind them, by Lena Schaefer.</description>
    <language>en</language>
    <lastBuildDate>Wed, 29 Jul 2026 00:00:00 +0000</lastBuildDate>
    <item>
      <title>Why people reach for a cap on AI spend</title>
      <link>https://lenaschaefer.me/writing/why-people-cap-ai-spend</link>
      <guid isPermaLink="true">https://lenaschaefer.me/writing/why-people-cap-ai-spend</guid>
      <pubDate>Wed, 29 Jul 2026 00:00:00 +0000</pubDate>
      <description>Companies track what AI costs to serve customers. The spend from the team using AI to build the product usually disappears into a general expense line. When finance can see the number rising but can't explain why, the next move is often a spend cap.</description>
      <category>Finance and business models</category>
    </item>
    <item>
      <title>Compliance is architecture, not paperwork</title>
      <link>https://lenaschaefer.me/writing/compliance-is-architecture-not-paperwork</link>
      <guid isPermaLink="true">https://lenaschaefer.me/writing/compliance-is-architecture-not-paperwork</guid>
      <pubDate>Fri, 12 Jun 2026 00:00:00 +0000</pubDate>
      <description>The AI Act deadline moved. The work it demands clearly didn't.</description>
      <category>Compliance as architecture</category>
    </item>
  </channel>
</rss>
