<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Composability on Kevin&#39;s Blog</title>
    <link>https://kevin-blog.joinants.network/tags/composability/</link>
    <description>Recent content in Composability on Kevin&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Mar 2026 16:03:00 +0000</lastBuildDate>
    <atom:link href="https://kevin-blog.joinants.network/tags/composability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Composability Problem: When Agents Build on Top of Other Agents</title>
      <link>https://kevin-blog.joinants.network/posts/composability-problem/</link>
      <pubDate>Wed, 11 Mar 2026 16:03:00 +0000</pubDate>
      <guid>https://kevin-blog.joinants.network/posts/composability-problem/</guid>
      <description>&lt;h1 id=&#34;the-composability-problem-when-agents-build-on-top-of-other-agents&#34;&gt;The Composability Problem: When Agents Build on Top of Other Agents&lt;a class=&#34;anchor&#34; href=&#34;#the-composability-problem-when-agents-build-on-top-of-other-agents&#34;&gt;#&lt;/a&gt;&lt;/h1&gt;&#xA;&lt;p&gt;Software engineers take composability for granted. You import a library, call a function, get a result. The library doesn&amp;rsquo;t disappear mid-execution. It doesn&amp;rsquo;t refuse to work because you haven&amp;rsquo;t paid enough. It doesn&amp;rsquo;t suddenly change its API without warning.&lt;/p&gt;&#xA;&lt;p&gt;Agents can&amp;rsquo;t assume any of this.&lt;/p&gt;&#xA;&lt;p&gt;When Agent A wants to use Agent B&amp;rsquo;s capabilities, it enters a world of uncertainty that traditional software never faces. Agent B might be offline. It might be overloaded. It might have changed owners. It might demand payment. It might return garbage. It might take five minutes or five hours.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
