<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Francesco Colamonici — Blog</title>
    <link>https://francescocolamonici.it/en/blog/</link>
    <description>Software architecture, system design and governance: decisions, boundaries, data.</description>
    <language>en</language>
    <lastBuildDate>Tue, 18 Aug 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://francescocolamonici.it/rss-en.xml" rel="self" type="application/rss+xml"/>
    <item>
      <title>The Number of Agents Is a Cost, Not a Capability</title>
      <link>https://francescocolamonici.it/en/blog/the-number-of-agents-is-a-cost-not-a-capability</link>
      <guid isPermaLink="true">https://francescocolamonici.it/en/blog/the-number-of-agents-is-a-cost-not-a-capability</guid>
      <pubDate>Tue, 18 Aug 2026 00:00:00 GMT</pubDate>
      <description>The pitch for multi-agent AI is that more agents mean a more powerful system. I paid that bill once — a nine-year experiment in splitting a platform across twelve separately-owned teams — and here is what it taught me about why the agent count is a cost you pay, not a capability you gain.</description>
      <category>multi-agent-systems</category>
      <category>ai-orchestration</category>
      <category>agentic-ai</category>
      <category>context-engineering</category>
      <category>distributed-systems</category>
      <category>system-design</category>
    </item>
    <item>
      <title>A Boundary You Don't Enforce Is Just a Wish</title>
      <link>https://francescocolamonici.it/en/blog/a-boundary-you-dont-enforce-is-just-a-wish</link>
      <guid isPermaLink="true">https://francescocolamonici.it/en/blog/a-boundary-you-dont-enforce-is-just-a-wish</guid>
      <pubDate>Tue, 11 Aug 2026 00:00:00 GMT</pubDate>
      <description>I opened my own repo and found that the rule meant to police my architecture enforced nothing. Here is how I turned it into a fitness function that fails the build when any code — human or AI — crosses a line it shouldn't.</description>
      <category>architecture-fitness-functions</category>
      <category>module-boundaries</category>
      <category>evolutionary-architecture</category>
      <category>ai-assisted-development</category>
      <category>system-design</category>
    </item>
    <item>
      <title>Decisions You Don't Write Down Become Debt</title>
      <link>https://francescocolamonici.it/en/blog/decisions-you-dont-write-down-become-debt</link>
      <guid isPermaLink="true">https://francescocolamonici.it/en/blog/decisions-you-dont-write-down-become-debt</guid>
      <pubDate>Tue, 04 Aug 2026 00:00:00 GMT</pubDate>
      <description>In 2016, on my first architecture assignment, a mentor told me documentation was a deliverable as important as the code. Here is why the architectural decisions you don't write down always come back as debt.</description>
      <category>software-architecture</category>
      <category>decision-records</category>
      <category>technical-debt</category>
      <category>system-design</category>
    </item>
  </channel>
</rss>