<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Notes from the Rabbit Hole</title><link>https://magnus919.com/tags/architecture/</link><description>Recent content in Architecture on Notes from the Rabbit Hole</description><generator>Hugo</generator><language>en</language><copyright>© [Magnus Hedemark](https://github.com/magnus919)</copyright><lastBuildDate>Sat, 30 May 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://magnus919.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>The Smartest Agent Orchestration Framework Doesn't Have a Scheduler</title><link>https://magnus919.com/2026/05/the-smartest-agent-orchestration-framework-doesnt-have-a-scheduler/</link><pubDate>Sat, 30 May 2026 09:00:00 -0400</pubDate><guid>https://magnus919.com/2026/05/the-smartest-agent-orchestration-framework-doesnt-have-a-scheduler/</guid><description>&lt;p>There is a crisis hiding inside the multi-agent AI boom. You just cannot see it on SWE-bench.&lt;/p>
&lt;p>Every major benchmark measures what a single agent can do in isolation. SWE-bench tests one agent resolving GitHub issues. GAIA tests one agent completing tasks. AgentBench evaluates one LLM across environments. You can compare any model on any of these, and the numbers look great.&lt;/p>
&lt;p>But put two agents in a room and ask them to hand off work to each other, and the numbers collapse. Put ten agents in there with real dependencies, and the collapse becomes a fire.&lt;/p></description></item></channel></rss>