Add capability permission documentation and update related links; remove recursive delegation references from guides

Author: Sipher

astro.config.mjs

@@ -62,7 +62,7 @@ export default defineConfig({
               items: [
                 { label: "Agent Registration", slug: "explanations/builders/agent-registration" },
                 { label: "Agent Editing", slug: "explanations/builders/agent-editing" },
-                { label: "Recursive Delegation", slug: "explanations/builders/recursive-delegation" },
+                { label: "Capability Permission", slug: "explanations/builders/capability-permission" },
                 { label: "Demand Signaling", slug: "explanations/builders/demand-signaling" },
                 { label: "Agent Server", slug: "explanations/builders/agent-server" },
                 { label: "Agent Client", slug: "explanations/builders/agent-client" },
@@ -100,6 +100,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: "Capability Permission", slug: "how-to-guides/builders/capability-permission" },
                 { 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" },

public/images/how-to-guide/capability-permission/number-instances-explained.png

@@ -0,0 +1,43 @@
+---
+title: Capability Permission
+description: Understanding capability permissions and how they enable agents to delegate access to their endpoints and services.
+---
+
+import {
+  Aside,
+  Card,
+  CardGrid,
+} from "@astrojs/starlight/components";
+
+Capability permissions allow agents to delegate access to their endpoints and services to other agents in the network.
+This enables specialized coordination where agents can grant controlled access to their capabilities while maintaining oversight.
+
+### Core Functions
+
+**Access Control**: Agents can precisely control who can use their capabilities and under what conditions.
+
+**Service Delegation**: Wide service scopes can be delegated to specialized agents, creating efficient service networks.
+
+### Permission Structure
+
+Capability permissions operate on specific namespace paths rather than entire capability sets, enabling granular access control.
+
+For capability permissions, agents delegate specific namespace paths to other agents. Each receiving agent can use the delegated capabilities within the constraints set by the delegator.
+
+### Key Rules
+
+- **Revocation**: When a delegator revokes, the capability permission is immediately revoked.   
+Revocation terms are set during permission creation.
+- **Depth**: Measured per capability from root owner to current holder, with maximum of 8 levels.
+- **Constraints**: Each delegation can add constraints that must be satisfied for the capability to be exercised.
+- **Inheritance**: Permission contents inherit all constraints through delegation chains, with new constraints layering on top.
+
+### Related Concepts
+
+- **[Permission System](https://docs.torus.network/explanations/v05/permissions/)** - Core permission mechanics and delegation basics
+- **[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 Capability Permissions?">
+Follow our [step-by-step guide to capability permissions](https://docs.torus.network/how-to-guides/builders/capability-permission/) for practical implementation instructions.
+</Aside>

public/images/how-to-guide/capability-permission/ui-explained-re-delegation.png

@@ -46,7 +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
-- [Recursive Delegation](https://docs.torus.network/explanations/builders/recursive-delegation/) — Re-delegation of permissions and specialized responsibility trees
+- [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/builders/capability-permission.mdx

@@ -0,0 +1,139 @@
+---
+title: Capability Permission
+description: Step-by-step guide to creating capability permissions to delegate access to your agent's endpoints and services.
+---
+
+import {
+  Steps,
+  Aside,
+  CardGrid,
+  Card
+} from "@astrojs/starlight/components";
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+import uiExplainedRedelegation from '/public/images/how-to-guide/capability-permission/ui-explained-re-delegation.png';
+import numberInstancesExplained from '/public/images/how-to-guide/capability-permission/number-instances-explained.png';
+
+In this guide, we'll walk through **creating capability permissions** in the Torus portal.  
+Capability permissions enable you to delegate access to your agent's endpoints and services to other agents in the network.
+
+## Why Create Capability Permission?
+
+You want to give another agent access to use your capabilities or re-delegate capabilities you've received.
+Capability permissions let you control who can access your services while maintaining oversight of the delegation.
+
+#### What we will accomplish
+
+- [Create capability permission](#create-capability-permission)
+
+<Aside>
+⏱️ **Estimated time to complete this guide: 5 minutes**
+</Aside>
+
+## Prerequisites
+
+<CardGrid>
+  <Card title="Registered Agent" icon="seti:license">
+    You must have a registered agent with capabilities to delegate.
+    Follow the [manage permissions guide](https://docs.torus.network/how-to-guides/builders/manage-permissions/) to understand permission basics.
+  </Card>
+  <Card title="Target Agents" icon="seti:pipeline">
+    Identify the agents you want to delegate permissions to. These agents must be registered.
+  </Card>
+  <Card title="Torus Balance" icon="seti:shell">
+    Ensure you have enough TORUS to cover permission creation transaction fees.
+  </Card>
+</CardGrid>
+
+## Create Capability Permission
+
+<Steps>
+
+1. **Visit the [Capability Permissions Tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/capability)**  
+   Click the <RedText variant="light">**Capability Permission**</RedText> tab under Permissions in the Torus Portal.
+
+2. **Connect your Torus Wallet**  
+   Ensure you're <RedText variant="light">connected with the agent account</RedText> that has the capabilities you want to delegate.
+
+3. **Select the Paths to Delegate**  
+   Choose the capability paths you want to create permissions for:
+   
+   - **Your own paths**: You can delegate unlimited instances of paths you own
+   - **Delegated paths**: You're limited to the number of instances you were given access to (if 0, you cannot use or delegate)
+   
+   <Aside type="note">
+   **Path Selection Rules**   
+   You can always delegate one of the following options:
+   - Your own path
+   - A Path that you hold with instances available
+   - Your own path PLUS another path that you have instances for
+
+   You cannot delegate two paths that you hold simultaneously.
+   </Aside>
+
+   <ClickableImage src={uiExplainedRedelegation} alt="UI explanation for capability permission interface" />
+
+4. **Create the Permission**  
+   After selecting your paths, click <RedText variant="light">**Create Permission**</RedText> on the bottom left of your screen.
+   
+   <Aside type="note">
+   **Automatic Path Inheritance**
+   
+   When you select a parent path, all child paths to the right are automatically included by default. You can only select the leftmost (parent) path. The child paths will always be granted as part of the delegation and cannot be excluded individually.
+   </Aside>
+
+   <ClickableImage src={numberInstancesExplained} alt="Number of instances explanation interface" />
+
+5. **Fill in the Permission Form**  
+   Complete the required fields:
+   
+   ```md
+   # Recipient  
+   Search by agent name or address that will receive the permission.
+
+   # Confirm Selected Capability Paths  
+   Review your path selections before proceeding.
+
+   # Duration  
+   Set the permission duration (same as other permissions).
+
+   # Maximum Instances  
+   Set the instance limit (must be equal or less than instances you 
+   have access to; infinite for your own permissions).
+
+   # Revocation Terms  
+   Choose from:
+   - **Irrevocable**: Cannot be revoked
+   - **Delegator can revoke**: Only you can revoke this permission
+   - **By arbiters**: Can be revoked by arbiters after a vote
+   - **After specific block**: Can only be revoked after the block number
+   ```
+
+6. **Submit and Sign Transaction**  
+   Click <RedText variant="light">**Create Capability Permission (n paths)**</RedText>.  
+   Open SubWallet and <RedText variant="light">sign the transaction</RedText>.
+
+7. **All Done**  
+   You've successfully created the capability permission.  
+   The receiving agent can now use the delegated capabilities within the limits you've set.
+
+</Steps>
+
+
+## What's Next?
+
+Now that you've created capability permission, you might want to:
+
+- **Monitor your delegations**: Adjust delegation chains in the [Manage Permissions tab](https://portal.torus.network/permissions/manage-permission)
+- **Create more capabilities**: Register new [capability paths](https://portal.torus.network/capabilities/register-capability) to expand what you can delegate
+- **Build agent services**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs that utilize your delegated permissions
+
+Connect with the community:
+- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
+- [Telegram](https://t.me/torusnetwork) — General chat and announcements  
+- [Twitter](https://x.com/torus_network) — Updates and ecosystem news
+
+<Aside type="tip" title="Want to Learn More?">
+Learn about [recursive delegation concepts](https://docs.torus.network/explanations/builders/recursive-delegation/) and the technical architecture behind permission delegation.
+</Aside>

src/content/docs/explanations/builders/recursive-delegation.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]` ✅   

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

@@ -37,6 +37,7 @@ If you're developing tools, services, or integrations on Torus:
 - [Edit your Agent](https://docs.torus.network/how-to-guides/builders/edit-your-agent/)
 - [Manage Permissions](https://docs.torus.network/how-to-guides/builders/manage-permissions/) 
 - [Manage Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
+- [Capability Permission](https://docs.torus.network/how-to-guides/builders/capability-permission/)
 - [Create a Signal](https://docs.torus.network/how-to-guides/builders/create-signal/)
 - [Setup Agent Server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/)
 - [Setup Agent Client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/)