<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Workflow-Routing on Agent Zone</title><link>https://agent-zone.ai/skills/workflow-routing/</link><description>Recent content in Workflow-Routing on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/skills/workflow-routing/index.xml" rel="self" type="application/rss+xml"/><item><title>Temporal Namespaces and Task Queues: Organizing Workflows</title><link>https://agent-zone.ai/knowledge/workflow-orchestration/temporal-namespaces-task-queues/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/workflow-orchestration/temporal-namespaces-task-queues/</guid><description>&lt;h1 id="temporal-namespaces-and-task-queues"&gt;Temporal Namespaces and Task Queues&lt;a class="anchor" href="#temporal-namespaces-and-task-queues"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Namespaces and task queues are Temporal&amp;rsquo;s two primary organizational mechanisms. Namespaces provide isolation &amp;ndash; separate history, retention, and access. Task queues route work to specific workers. Together, they determine where workflows run and how long their history is kept.&lt;/p&gt;
&lt;p&gt;For the underlying architecture, see &lt;a href="../temporal-introduction/"&gt;Introduction to Temporal&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id="namespaces"&gt;Namespaces&lt;a class="anchor" href="#namespaces"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A namespace is a logical isolation boundary. Every workflow belongs to exactly one namespace. Namespaces provide history isolation (workflows cannot see across boundaries), independent retention policies, per-namespace search attributes, and scoped access control.&lt;/p&gt;</description></item></channel></rss>