<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Agent Routing on AIBussin — AI applications, systems and books</title><link>https://aibussin.com/tags/agent-routing/</link><description>Recent content in Agent Routing on AIBussin — AI applications, systems and books</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sat, 08 Aug 2026 23:41:00 +0100</lastBuildDate><atom:link href="https://aibussin.com/tags/agent-routing/index.xml" rel="self" type="application/rss+xml"/><item><title>Capabilities and Routing</title><link>https://aibussin.com/books/agents-from-first-principles/07-chapter/</link><pubDate>Sat, 08 Aug 2026 17:09:00 +0100</pubDate><guid>https://aibussin.com/books/agents-from-first-principles/07-chapter/</guid><description>&lt;p&gt;Every mechanism built so far has taken the action set as given. The action boundary validates a proposal against a fixed list of permitted action types. Candidate generation samples several proposals from the same list. The runtime-state chapter watches what happens after execution and decides whether to continue. All of them assume that somebody, somewhere, already decided which capabilities the policy could choose from.&lt;/p&gt;&#10;&lt;p&gt;So far we have treated that decision as an input. This chapter makes it explicit, because the capability surface changes the decision problem the policy has to solve and therefore belongs inside the agent architecture itself.&lt;/p&gt;</description></item><item><title>Advanced Agents From First Principles 05: Is One Model Doing Everything? Build a Mixture of Experts at the Agent Level</title><link>https://aibussin.com/books/advanced-agents-from-first-principles/05-chapter/</link><pubDate>Sat, 08 Aug 2026 23:41:00 +0100</pubDate><guid>https://aibussin.com/books/advanced-agents-from-first-principles/05-chapter/</guid><description>&lt;p&gt;A common agent architecture starts simply:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;request&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;model&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;action&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;That simplicity is valuable.&lt;/p&gt;&#10;&lt;p&gt;It should be your default.&lt;/p&gt;&#10;&lt;p&gt;But eventually you may notice something strange.&lt;/p&gt;&#10;&lt;p&gt;The same model is being asked to do everything:&lt;/p&gt;&#10;&lt;ul&gt;&#10;&lt;li&gt;classify the task,&lt;/li&gt;&#10;&lt;li&gt;search documentation,&lt;/li&gt;&#10;&lt;li&gt;reason about code,&lt;/li&gt;&#10;&lt;li&gt;write SQL,&lt;/li&gt;&#10;&lt;li&gt;review a patch,&lt;/li&gt;&#10;&lt;li&gt;summarize logs,&lt;/li&gt;&#10;&lt;li&gt;judge another model,&lt;/li&gt;&#10;&lt;li&gt;decide whether a deployment is safe,&lt;/li&gt;&#10;&lt;li&gt;and answer simple questions that did not require an expensive model in the first place.&lt;/li&gt;&#10;&lt;/ul&gt;&#10;&lt;p&gt;At that point the problem may no longer be:&lt;/p&gt;</description></item><item><title>Agents From First Principles 06: AI Agent Chooses the Wrong Tool? Design Better Tool Interfaces, Schemas and Routing</title><link>https://aibussin.com/post/agents-from-first-principles-06/</link><pubDate>Sat, 08 Aug 2026 17:09:00 +0100</pubDate><guid>https://aibussin.com/post/agents-from-first-principles-06/</guid><description>&lt;p&gt;An agent can have a perfectly capable model and still behave badly because its tools are badly designed.&lt;/p&gt;&#10;&lt;p&gt;This is one of the most common agent failures in production:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;user goal&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;agent&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;wrong tool&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt; ↓&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;wrong action&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;The model may understand the task.&lt;/p&gt;&#10;&lt;p&gt;The agent may have enough context.&lt;/p&gt;&#10;&lt;p&gt;The problem is that the action space is ambiguous.&lt;/p&gt;&#10;&lt;p&gt;If two tools overlap, their descriptions are vague, their schemas are huge, or their results are difficult to interpret, the model has to guess.&lt;/p&gt;</description></item></channel></rss>