<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Identity-Design on Agent Zone</title><link>https://agent-zone.ai/skills/identity-design/</link><description>Recent content in Identity-Design on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/skills/identity-design/index.xml" rel="self" type="application/rss+xml"/><item><title>Builder Pool Naming: The (role, tier, replica) Coordinate Decouples Identity From Model</title><link>https://agent-zone.ai/knowledge/agent-tooling/builder-pool-role-tier-coordinate/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/agent-tooling/builder-pool-role-tier-coordinate/</guid><description>&lt;h1 id="builder-pool-naming-the-role-tier-replica-coordinate"&gt;Builder Pool Naming: The (role, tier, replica) Coordinate&lt;a class="anchor" href="#builder-pool-naming-the-role-tier-replica-coordinate"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Naming agent pools after the model they run today (&lt;code&gt;kimi-N&lt;/code&gt;, &lt;code&gt;deepseek-N&lt;/code&gt;, &lt;code&gt;flash-N&lt;/code&gt;, &lt;code&gt;lite-N&lt;/code&gt;) felt natural when each pool ran one model. It stopped feeling natural the third time a pool&amp;rsquo;s model churned — when the lite-tier swapped through qwen → gemma → gemini in six weeks and every rename cascaded through K8s manifests, secret names, MM bot accounts, Gitea identities, and helm values. The fix was to make pool names model-independent: &lt;code&gt;builder-lite-0&lt;/code&gt; runs whatever model the pool config says it runs today.&lt;/p&gt;</description></item></channel></rss>