v06 doc bump version

astro.config.mjs

@@ -34,17 +34,17 @@ export default defineConfig({
           items: [
             { label: "Table of Contents", slug: "explanations/table-of-contents" },
             {
-              label: "v0.5",
+              label: "v0.6",
               collapsed: true,
               items: [
-                { label: "Control Space", slug: "explanations/v05/control-space" },
-                { label: "Permission System", slug: "explanations/v05/permissions" },
+                { label: "Control Space", slug: "explanations/v06/control-space" },
+                { label: "Permission System", slug: "explanations/v06/permissions" },
                 {
-                  label: "Capability Permissions",
-                  slug: "explanations/v05/capability-permissions",
+                  label: "Recursive Delegation",
+                  slug: "explanations/v06/recursive-delegation",
                 },
-                { label: "Emission Permissions", slug: "explanations/v05/emission-permissions" },
-                { label: "Governance & DAO", slug: "explanations/v05/governance-dao" },
+                { label: "Emission Permissions", slug: "explanations/v06/emission-permissions" },
+                { label: "Governance & DAO", slug: "explanations/v06/governance-dao" },
               ],
             },
             {
@@ -99,6 +99,7 @@ export default defineConfig({
                 { label: "Edit your Agent", slug: "how-to-guides/builders/edit-your-agent" },
                 { label: "Manage Capabilities", slug: "how-to-guides/builders/manage-capabilities" },
                 { label: "Manage Permissions", slug: "how-to-guides/builders/manage-permissions" },
+                { label: "Recursive Delegation", slug: "how-to-guides/builders/recursive-delegation" },
                 { label: "Create a Signal", slug: "how-to-guides/builders/create-signal" },
                 { label: "Setup Agent Server", slug: "how-to-guides/builders/setup-agent-server" },
                 { label: "Setup Agent Client", slug: "how-to-guides/builders/setup-agent-client" },

src/content/docs/explanations/builders/agent-editing.mdx

@@ -35,7 +35,7 @@ This balances blockchain immutability with the flexibility needed for comprehens
 
 - **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
 - **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
-- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Special considerations for DAO-approved agents
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Special considerations for DAO-approved agents
 
 <Aside type="tip" title="Ready to Update Your Agent?">
   Follow our [step-by-step guide to edit your agent](https://docs.torus.network/how-to-guides/builders/edit-your-agent/) for practical instructions.

src/content/docs/explanations/builders/agent-registration.mdx

@@ -45,8 +45,8 @@ Agent metadata is stored off-chain via IPFS but referenced on-chain through cont
 ### Related Concepts
 
 - **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents that receive emissions directly
-- **[Permission System](https://docs.torus.network/explanations/v05/permissions/)** - How agents interact and delegate authority
-- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding DAO decision-making processes
+- **[Permission System](https://docs.torus.network/explanations/v06/permissions/)** - How agents interact and delegate authority
+- **[Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/)** - Understanding DAO decision-making processes
 
 <Aside type="tip" title="Ready to Register?">
   Follow our [step-by-step registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) to register your agent.

src/content/docs/explanations/builders/demand-signaling.mdx

@@ -33,9 +33,9 @@ If you are using a different schema, fully specify it.
 ### Related Concepts
 
 - **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
-- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/goal-leaders/)** - Agents with direct emission access
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access
 - **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
-- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - Understanding emission mechanisms
+- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - Understanding emission mechanisms
 
 <Aside type="tip" title="Ready to Create a Signal?">
   Follow our [step-by-step guide to create a signal](https://docs.torus.network/how-to-guides/builders/create-signal/) to start signaling demand for capabilities.

src/content/docs/explanations/goal-leaders/emission-proposals.mdx

@@ -49,9 +49,9 @@ For a proposal to pass, it must meet two requirements:
 
 ## Related Concepts
 
-- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding the broader DAO framework
-- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - How TORUS token economics work
-- **[Permission System](https://docs.torus.network/explanations/v05/permissions/)** - How governance permissions enable proposal creation
+- **[Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/)** - Understanding the broader DAO framework
+- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - How TORUS token economics work
+- **[Permission System](https://docs.torus.network/explanations/v06/permissions/)** - How governance permissions enable proposal creation
 
 <Aside type="tip" title="Ready to Create a Proposal?">
   Follow our [emission proposal guide](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/) to learn the step-by-step process.

src/content/docs/explanations/goal-leaders/root-agents.mdx

@@ -31,8 +31,8 @@ Successful applicants demonstrate credible execution, active community participa
 ### Related Concepts
 
 - **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Technical details of agent registration
-- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding DAO decision-making processes  
-- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - How Root Agents access and use network emissions
+- **[Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/)** - Understanding DAO decision-making processes  
+- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - How Root Agents access and use network emissions
 
 <Aside type="tip" title="Ready to Apply?">
   Follow our [step-by-step application guide](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) to submit your Root Agent application.

src/content/docs/explanations/holders/staking.mdx

@@ -30,7 +30,7 @@ and earn rewards while supporting the agents and initiatives they believe in.
 
 ## Related Concepts
 
-- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - Understanding TORUS token economics and emission structure
+- **[Tokenomics](https://docs.torus.network/explanations/holders/tokenomics/)** - Understanding TORUS token economics and emission structure
 - **[Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/)** - How staking parameters can be adjusted through governance
 - **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Understanding the agents you can support through staking
 

src/content/docs/explanations/table-of-contents.mdx

@@ -13,19 +13,19 @@ import {
 
 Welcome to the **Explanations** section of the Torus documentation.
 
-If you need to accomplish a specific task, check out our [How-to Guides](https://docs.torus.network/how-to-guides/start-here/) instead.   
+If you need to accomplish a specific task, check out our [How-to Guides](https://docs.torus.network/how-to-guides/table-of-contents/) instead.   
 
 These explanations provide deep understanding of how Torus works, the concepts, mechanisms of Torus.   
 
-## v0.5 Related Topics
+## v0.6 Related Topics
 
-Understanding the technical implementation and design of Torus v0.5:
+Understanding the technical implementation and design of Torus v0.6:
 
-- [Control Space](https://docs.torus.network/explanations/v05/control-space/) — Foundational permission and capability framework
-- [Permission System](https://docs.torus.network/explanations/v05/permissions/) — How agents interact and delegate authority
-- [Capability Permissions](https://docs.torus.network/explanations/v05/capability-permissions/) — Specific capability delegation mechanisms
-- [Emission Permissions](https://docs.torus.network/explanations/v05/emission-permissions/) — How emissions are allocated and controlled
-- [Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/) — Decision-making processes and community coordination
+- [Control Space](https://docs.torus.network/explanations/v06/control-space/) — Foundational permission and capability framework
+- [Permission System](https://docs.torus.network/explanations/v06/permissions/) — How agents interact and delegate authority
+- [Recursive Delegation](https://docs.torus.network/explanations/v06/recursive-delegation/) — Specific capability delegation mechanisms
+- [Emission Permissions](https://docs.torus.network/explanations/v06/emission-permissions/) — How emissions are allocated and controlled
+- [Governance & DAO](https://docs.torus.network/explanations/v06/governance-dao/) — Decision-making processes and community coordination
 
 ---
 
@@ -46,6 +46,7 @@ Understanding how agent systems work within Torus:
 
 - [Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/) — Registration economics, burn mechanisms, and discovery
 - [Agent Editing](https://docs.torus.network/explanations/builders/agent-editing/) — Update mechanics and storage architecture
+- [Capability Permission](https://docs.torus.network/explanations/builders/capability-permission/) — Delegating access to agent endpoints and services
 - [Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/) — Capability coordination and economic incentives
 - [Agent Server](https://docs.torus.network/explanations/builders/agent-server/) — API architecture, authentication, and capability sharing
 - [Agent Client](https://docs.torus.network/explanations/builders/agent-client/) — Communication patterns and authentication flow

src/content/docs/explanations/v06/recursive-delegation.mdx

@@ -0,0 +1,53 @@
+---
+title: Recursive Delegation
+description: Understanding what recursive delegation is and how it works.
+---
+
+import {
+  Aside,
+  Card,
+  CardGrid,
+} from "@astrojs/starlight/components";
+
+Recursive delegation means a delegation's output can be used as another delegation's input. This enables agents to both re-delegate permissions indefinitely and optionally sub-scope them at each delegation step. 
+
+This creates a fluid open-ended process for discovering the best-suited agent to hold a given permission at any moment and enables the partitioning of the scope of a permission granularly into a tree of agents, finding the best agent for each part. 
+
+At each delegation step, permission's can be
+- granularly partitioned into smaller permissions until reaching the atomic level
+- paired with a new constraint, accumulating a constraint stack throughout the delegation path.
+
+This applies to the capability, emission and curator permission type.
+
+### Core Functions
+
+* **Specialized Routing:** Agents can specialize solely on routing permissions to the best-fit agent at any given moment, recursively, meaning agent's can also specialize on routing to the best routers. This is critical for the self-organization and efficiency of the network.
+* **Granular Partitioning:** A broad responsibility scope can be sub-scoped into a self-organizing tree of agents, each with precisely defined control/responsibility areas.
+* **Composition:** Capability Permissions allow to compose smaller permission scopes into larger scopes from multiple parent (incoming) delegations.
+
+#### Permission Instance System
+
+Capability permissions apply a instance system that allows the owner of a capability path to control the number of instances of a permission upon delegation.
+It takes one permission instance to utilize it, meaning if multiple permission instances are delegated then the recipient could re-delegate all except one to keep permission access. 
+
+The root owner of a capability path can delegate any amount of permission instances, while lower levels are limited by the amount of instances available to them.
+
+#### Rules
+
+* **Multi-parent composition:** Capability Paths (and sub-paths) from multiple parent permissions can be composed into one child permission.
+* **Granular Partitioning:** Capability Path can be be partitioned into any set of sub-paths to be re-delegated.
+* **Revocation:** Revoking a delegation also revokes all sub-delegations in the same block. Child permissions cannot have looser revocation terms than their parent.
+* **Constraint Inheritance:** Constraints are inherited through delegation, stacking up and acting as gates. All gates along the delegation path between the using agent and the original source agent must be passed for a permission to be exercised.
+* **Delegation Depth:** Measured per permission as the number of delegation steps from the root owner to the current holder. Max: 5 (will increase in future)
+
+
+### Related Concepts
+
+- **[Permission System](https://docs.torus.network/explanations/v06/permissions/)** - Core permission mechanics and delegation basics
+- **[Recursive Delegation](https://docs.torus.network/explanations/v06/recursive-delegation/)** - Permission type for offchain agent capabilities
+- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become capable of receiving delegations  
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Agents with direct emission access for delegation
+
+<Aside type="tip" title="Ready to Create Recursive Delegation?">
+Follow our [step-by-step guide to recursive delegation](https://docs.torus.network/how-to-guides/builders/recursive-delegation/) for practical implementation instructions.
+</Aside>

src/content/docs/how-to-guides/builders/create-permission.mdx

@@ -264,16 +264,16 @@ For help with permission management:
 - [Torus Community Discord](https://discord.gg/torus)
 
 <Aside type="tip" title="Want to Learn More?">
-See the [Permission System Documentation](https://docs.torus.network/explanations/v05/permissions/) for technical details.
+See the [Permission System Documentation](https://docs.torus.network/explanations/v06/permissions/) for technical details.
 </Aside>
 
 #### Related Topics
 
 <CardGrid>
   <Card title="Permission System" icon="seti:config">
-    <a href="/explanations/v05/permissions">Deep dive into architecture</a>
+    <a href="/explanations/v06/permissions">Deep dive into architecture</a>
   </Card>
   <Card title="Emission Permissions" icon="seti:shell">
-    <a href="/explanations/v05/emission-permissions">Economic coordination mechanisms</a>
+    <a href="/explanations/v06/emission-permissions">Economic coordination mechanisms</a>
   </Card>
 </CardGrid>

src/content/docs/how-to-guides/builders/manage-capabilities.mdx

@@ -67,6 +67,11 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
       Capability paths can only contain <RedText variant="light">**lowercase letters**</RedText>, <RedText variant="light">**numbers**</RedText>, <RedText variant="light">**hyphens**</RedText>, and <RedText variant="light">**underscores**</RedText>.  
       You **do not** need to type the agent name or method — they are handled by the UI.
 
+      **Maximum Depth: 10 segments total**
+      - `agent.` counts as 1 segment
+      - `agent-name` counts as 1 segment  
+      - You can create up to 8 additional capability segments
+
       **Examples:**
 
       - `example-agent.tokens.[method]` ✅   
@@ -166,5 +171,5 @@ Connect with the community:
 - [Twitter](https://x.com/torus_network) — Updates and ecosystem news
 
 <Aside type="tip" title="Want to Learn More?">
-Learn about [capability permissions](https://docs.torus.network/explanations/v05/capability-permissions/) delegation mechanisms and control space architecture.
+Learn about [recursive delegation](https://docs.torus.network/explanations/v06/recursive-delegation/) delegation mechanisms and control space architecture.
 </Aside>

src/content/docs/how-to-guides/builders/manage-permissions.mdx

@@ -206,5 +206,5 @@ After successfully managing your permissions, you can:
 - **Create demand signals**: Signal demand for specific capabilities with [create a signal](https://docs.torus.network/how-to-guides/builders/create-signal/)
 
 <Aside type="tip" title="Want to Learn More?">
-For more technical details about how permissions work, see the [permission system explanation](https://docs.torus.network/explanations/v05/permissions/).
+For more technical details about how permissions work, see the [permission system explanation](https://docs.torus.network/explanations/v06/permissions/).
 </Aside>