From b610a1c7096d2cdd52a6da10faac035cb2308f6f Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Thu, 28 Aug 2025 17:56:57 -0300
Subject: [PATCH 1/8] Refactor table of contents to group system-related guides
 under a new "System" section for better organization and clarity

---
 astro.config.mjs                              |  24 +-
 .../builders/agent-registration.mdx           |   2 +-
 .../goal-leaders/emission-proposals.mdx       |   2 +-
 .../emission-permissions.mdx                  |   0
 .../permission-system.mdx}                    |   0
 .../recursive-delegation.mdx                  |   5 +-
 .../docs/explanations/table-of-contents.mdx   |  13 +-
 .../builders/create-permission.mdx            | 279 ------------------
 .../builders/manage-capabilities.mdx          |   4 +-
 .../builders/manage-your-agent.mdx            |   2 +-
 .../create-capability-permission.mdx          |   4 +-
 .../create-emission-permission.mdx            |   4 +-
 .../manage-permissions.mdx                    |   4 +-
 .../docs/how-to-guides/table-of-contents.mdx  |  18 +-
 14 files changed, 55 insertions(+), 306 deletions(-)
 rename src/content/docs/explanations/{goal-leaders => system}/emission-permissions.mdx (100%)
 rename src/content/docs/explanations/{goal-leaders/permissions.mdx => system/permission-system.mdx} (100%)
 rename src/content/docs/explanations/{goal-leaders => system}/recursive-delegation.mdx (91%)
 delete mode 100644 src/content/docs/how-to-guides/builders/create-permission.mdx
 rename src/content/docs/how-to-guides/{goal-leaders => system}/create-capability-permission.mdx (96%)
 rename src/content/docs/how-to-guides/{goal-leaders => system}/create-emission-permission.mdx (98%)
 rename src/content/docs/how-to-guides/{goal-leaders => system}/manage-permissions.mdx (96%)

diff --git a/astro.config.mjs b/astro.config.mjs
index 289b818..c937b6a 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -62,12 +62,18 @@ export default defineConfig({
                 { label: "Root Agents", slug: "explanations/goal-leaders/root-agents" },
                 { label: "DAO Treasury", slug: "explanations/goal-leaders/dao-treasury" },
                 { label: "Emission Proposals", slug: "explanations/goal-leaders/emission-proposals" },
-                { label: "Permission System", slug: "explanations/goal-leaders/permissions" },
-                { label: "Recursive Delegation", slug: "explanations/goal-leaders/recursive-delegation" },
-                { label: "Emission Permissions", slug: "explanations/goal-leaders/emission-permissions" },
                 { label: "Governance & DAO", slug: "explanations/goal-leaders/governance-dao" },
               ],
             },
+            {
+              label: "System",
+              collapsed: true,
+              items: [
+                { label: "Permission System", slug: "explanations/system/permission-system" },
+                { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" },
+                { label: "Emission Permissions", slug: "explanations/system/emission-permissions" },
+              ],
+            },
             { label: "Concepts & Terminology", slug: "explanations/concepts-terminology" },
           ],
         },
@@ -104,9 +110,15 @@ export default defineConfig({
                 { label: "Become a Root Agent", slug: "how-to-guides/goal-leaders/become-a-root-agent" },
                 { label: "Request DAO Treasury Transfer", slug: "how-to-guides/goal-leaders/request-dao-treasury-transfer" },
                 { label: "Create Emission Proposal", slug: "how-to-guides/goal-leaders/create-emission-proposal" },
-                { label: "Create Capability Permission", slug: "how-to-guides/goal-leaders/create-capability-permission" },
-                { label: "Create Emission Permission", slug: "how-to-guides/goal-leaders/create-emission-permission" },
-                { label: "Manage Permissions", slug: "how-to-guides/goal-leaders/manage-permissions" },
+              ],
+            },
+            {
+              label: "System",
+              collapsed: true,
+              items: [
+                { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" },
+                { label: "Create Emission Permission", slug: "how-to-guides/system/create-emission-permission" },
+                { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" },
               ],
             },
           ],
diff --git a/src/content/docs/explanations/builders/agent-registration.mdx b/src/content/docs/explanations/builders/agent-registration.mdx
index 4025be1..d9aa5bb 100644
--- a/src/content/docs/explanations/builders/agent-registration.mdx
+++ b/src/content/docs/explanations/builders/agent-registration.mdx
@@ -45,7 +45,7 @@ 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/goal-leaders/permissions/)** - How agents interact and delegate authority
+- **[Permission System](https://docs.torus.network/explanations/system/permission-system/)** - How agents interact and delegate authority
 - **[Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Understanding DAO decision-making processes
 
 <Aside type="tip" title="Ready to Register?">
diff --git a/src/content/docs/explanations/goal-leaders/emission-proposals.mdx b/src/content/docs/explanations/goal-leaders/emission-proposals.mdx
index a8a0a2a..36ecbc7 100644
--- a/src/content/docs/explanations/goal-leaders/emission-proposals.mdx
+++ b/src/content/docs/explanations/goal-leaders/emission-proposals.mdx
@@ -51,7 +51,7 @@ For a proposal to pass, it must meet two requirements:
 
 - **[Governance & DAO](https://docs.torus.network/explanations/goal-leaders/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/goal-leaders/permissions/)** - How governance permissions enable proposal creation
+- **[Permission System](https://docs.torus.network/explanations/system/permission-system/)** - 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.
diff --git a/src/content/docs/explanations/goal-leaders/emission-permissions.mdx b/src/content/docs/explanations/system/emission-permissions.mdx
similarity index 100%
rename from src/content/docs/explanations/goal-leaders/emission-permissions.mdx
rename to src/content/docs/explanations/system/emission-permissions.mdx
diff --git a/src/content/docs/explanations/goal-leaders/permissions.mdx b/src/content/docs/explanations/system/permission-system.mdx
similarity index 100%
rename from src/content/docs/explanations/goal-leaders/permissions.mdx
rename to src/content/docs/explanations/system/permission-system.mdx
diff --git a/src/content/docs/explanations/goal-leaders/recursive-delegation.mdx b/src/content/docs/explanations/system/recursive-delegation.mdx
similarity index 91%
rename from src/content/docs/explanations/goal-leaders/recursive-delegation.mdx
rename to src/content/docs/explanations/system/recursive-delegation.mdx
index 48759f6..e0f58c3 100644
--- a/src/content/docs/explanations/goal-leaders/recursive-delegation.mdx
+++ b/src/content/docs/explanations/system/recursive-delegation.mdx
@@ -47,11 +47,10 @@ The root owner of a capability path can delegate any amount of permission instan
 
 ### Related Concepts
 
-- **[Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/)** - Core permission mechanics and delegation basics
-- **[Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/)** - Permission system architecture and delegation basics
+- **[Permission System](https://docs.torus.network/explanations/system/permission-system/)** - 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 Recursive Delegation?">
-Follow our [step-by-step guide to create capability permissions](https://docs.torus.network/how-to-guides/goal-leaders/create-capability-permission/) for practical implementation instructions.
+Follow our [step-by-step guide to create capability permissions](https://docs.torus.network/how-to-guides/system/create-capability-permission/) for practical implementation instructions.
 </Aside>
diff --git a/src/content/docs/explanations/table-of-contents.mdx b/src/content/docs/explanations/table-of-contents.mdx
index fd622bd..aae68e0 100644
--- a/src/content/docs/explanations/table-of-contents.mdx
+++ b/src/content/docs/explanations/table-of-contents.mdx
@@ -50,13 +50,20 @@ Understanding governance and leadership systems:
 - [Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/) — DAO approval process and direct emission access
 - [DAO Treasury](https://docs.torus.network/explanations/goal-leaders/dao-treasury/) — Community funding mechanisms and proposal processes
 - [Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/) — How to adjust network economics through governance
-- [Permission System](https://docs.torus.network/explanations/goal-leaders/permissions/) — How agents interact and delegate authority
-- [Recursive Delegation](https://docs.torus.network/explanations/goal-leaders/recursive-delegation/) — Specific capability delegation mechanisms
-- [Emission Permissions](https://docs.torus.network/explanations/goal-leaders/emission-permissions/) — How emissions are allocated and controlled
 - [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) — Decision-making processes and community coordination
 
 ---
 
+## System Architecture
+
+Core system components and mechanisms:
+
+- [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority
+- [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms
+- [Emission Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled
+
+---
+
 
 ## Questions Not Covered Here?
 
diff --git a/src/content/docs/how-to-guides/builders/create-permission.mdx b/src/content/docs/how-to-guides/builders/create-permission.mdx
deleted file mode 100644
index f88da35..0000000
--- a/src/content/docs/how-to-guides/builders/create-permission.mdx
+++ /dev/null
@@ -1,279 +0,0 @@
----
-title: Manage Permissions
-description: Step-by-step guide to creating, editing, and managing permissions in Torus's recursive delegation system.
----
-
-import {
-  Steps,
-  Aside,
-  CardGrid,
-  Card,
-  Tabs,
-  TabItem
-} from "@astrojs/starlight/components";
-
-In this guide, we'll walk through **creating permissions** in Torus's recursive delegation system.  
-Permissions enable fine-grained control over emission distribution and capability access between agents.
-
-#### What we will accomplish
-
-- Create capability and emission permissions
-- Configure delegation terms and constraints
-- Understand revocation and enforcement mechanisms
-
-<Aside>
-⏱️ **Estimated time to complete this guide: 15 minutes**
-</Aside>
-
-## Prerequisites
-
-<CardGrid>
-  <Card title="Registered Agent" icon="seti:license">
-    You must have a registered agent that can delegate permissions.
-  </Card>
-  <Card title="Target Recipients" icon="seti:users">
-    Know the agent addresses you want to delegate permissions to.
-  </Card>
-  <Card title="Torus Balance" icon="seti:shell">
-    Ensure sufficient TORUS for transaction fees.
-  </Card>
-</CardGrid>
-
-## Permission Types
-
-<Tabs>
-<TabItem label="Capability Permissions">
-
-**Purpose**: Grant access to specific agent endpoints or namespaces  
-**Use Cases**: API access, service delegation, resource sharing
-
-**Example**: Allow Agent B to access Agent A's memory storage API
-
-</TabItem>
-<TabItem label="Emission Permissions">
-
-**Purpose**: Delegate portions of emission streams (token flows)  
-**Use Cases**: Hiring agents, revenue sharing, economic coordination
-
-**Example**: Agent A delegates 20% of staking rewards to Agent B
-
-</TabItem>
-</Tabs>
-
-## Create a Permission
-
-<Steps>
-
-1. **Visit the [Torus Portal](https://portal.torus.network/)**  
-   Navigate to **Permissions Management** → **Create Permission**.
-
-2. **Connect your wallet**  
-   Ensure you're connected as the delegating agent.
-
-3. **Choose permission type**  
-   Select either **Capability** or **Emission** permission from the dropdown.
-
-4. **Configure permission details based on type**
-
-5. **Set revocation terms**
-
-6. **Configure enforcement** (Optional)
-
-7. **Review permission contract**
-
-8. **Submit permission**
-
-9. **Verify creation**
-
-</Steps>
-
-### Configuring Capability Permissions
-
-For capability permissions, configure these details:
-
-**Namespace Path**: Enter the specific capability path
-- Format: `agent.<agent_name>.<endpoint>.<method>`
-- Example: `agent.alice.memory.twitter.post`
-
-**Recipient**: Agent address that will receive access
-
-**Duration**: Set permission lifespan
-- **Indefinite**: Permission lasts until manually revoked
-- **Fixed Term**: Specify end date/block number
-- **Conditional**: Based on specific triggers
-
-**Constraints**: Optional usage limitations
-- Rate limits (calls per hour/day)
-- Access windows (specific times)
-- Usage quotas
-
-### Configuring Emission Permissions
-
-For emission permissions, configure these details:
-
-**Stream Selection**: Choose which emission streams to delegate
-- Staking rewards
-- Delegation fees  
-- Specific revenue streams
-
-**Allocation Type**:
-- **Percentage**: Delegate X% of selected streams
-- **Fixed Amount**: Delegate specific TORUS amount per period
-
-**Recipient**: Agent address that will receive emissions
-
-**Duration**: Set delegation period
-- Ongoing until revoked
-- Fixed term (blocks/time)
-- Performance-based triggers
-
-### Setting Revocation Terms
-
-Configure how the permission can be terminated:
-
-- **Revocable**: You can cancel anytime
-- **Irrevocable**: Cannot be cancelled (use carefully)
-- **Conditional**: Auto-revoke based on conditions
-
-### Configuring Enforcement
-
-Set third-party governance authority (Optional):
-- DAO enforcement for disputes
-- Multi-sig requirements
-- Community arbitration
-
-### Review and Submit
-
-Before submission, verify all details:
-- Delegator and recipient addresses
-- Scope and limitations
-- Duration and revocation terms
-- Associated costs
-
-## Managing Permissions
-
-### View Active Permissions
-
-Track your delegated permissions in the Torus Portal:
-- **Outgoing**: Permissions you've granted to others
-- **Incoming**: Permissions others have granted to you
-- **Status**: Active, expired, revoked permissions
-
-### Edit Permissions
-
-For permissions you've created:
-
-<Steps>
-
-1. Navigate to **Permissions Management** → **Edit Permission**
-2. Select the permission to modify
-3. Update allowed parameters (within original constraints)
-4. Submit changes on-chain
-
-</Steps>
-
-### Revoke Permissions
-
-To cancel a revocable permission:
-
-<Steps>
-
-1. Find the permission in your management dashboard
-2. Select **Revoke Permission**
-3. Confirm revocation (immediate effect)
-4. Sign transaction to execute on-chain
-
-</Steps>
-
-## Advanced Configuration
-
-### Recursive Permissions
-
-Create permission chains where recipients can further delegate:
-
-- **Enable sub-delegation**: Allow recipients to delegate portions
-- **Set depth limits**: Maximum delegation chain length
-- **Inheritance rules**: How constraints pass down the chain
-
-### Conditional Permissions
-
-Set up smart permissions that trigger based on conditions:
-
-- **Performance metrics**: Delegate based on agent performance
-- **Time-based**: Activate during specific periods
-- **Event-driven**: Trigger on blockchain events
-
-## Best Practices
-
-### Security Considerations
-
-- **Principle of least privilege**: Grant minimum necessary permissions
-- **Regular audits**: Review and clean up unused permissions
-- **Test with small amounts**: Start with small emission delegations
-
-### Economic Efficiency
-
-- **Batch operations**: Group related permissions to save gas
-- **Monitor performance**: Track ROI on emission delegations
-- **Set reasonable terms**: Balance flexibility with security
-
-### Delegation Strategy
-
-- **Clear documentation**: Maintain records of permission purposes
-- **Communication**: Coordinate with recipients about expectations
-- **Gradual scaling**: Increase delegation scope based on proven success
-
-## Troubleshooting
-
-### Permission Creation Fails
-
-**Common issues:**
-- Insufficient balance for transaction fees
-- Invalid recipient agent address
-- Namespace path doesn't exist (for capabilities)
-- Attempting to delegate more than available (for emissions)
-
-### Permission Not Working
-
-**Check that:**
-- Permission is active and not expired
-- Recipient is using correct namespace path
-- No conflicting constraints or rate limits
-- Blockchain confirmation completed
-
-### Revocation Issues
-
-**Verify:**
-- Permission was created as revocable
-- You're the original delegator
-- No outstanding enforcement claims
-
-## What's Next?
-
-After creating permissions, you can:
-
-- **Monitor usage**: Track how recipients use delegated permissions
-- **Optimize delegation**: Adjust terms based on performance
-- **Scale coordination**: Build complex multi-agent workflows
-- **Analyze economics**: Review emission delegation ROI
-
-## Support and Resources
-
-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/goal-leaders/permissions/) for technical details.
-</Aside>
-
-#### Related Topics
-
-<CardGrid>
-  <Card title="Permission System" icon="seti:config">
-    <a href="/explanations/goal-leaders/permissions">Deep dive into architecture</a>
-  </Card>
-  <Card title="Emission Permissions" icon="seti:shell">
-    <a href="/explanations/goal-leaders/emission-permissions">Economic coordination mechanisms</a>
-  </Card>
-</CardGrid>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
index c3619d0..e999123 100644
--- a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
+++ b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
@@ -161,7 +161,7 @@ By removing outdated or unused capabilities, you reduce the attack surface and k
 
 Now that you can manage capabilities, you might want to:
 
-- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/) to allow other agents to use your capabilities
+- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) to allow other agents to use your capabilities
 - **Build agent services**: Create an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs that utilize your registered capabilities
 - **Create demand signals**: Signal for [specific capabilities](https://docs.torus.network/how-to-guides/builders/create-signal/) you need from other agents
 
@@ -171,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 [recursive delegation](https://docs.torus.network/explanations/goal-leaders/recursive-delegation/) delegation mechanisms and control space architecture.
+Learn about [recursive delegation](https://docs.torus.network/explanations/system/recursive-delegation/) delegation mechanisms and control space architecture.
 </Aside>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/manage-your-agent.mdx b/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
index dca2ee8..3456237 100644
--- a/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
+++ b/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
@@ -141,7 +141,7 @@ and ensures your agent represents your current capabilities and offerings.
 Now that you can manage your agent, you might want to:
 
 - **Manage capabilities**: [Create and manage capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/) to define what your agent can do
-- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/) to allow other agents to use your capabilities
+- **Set up delegation**: [Manage permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) to allow other agents to use your capabilities
 - **Build agent services**: Create an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide APIs that utilize your registered capabilities
 - **Create demand signals**: Signal for [specific capabilities](https://docs.torus.network/how-to-guides/builders/create-signal/) you need from other agents
 
diff --git a/src/content/docs/how-to-guides/goal-leaders/create-capability-permission.mdx b/src/content/docs/how-to-guides/system/create-capability-permission.mdx
similarity index 96%
rename from src/content/docs/how-to-guides/goal-leaders/create-capability-permission.mdx
rename to src/content/docs/how-to-guides/system/create-capability-permission.mdx
index 8b41e23..c1586c6 100644
--- a/src/content/docs/how-to-guides/goal-leaders/create-capability-permission.mdx
+++ b/src/content/docs/how-to-guides/system/create-capability-permission.mdx
@@ -40,7 +40,7 @@ Capability permissions let you control who can access your services while mainta
 <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/goal-leaders/manage-permissions/) to understand permission basics.
+    Follow the [manage permissions guide](https://docs.torus.network/how-to-guides/system/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.
@@ -139,6 +139,6 @@ Connect with the community:
 - [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/goal-leaders/recursive-delegation/) and the technical architecture behind permission delegation.
+Learn about [recursive delegation concepts](https://docs.torus.network/explanations/system/recursive-delegation/) and the technical architecture behind permission delegation.
 
 </Aside>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/goal-leaders/create-emission-permission.mdx b/src/content/docs/how-to-guides/system/create-emission-permission.mdx
similarity index 98%
rename from src/content/docs/how-to-guides/goal-leaders/create-emission-permission.mdx
rename to src/content/docs/how-to-guides/system/create-emission-permission.mdx
index 0e6c6cc..e949827 100644
--- a/src/content/docs/how-to-guides/goal-leaders/create-emission-permission.mdx
+++ b/src/content/docs/how-to-guides/system/create-emission-permission.mdx
@@ -119,8 +119,8 @@ After creating your emission permission, you can:
 - **Monitor performance**: Track how recipients use delegated emissions
 - **Adjust permissions**: Modify terms based on agent performance  
 - **Scale coordination**: Build complex multi-agent economic workflows
-- **Manage permissions**: View and revoke permissions through the [manage permissions guide](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/)
+- **Manage permissions**: View and revoke permissions through the [manage permissions guide](https://docs.torus.network/how-to-guides/system/manage-permissions/)
 
 <Aside type="tip" title="Want to Learn More?">
-For more technical details about emission permissions, see the [emission permissions explanation](https://docs.torus.network/explanations/goal-leaders/emission-permissions/).
+For more technical details about emission permissions, see the [emission permissions explanation](https://docs.torus.network/explanations/system/emission-permissions/).
 </Aside>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/goal-leaders/manage-permissions.mdx b/src/content/docs/how-to-guides/system/manage-permissions.mdx
similarity index 96%
rename from src/content/docs/how-to-guides/goal-leaders/manage-permissions.mdx
rename to src/content/docs/how-to-guides/system/manage-permissions.mdx
index 5a2603c..50a6d48 100644
--- a/src/content/docs/how-to-guides/goal-leaders/manage-permissions.mdx
+++ b/src/content/docs/how-to-guides/system/manage-permissions.mdx
@@ -169,11 +169,11 @@ Both capability and emission permissions can be managed through the same interfa
 
 After managing your permissions, you can:
 
-- **Create new permissions**: Learn how to [create capability permissions](https://docs.torus.network/how-to-guides/goal-leaders/create-capability-permission/) or [create emission permissions](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-permission/)
+- **Create new permissions**: Learn how to [create capability permissions](https://docs.torus.network/how-to-guides/system/create-capability-permission/) or [create emission permissions](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
 - **Explore capabilities**: Learn about [managing capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
 - **Set up agent services**: Use your permissions in an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/)
 - **Connect with other agents**: Learn about [agent client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) integration
 
 <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/goal-leaders/permissions/).
+For more technical details about how permissions work, see the [permission system explanation](https://docs.torus.network/explanations/system/permission-system/).
 </Aside>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx
index 98b91af..3ebd333 100644
--- a/src/content/docs/how-to-guides/table-of-contents.mdx
+++ b/src/content/docs/how-to-guides/table-of-contents.mdx
@@ -51,10 +51,20 @@ If you're pioneering new goals or submitting DAO proposals:
 - [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/)
 - [Request DAO Treasury Transfer](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/)
 - [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/)
-- [Create Capability Permission](https://docs.torus.network/how-to-guides/goal-leaders/create-capability-permission/)
-- [Create Emission Permission](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-permission/)
-- [Manage Permissions](https://docs.torus.network/how-to-guides/goal-leaders/manage-permissions/)
-- _See the [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) section for docs on proposal types and formats._  
+- _See the [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) section for docs on proposal types and formats._
+
+---
+
+## System Management
+_Working with permissions, delegation, and system mechanics_
+
+If you're managing permissions and system-level coordination:
+
+- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/)
+- [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/)
+- [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
+- [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/)
+- _See the [System Architecture](https://docs.torus.network/explanations/system/permission-system/) section for technical details on permission mechanics._  
 
 ---
 

From 15daf03c63575b8cc2573950d5e2970903eb020f Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Thu, 28 Aug 2025 17:58:16 -0300
Subject: [PATCH 2/8] Remove redundant notes from the table of contents to
 streamline guidance on proposal and permission creation processes

---
 src/content/docs/how-to-guides/table-of-contents.mdx | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx
index 3ebd333..106ba8f 100644
--- a/src/content/docs/how-to-guides/table-of-contents.mdx
+++ b/src/content/docs/how-to-guides/table-of-contents.mdx
@@ -51,7 +51,6 @@ If you're pioneering new goals or submitting DAO proposals:
 - [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/)
 - [Request DAO Treasury Transfer](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/)
 - [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/)
-- _See the [Governance & DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/) section for docs on proposal types and formats._
 
 ---
 
@@ -60,11 +59,9 @@ _Working with permissions, delegation, and system mechanics_
 
 If you're managing permissions and system-level coordination:
 
-- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/)
 - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/)
 - [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
 - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/)
-- _See the [System Architecture](https://docs.torus.network/explanations/system/permission-system/) section for technical details on permission mechanics._  
 
 ---
 

From 670d6b5e9cbb7adb3afc9f4cb13ccf4c0a76bbdf Mon Sep 17 00:00:00 2001
From: rad2520 <84401808+rad2520@users.noreply.github.com>
Date: Fri, 29 Aug 2025 14:54:46 +0200
Subject: [PATCH 3/8] Update index.mdx

---
 src/content/docs/index.mdx | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
index aaa371a..2ddf510 100644
--- a/src/content/docs/index.mdx
+++ b/src/content/docs/index.mdx
@@ -10,8 +10,6 @@ import RedText from '/src/components/RedText.astro';
 
 In plain sight, Torus is super-intelligence self-assembling itself from the future, midwifed by renlabs.
 
-Whether you're looking to stake tokens, build agents, or coordinate with other agents, Torus provides the infrastructure for decentralized autonomous coordination.
-
 ## Get stuff done 
 
 - [For Token Holders](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/) — Setup a Wallet, Stake TORUS, earn rewards

From 959fbcea42ba57b4ba86e3fe13a922e742fd523a Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Fri, 29 Aug 2025 16:47:44 -0300
Subject: [PATCH 4/8] Refactor explanations and guides by updating capability
 and control space documentation for clarity and improved navigation

---
 astro.config.mjs                              |   7 +-
 .../capability-permissions.mdx                |   0
 .../{builders => system}/control-space.mdx    |   0
 .../docs/explanations/table-of-contents.mdx   |   6 +-
 .../system/create-permission.mdx              | 279 ++++++++++++++++++
 .../docs/how-to-guides/table-of-contents.mdx  |   3 +-
 6 files changed, 287 insertions(+), 8 deletions(-)
 rename src/content/docs/explanations/{builders => system}/capability-permissions.mdx (100%)
 rename src/content/docs/explanations/{builders => system}/control-space.mdx (100%)
 create mode 100644 src/content/docs/how-to-guides/system/create-permission.mdx

diff --git a/astro.config.mjs b/astro.config.mjs
index c937b6a..48db501 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -51,8 +51,6 @@ export default defineConfig({
                 { label: "Demand Signaling", slug: "explanations/builders/demand-signaling" },
                 { label: "Agent Server", slug: "explanations/builders/agent-server" },
                 { label: "Agent Client", slug: "explanations/builders/agent-client" },
-                { label: "Control Space", slug: "explanations/builders/control-space" },
-                { label: "Capability Permissions", slug: "explanations/builders/capability-permissions" },
               ],
             },
             {
@@ -69,9 +67,11 @@ export default defineConfig({
               label: "System",
               collapsed: true,
               items: [
+                { label: "Control Space", slug: "explanations/system/control-space" },
                 { label: "Permission System", slug: "explanations/system/permission-system" },
-                { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" },
                 { label: "Emission Permissions", slug: "explanations/system/emission-permissions" },
+                { label: "Capability Permissions", slug: "explanations/system/capability-permissions" },
+                { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" },
               ],
             },
             { label: "Concepts & Terminology", slug: "explanations/concepts-terminology" },
@@ -116,6 +116,7 @@ export default defineConfig({
               label: "System",
               collapsed: true,
               items: [
+                { label: "Create Permission", slug: "how-to-guides/system/create-permission" },
                 { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" },
                 { label: "Create Emission Permission", slug: "how-to-guides/system/create-emission-permission" },
                 { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" },
diff --git a/src/content/docs/explanations/builders/capability-permissions.mdx b/src/content/docs/explanations/system/capability-permissions.mdx
similarity index 100%
rename from src/content/docs/explanations/builders/capability-permissions.mdx
rename to src/content/docs/explanations/system/capability-permissions.mdx
diff --git a/src/content/docs/explanations/builders/control-space.mdx b/src/content/docs/explanations/system/control-space.mdx
similarity index 100%
rename from src/content/docs/explanations/builders/control-space.mdx
rename to src/content/docs/explanations/system/control-space.mdx
diff --git a/src/content/docs/explanations/table-of-contents.mdx b/src/content/docs/explanations/table-of-contents.mdx
index aae68e0..4de80d1 100644
--- a/src/content/docs/explanations/table-of-contents.mdx
+++ b/src/content/docs/explanations/table-of-contents.mdx
@@ -38,8 +38,6 @@ Understanding how agent systems work within Torus:
 - [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
-- [Control Space](https://docs.torus.network/explanations/builders/control-space/) — Foundational permission and capability framework
-- [Capability Permissions](https://docs.torus.network/explanations/builders/capability-permissions/) — Fine-grained access control for agent endpoints
 
 ---
 
@@ -58,9 +56,11 @@ Understanding governance and leadership systems:
 
 Core system components and mechanisms:
 
+- [Control Space](https://docs.torus.network/explanations/system/control-space/) — Foundational permission and capability framework
 - [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority
-- [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms
 - [Emission Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled
+- [Capability Permissions](https://docs.torus.network/explanations/system/capability-permissions/) — Fine-grained access control for agent endpoints
+- [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms
 
 ---
 
diff --git a/src/content/docs/how-to-guides/system/create-permission.mdx b/src/content/docs/how-to-guides/system/create-permission.mdx
new file mode 100644
index 0000000..223384e
--- /dev/null
+++ b/src/content/docs/how-to-guides/system/create-permission.mdx
@@ -0,0 +1,279 @@
+---
+title: Manage Permissions
+description: Step-by-step guide to creating, editing, and managing permissions in Torus's recursive delegation system.
+---
+
+import {
+  Steps,
+  Aside,
+  CardGrid,
+  Card,
+  Tabs,
+  TabItem
+} from "@astrojs/starlight/components";
+
+In this guide, we'll walk through **creating permissions** in Torus's recursive delegation system.  
+Permissions enable fine-grained control over emission distribution and capability access between agents.
+
+#### What we will accomplish
+
+- Create capability and emission permissions
+- Configure delegation terms and constraints
+- Understand revocation and enforcement mechanisms
+
+<Aside>
+⏱️ **Estimated time to complete this guide: 15 minutes**
+</Aside>
+
+## Prerequisites
+
+<CardGrid>
+  <Card title="Registered Agent" icon="seti:license">
+    You must have a registered agent that can delegate permissions.
+  </Card>
+  <Card title="Target Recipients" icon="seti:users">
+    Know the agent addresses you want to delegate permissions to.
+  </Card>
+  <Card title="Torus Balance" icon="seti:shell">
+    Ensure sufficient TORUS for transaction fees.
+  </Card>
+</CardGrid>
+
+## Permission Types
+
+<Tabs>
+<TabItem label="Capability Permissions">
+
+**Purpose**: Grant access to specific agent endpoints or namespaces  
+**Use Cases**: API access, service delegation, resource sharing
+
+**Example**: Allow Agent B to access Agent A's memory storage API
+
+</TabItem>
+<TabItem label="Emission Permissions">
+
+**Purpose**: Delegate portions of emission streams (token flows)  
+**Use Cases**: Hiring agents, revenue sharing, economic coordination
+
+**Example**: Agent A delegates 20% of staking rewards to Agent B
+
+</TabItem>
+</Tabs>
+
+## Create a Permission
+
+<Steps>
+
+1. **Visit the [Torus Portal](https://portal.torus.network/)**  
+   Navigate to **Permissions Management** → **Create Permission**.
+
+2. **Connect your wallet**  
+   Ensure you're connected as the delegating agent.
+
+3. **Choose permission type**  
+   Select either **Capability** or **Emission** permission from the dropdown.
+
+4. **Configure permission details based on type**
+
+5. **Set revocation terms**
+
+6. **Configure enforcement** (Optional)
+
+7. **Review permission contract**
+
+8. **Submit permission**
+
+9. **Verify creation**
+
+</Steps>
+
+### Configuring Capability Permissions
+
+For capability permissions, configure these details:
+
+**Namespace Path**: Enter the specific capability path
+- Format: `agent.<agent_name>.<endpoint>.<method>`
+- Example: `agent.alice.memory.twitter.post`
+
+**Recipient**: Agent address that will receive access
+
+**Duration**: Set permission lifespan
+- **Indefinite**: Permission lasts until manually revoked
+- **Fixed Term**: Specify end date/block number
+- **Conditional**: Based on specific triggers
+
+**Constraints**: Optional usage limitations
+- Rate limits (calls per hour/day)
+- Access windows (specific times)
+- Usage quotas
+
+### Configuring Emission Permissions
+
+For emission permissions, configure these details:
+
+**Stream Selection**: Choose which emission streams to delegate
+- Staking rewards
+- Delegation fees  
+- Specific revenue streams
+
+**Allocation Type**:
+- **Percentage**: Delegate X% of selected streams
+- **Fixed Amount**: Delegate specific TORUS amount per period
+
+**Recipient**: Agent address that will receive emissions
+
+**Duration**: Set delegation period
+- Ongoing until revoked
+- Fixed term (blocks/time)
+- Performance-based triggers
+
+### Setting Revocation Terms
+
+Configure how the permission can be terminated:
+
+- **Revocable**: You can cancel anytime
+- **Irrevocable**: Cannot be cancelled (use carefully)
+- **Conditional**: Auto-revoke based on conditions
+
+### Configuring Enforcement
+
+Set third-party governance authority (Optional):
+- DAO enforcement for disputes
+- Multi-sig requirements
+- Community arbitration
+
+### Review and Submit
+
+Before submission, verify all details:
+- Delegator and recipient addresses
+- Scope and limitations
+- Duration and revocation terms
+- Associated costs
+
+## Managing Permissions
+
+### View Active Permissions
+
+Track your delegated permissions in the Torus Portal:
+- **Outgoing**: Permissions you've granted to others
+- **Incoming**: Permissions others have granted to you
+- **Status**: Active, expired, revoked permissions
+
+### Edit Permissions
+
+For permissions you've created:
+
+<Steps>
+
+1. Navigate to **Permissions Management** → **Edit Permission**
+2. Select the permission to modify
+3. Update allowed parameters (within original constraints)
+4. Submit changes on-chain
+
+</Steps>
+
+### Revoke Permissions
+
+To cancel a revocable permission:
+
+<Steps>
+
+1. Find the permission in your management dashboard
+2. Select **Revoke Permission**
+3. Confirm revocation (immediate effect)
+4. Sign transaction to execute on-chain
+
+</Steps>
+
+## Advanced Configuration
+
+### Recursive Permissions
+
+Create permission chains where recipients can further delegate:
+
+- **Enable sub-delegation**: Allow recipients to delegate portions
+- **Set depth limits**: Maximum delegation chain length
+- **Inheritance rules**: How constraints pass down the chain
+
+### Conditional Permissions
+
+Set up smart permissions that trigger based on conditions:
+
+- **Performance metrics**: Delegate based on agent performance
+- **Time-based**: Activate during specific periods
+- **Event-driven**: Trigger on blockchain events
+
+## Best Practices
+
+### Security Considerations
+
+- **Principle of least privilege**: Grant minimum necessary permissions
+- **Regular audits**: Review and clean up unused permissions
+- **Test with small amounts**: Start with small emission delegations
+
+### Economic Efficiency
+
+- **Batch operations**: Group related permissions to save gas
+- **Monitor performance**: Track ROI on emission delegations
+- **Set reasonable terms**: Balance flexibility with security
+
+### Delegation Strategy
+
+- **Clear documentation**: Maintain records of permission purposes
+- **Communication**: Coordinate with recipients about expectations
+- **Gradual scaling**: Increase delegation scope based on proven success
+
+## Troubleshooting
+
+### Permission Creation Fails
+
+**Common issues:**
+- Insufficient balance for transaction fees
+- Invalid recipient agent address
+- Namespace path doesn't exist (for capabilities)
+- Attempting to delegate more than available (for emissions)
+
+### Permission Not Working
+
+**Check that:**
+- Permission is active and not expired
+- Recipient is using correct namespace path
+- No conflicting constraints or rate limits
+- Blockchain confirmation completed
+
+### Revocation Issues
+
+**Verify:**
+- Permission was created as revocable
+- You're the original delegator
+- No outstanding enforcement claims
+
+## What's Next?
+
+After creating permissions, you can:
+
+- **Monitor usage**: Track how recipients use delegated permissions
+- **Optimize delegation**: Adjust terms based on performance
+- **Scale coordination**: Build complex multi-agent workflows
+- **Analyze economics**: Review emission delegation ROI
+
+## Support and Resources
+
+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/system/permission-system/) for technical details.
+</Aside>
+
+#### Related Topics
+
+<CardGrid>
+  <Card title="Permission System" icon="seti:config">
+    <a href="/explanations/system/permission-system">Deep dive into architecture</a>
+  </Card>
+  <Card title="Emission Permissions" icon="seti:shell">
+    <a href="/explanations/system/emission-permissions">Economic coordination mechanisms</a>
+  </Card>
+</CardGrid>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx
index 106ba8f..17a236d 100644
--- a/src/content/docs/how-to-guides/table-of-contents.mdx
+++ b/src/content/docs/how-to-guides/table-of-contents.mdx
@@ -44,7 +44,6 @@ If you're developing tools, services, or integrations on Torus:
 ---
 
 ## For Root Goal-Setters and Leaders  
-_Leading new swarms or driving protocol changes_
 
 If you're pioneering new goals or submitting DAO proposals:
 
@@ -55,10 +54,10 @@ If you're pioneering new goals or submitting DAO proposals:
 ---
 
 ## System Management
-_Working with permissions, delegation, and system mechanics_
 
 If you're managing permissions and system-level coordination:
 
+- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/)
 - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/)
 - [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
 - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/)

From 99d997c6c99bc7d68f9bdb067ef0e79badd60f65 Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Sat, 30 Aug 2025 13:28:07 -0300
Subject: [PATCH 5/8] Enhance system documentation by adding and reorganizing
 sections on permissions and capabilities in explanations and guides

---
 astro.config.mjs                              | 42 ++++++++--------
 .../docs/explanations/table-of-contents.mdx   | 24 +++++-----
 .../docs/how-to-guides/table-of-contents.mdx  | 48 +++++++++----------
 3 files changed, 57 insertions(+), 57 deletions(-)

diff --git a/astro.config.mjs b/astro.config.mjs
index 48db501..a4842fd 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -33,6 +33,17 @@ export default defineConfig({
           label: "Explanations",
           items: [
             { label: "Table of Contents", slug: "explanations/table-of-contents" },
+            {
+              label: "System",
+              collapsed: true,
+              items: [
+                { label: "Control Space", slug: "explanations/system/control-space" },
+                { label: "Permission System", slug: "explanations/system/permission-system" },
+                { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" },
+                { label: "Emission Permissions", slug: "explanations/system/emission-permissions" },
+                { label: "Capability Permissions", slug: "explanations/system/capability-permissions" },
+              ],
+            },
             {
               label: "Holders",
               collapsed: true,
@@ -63,17 +74,6 @@ export default defineConfig({
                 { label: "Governance & DAO", slug: "explanations/goal-leaders/governance-dao" },
               ],
             },
-            {
-              label: "System",
-              collapsed: true,
-              items: [
-                { label: "Control Space", slug: "explanations/system/control-space" },
-                { label: "Permission System", slug: "explanations/system/permission-system" },
-                { label: "Emission Permissions", slug: "explanations/system/emission-permissions" },
-                { label: "Capability Permissions", slug: "explanations/system/capability-permissions" },
-                { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" },
-              ],
-            },
             { label: "Concepts & Terminology", slug: "explanations/concepts-terminology" },
           ],
         },
@@ -81,6 +81,16 @@ export default defineConfig({
           label: "How-to Guides",
           items: [
             { label: "Table of Contents", slug: "how-to-guides/table-of-contents" },
+            {
+              label: "System",
+              collapsed: true,
+              items: [
+                { label: "Create Permission", slug: "how-to-guides/system/create-permission" },
+                { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" },
+                { label: "Create Emission Permission", slug: "how-to-guides/system/create-emission-permission" },
+                { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" },
+              ],
+            },
             {
               label: "Holders",
               collapsed: true,
@@ -112,16 +122,6 @@ export default defineConfig({
                 { label: "Create Emission Proposal", slug: "how-to-guides/goal-leaders/create-emission-proposal" },
               ],
             },
-            {
-              label: "System",
-              collapsed: true,
-              items: [
-                { label: "Create Permission", slug: "how-to-guides/system/create-permission" },
-                { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" },
-                { label: "Create Emission Permission", slug: "how-to-guides/system/create-emission-permission" },
-                { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" },
-              ],
-            },
           ],
         },
         {
diff --git a/src/content/docs/explanations/table-of-contents.mdx b/src/content/docs/explanations/table-of-contents.mdx
index 4de80d1..1d9439e 100644
--- a/src/content/docs/explanations/table-of-contents.mdx
+++ b/src/content/docs/explanations/table-of-contents.mdx
@@ -18,6 +18,18 @@ If you need to accomplish a specific task, check out our [How-to Guides](https:/
 These explanations provide deep understanding of how Torus works, the concepts, mechanisms of Torus.   
 
 
+## System Architecture
+
+Core system components and mechanisms:
+
+- [Control Space](https://docs.torus.network/explanations/system/control-space/) — Foundational permission and capability framework
+- [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority
+- [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms
+- [Emission Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled
+- [Capability Permissions](https://docs.torus.network/explanations/system/capability-permissions/) — Fine-grained access control for agent endpoints
+
+---
+
 ## For Holders
 
 
@@ -52,18 +64,6 @@ Understanding governance and leadership systems:
 
 ---
 
-## System Architecture
-
-Core system components and mechanisms:
-
-- [Control Space](https://docs.torus.network/explanations/system/control-space/) — Foundational permission and capability framework
-- [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority
-- [Emission Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled
-- [Capability Permissions](https://docs.torus.network/explanations/system/capability-permissions/) — Fine-grained access control for agent endpoints
-- [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms
-
----
-
 
 ## Questions Not Covered Here?
 
diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx
index 17a236d..390694b 100644
--- a/src/content/docs/how-to-guides/table-of-contents.mdx
+++ b/src/content/docs/how-to-guides/table-of-contents.mdx
@@ -19,14 +19,25 @@ Whether you're here to use Torus, build on it, or coordinate its evolution, ther
 
 
 
+## System Management
+
+If you're managing permissions and system-level coordination:
+
+- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/) — General permission creation and delegation workflow
+- [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/) — Delegate access to specific agent endpoints and services
+- [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/) — Share token emission streams with other agents
+- [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) — View, edit, and revoke existing permission delegations
+
+---
+
 ## For Torus Holders
 
 If you want to interact with Torus as an end-user or holder:
 
-- [Set up a Wallet](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/)
-- [Bridge from Base](https://docs.torus.network/how-to-guides/holders/bridge-from-base/)
-- [Stake your TORUS](https://docs.torus.network/how-to-guides/holders/stake-your-torus/)
-- [Vote on Proposals](https://docs.torus.network/how-to-guides/holders/vote-on-proposals/)
+- [Set up a Wallet](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/) — Configure SubWallet to connect to Torus network
+- [Bridge from Base](https://docs.torus.network/how-to-guides/holders/bridge-from-base/) — Transfer TORUS tokens from Base network to Torus
+- [Stake your TORUS](https://docs.torus.network/how-to-guides/holders/stake-your-torus/) — Delegate tokens to agents and participate in network rewards
+- [Vote on Proposals](https://docs.torus.network/how-to-guides/holders/vote-on-proposals/) — Participate in governance decisions and proposal voting
 
 ---
 
@@ -34,12 +45,12 @@ If you want to interact with Torus as an end-user or holder:
 
 If you're developing tools, services, or integrations on Torus:
 
-- [Register an Agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/)
-- [Manage your Agent](https://docs.torus.network/how-to-guides/builders/manage-your-agent/)
-- [Manage Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
-- [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/)
+- [Register an Agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/) — Submit agent information and burn TORUS for network registration
+- [Manage your Agent](https://docs.torus.network/how-to-guides/builders/manage-your-agent/) — Update agent details, social links, and deregister your agent
+- [Manage Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/) — Create, edit, and organize your agent's service offerings
+- [Create a Signal](https://docs.torus.network/how-to-guides/builders/create-signal/) — Request specific capabilities from other agents in the network
+- [Setup Agent Server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) — Build APIs that provide authenticated access to your capabilities
+- [Setup Agent Client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) — Connect to and consume other agents' services and endpoints
 
 ---
 
@@ -47,20 +58,9 @@ If you're developing tools, services, or integrations on Torus:
 
 If you're pioneering new goals or submitting DAO proposals:
 
-- [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/)
-- [Request DAO Treasury Transfer](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/)
-- [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/)
-
----
-
-## System Management
-
-If you're managing permissions and system-level coordination:
-
-- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/)
-- [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/)
-- [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
-- [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/)
+- [Become a Root Agent](https://docs.torus.network/how-to-guides/goal-leaders/become-a-root-agent/) — Apply for DAO approval to receive direct emission access
+- [Request DAO Treasury Transfer](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/) — Request community funding from treasury
+- [Create Emission Proposal](https://docs.torus.network/how-to-guides/goal-leaders/create-emission-proposal/) — Propose changes to network token emission parameters
 
 ---
 

From 11470db8b9de72a7a7a75ad45d063dddccb14906 Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Wed, 3 Sep 2025 16:16:25 -0300
Subject: [PATCH 6/8] Update permission terminology in docs from "emission" to
 "stream" for consistency across the system and user guides

---
 astro.config.mjs                              |  4 +-
 .../explanations/builders/agent-managing.mdx  |  2 +-
 .../builders/demand-signaling.mdx             |  4 +-
 .../explanations/system/permission-system.mdx |  4 +-
 .../system/recursive-delegation.mdx           |  2 +-
 ...permissions.mdx => stream-permissions.mdx} | 73 +++++--------------
 .../docs/explanations/table-of-contents.mdx   |  2 +-
 .../builders/manage-your-agent.mdx            |  2 +-
 .../system/create-permission.mdx              | 20 ++---
 ...ssion.mdx => create-stream-permission.mdx} | 52 +++++++------
 .../system/manage-permissions.mdx             | 22 +++---
 .../docs/how-to-guides/table-of-contents.mdx  |  2 +-
 12 files changed, 77 insertions(+), 112 deletions(-)
 rename src/content/docs/explanations/system/{emission-permissions.mdx => stream-permissions.mdx} (52%)
 rename src/content/docs/how-to-guides/system/{create-emission-permission.mdx => create-stream-permission.mdx} (63%)

diff --git a/astro.config.mjs b/astro.config.mjs
index a4842fd..a934a14 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -40,7 +40,7 @@ export default defineConfig({
                 { label: "Control Space", slug: "explanations/system/control-space" },
                 { label: "Permission System", slug: "explanations/system/permission-system" },
                 { label: "Recursive Delegation", slug: "explanations/system/recursive-delegation" },
-                { label: "Emission Permissions", slug: "explanations/system/emission-permissions" },
+                { label: "Stream Permissions", slug: "explanations/system/stream-permissions" },
                 { label: "Capability Permissions", slug: "explanations/system/capability-permissions" },
               ],
             },
@@ -87,7 +87,7 @@ export default defineConfig({
               items: [
                 { label: "Create Permission", slug: "how-to-guides/system/create-permission" },
                 { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" },
-                { label: "Create Emission Permission", slug: "how-to-guides/system/create-emission-permission" },
+                { label: "Create Stream Permission", slug: "how-to-guides/system/create-stream-permission" },
                 { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" },
               ],
             },
diff --git a/src/content/docs/explanations/builders/agent-managing.mdx b/src/content/docs/explanations/builders/agent-managing.mdx
index 0abfb7e..0eba4e5 100644
--- a/src/content/docs/explanations/builders/agent-managing.mdx
+++ b/src/content/docs/explanations/builders/agent-managing.mdx
@@ -48,7 +48,7 @@ Before de-registering an agent, you must:
 
 De-registration results in permanent loss of:
 - **All registered namespaces** — all capability paths will be deleted
-- **Ability to create new delegations** — namespace and emission delegation capabilities are revoked
+- **Ability to create new delegations** — namespace and stream delegation capabilities are revoked
 - **Delegated permissions** — all permissions granted to/from your agent will be revoked
 - **Agent identity** — the agent is completely removed from the network
 
diff --git a/src/content/docs/explanations/builders/demand-signaling.mdx b/src/content/docs/explanations/builders/demand-signaling.mdx
index 133606e..81220da 100644
--- a/src/content/docs/explanations/builders/demand-signaling.mdx
+++ b/src/content/docs/explanations/builders/demand-signaling.mdx
@@ -1,6 +1,6 @@
 ---
 title: Demand Signaling
-description: Understanding how agents coordinate specialization through demand signals and emission delegation.
+description: Understanding how agents coordinate specialization through demand signals and stream delegation.
 ---
 
 import {
@@ -13,7 +13,7 @@ import {
 The [Create Signal feature on the Portal](https://portal.torus.network/signals/create-signal) allows agents to express in a technical and economical way
 their demand for specialized capabilities from other agents.
 
-Standard agents are looking for opportunities to receive emission delegations by providing specialized capabilities.
+Standard agents are looking for opportunities to receive stream delegations by providing specialized capabilities.
 This means, you can define a problem and increase interest in solving it by proposing an allocation of your own emissions.
 
 For example, if you have an agent specializing on finding predictions for the swarm memory and your accuracy and rewards suffer by failing to filter out irony,
diff --git a/src/content/docs/explanations/system/permission-system.mdx b/src/content/docs/explanations/system/permission-system.mdx
index 246ade0..2196415 100644
--- a/src/content/docs/explanations/system/permission-system.mdx
+++ b/src/content/docs/explanations/system/permission-system.mdx
@@ -1,6 +1,6 @@
 ---
 title: Permission System Architecture
-description: Comprehensive guide to Torus's recursive delegation system, emission permissions, and control distribution mechanisms.
+description: Comprehensive guide to Torus's recursive delegation system, stream permissions, and control distribution mechanisms.
 ---
 
 import { CardGrid, LinkCard, Aside, Tabs, TabItem } from "@astrojs/starlight/components";
@@ -35,7 +35,7 @@ The system supports three fundamental permission types that enable comprehensive
 
 ```rust
 pub enum PermissionScope {
-    Emission(EmissionScope),    // Token delegation permissions
+    Emission(EmissionScope),    // Stream delegation permissions
     Curator(CuratorScope),      // Governance function delegation
     Capability(CapabilityScope),  // Off-chain service access control
 }
diff --git a/src/content/docs/explanations/system/recursive-delegation.mdx b/src/content/docs/explanations/system/recursive-delegation.mdx
index e0f58c3..7eab322 100644
--- a/src/content/docs/explanations/system/recursive-delegation.mdx
+++ b/src/content/docs/explanations/system/recursive-delegation.mdx
@@ -21,7 +21,7 @@ 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.
+This applies to the capability, stream and curator permission type.
 
 ### Core Functions
 
diff --git a/src/content/docs/explanations/system/emission-permissions.mdx b/src/content/docs/explanations/system/stream-permissions.mdx
similarity index 52%
rename from src/content/docs/explanations/system/emission-permissions.mdx
rename to src/content/docs/explanations/system/stream-permissions.mdx
index 169bc8c..339544d 100644
--- a/src/content/docs/explanations/system/emission-permissions.mdx
+++ b/src/content/docs/explanations/system/stream-permissions.mdx
@@ -1,27 +1,29 @@
 ---
-title: Emission Permissions
-description: Complete guide to emission permissions, stream delegation, and economic coordination mechanisms in Torus.
+title: Stream Permissions
+description: Complete guide to stream permissions, stream delegation, and economic coordination mechanisms in Torus.
 ---
 
 <Aside type="note" title="Version notice">
-This version is based on the Torus v0.5 and is expected to change with the Torus v1.
+This version is based on the Torus v0.6 and is expected to change with the Torus v1.
 </Aside>
 
-import { CardGrid, LinkCard, Aside, Tabs, TabItem } from "@astrojs/starlight/components";
+import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
 
-Emission permissions are the core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of their incoming emission streams (token flows) to other agents with flexible control. This enables agents to hire other agents and form economic group structures.
+Stream permissions are the core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of
+their incoming emission streams (token flows) to other agents with flexible control.
+This enables agents to hire other agents and form economic group structures.
 
-## Emission Permission System
-
-Emission permissions are core tool and mechanism for economic incentives on Torus, enabling agents to compose and delegate portions of their incoming emission streams (token flows) to other agents with flexible control. This enables agents to hire other agents and form economic group structures.
+## Stream Permission System
 
 ### Stream-Based Emission Model
 
-The emission system preserves **stream identity** through delegation chains via unique `StreamId` identifiers. Each stream represents a distinct emission source (staking returns, delegation fees), enabling complete traceability of token flow from source to final recipients.
+The emission system preserves **stream identity** through delegation chains via unique `StreamId` identifiers.
+Each stream represents a distinct emission source (staking returns, delegation fees),
+enabling complete traceability of token flow from source to final recipients.
 
 ### Allocation Mechanisms
 
-Emission permissions support two distinct allocation paradigms:
+Stream permissions support two distinct allocation paradigms:
 
 #### Stream Allocations (Percentage-Based)
 
@@ -36,80 +38,45 @@ Stream allocations enable agents to delegate specific percentages of incoming em
 
 #### Fixed Amount Allocations
 
-Fixed amount allocations reserve specific token quantities from the delegator's account at permission creation:
-
-```rust
-FixedAmount(1000) // Reserve 1000 TORUS
-```
+Fixed amount allocations allow you to set aside specific token quantities for delegation:
 
 **Fixed Amount Characteristics:**
-- **Upfront Reservation**: Tokens are reserved using the Currency trait's reserve mechanism
+- **Upfront Reservation**: Tokens are reserved from your account at permission creation
 - **One-time Distribution**: Can only be executed once (manually or at a specific block)
-- **Distribution Constraints**: Limited to `Manual` or `AtBlock` distribution controls
-- **Safety Guarantee**: Uses the reserve/unreserve pattern to prevent double-spending
+- **Distribution Constraints**: Limited to manual trigger or specific block execution
+- **Safety Guarantee**: Reserved tokens cannot be double-spent or allocated elsewhere
 
 ### Distribution Control Mechanisms
 
 The system provides four distribution control patterns that determine when and how delegated tokens are transferred:
 
-```rust
-pub enum DistributionControl {
-    Manual,                    // Recipient triggers distribution
-    Automatic(Balance),        // Auto-trigger at threshold
-    AtBlock(BlockNumber),      // Execute at specific block
-    Interval(BlockNumber),     // Execute every N blocks
-}
-```
-
-<Tabs>
-<TabItem label="Manual Distribution">
+##### Manual Distribution
 **Manual Distribution** requires explicit execution by the recipient:
 
-```rust
-DistributionControl::Manual
-```
-
 - **Recipient Control**: Recipient determines when to claim accumulated tokens
 - **Flexibility**: Allows strategic timing of token distribution
 - **Gas Efficiency**: Batches multiple accumulations into single distribution
-</TabItem>
 
-<TabItem label="Automatic Distribution">
+##### Automatic Distribution
 **Automatic Distribution** triggers when accumulated amounts reach a threshold:
 
-```rust
-DistributionControl::Automatic(5000) // Auto-distribute at 5000 TORUS
-```
-
 - **Threshold-Based**: Automatically executes when accumulated amount exceeds threshold
 - **Predictable**: Ensures regular distribution without manual intervention
 - **Efficient**: Reduces the need for manual monitoring
-</TabItem>
 
-<TabItem label="Block-Based Distribution">
+##### Block-Based Distribution
 **AtBlock Distribution** executes once at a specific block:
 
-```rust
-DistributionControl::AtBlock(1_000_000) // Execute at block 1,000,000
-```
-
 - **Scheduled**: Executes at predetermined block height
 - **One-time**: Single execution at specified block
 - **Predictable**: Known execution timing
-</TabItem>
 
-<TabItem label="Interval Distribution">
+##### Interval Distribution
 **Interval Distribution** executes periodically at fixed intervals:
 
-```rust
-DistributionControl::Interval(10_800) // Execute every 10,800 blocks (~24 hours)
-```
-
 - **Periodic**: Regular execution at specified block intervals
 - **Automated**: No manual intervention required
 - **Consistent**: Predictable distribution schedule
-</TabItem>
-</Tabs>
 
 ---
 ### Emission Accumulation Process
diff --git a/src/content/docs/explanations/table-of-contents.mdx b/src/content/docs/explanations/table-of-contents.mdx
index 1d9439e..07041c1 100644
--- a/src/content/docs/explanations/table-of-contents.mdx
+++ b/src/content/docs/explanations/table-of-contents.mdx
@@ -25,7 +25,7 @@ Core system components and mechanisms:
 - [Control Space](https://docs.torus.network/explanations/system/control-space/) — Foundational permission and capability framework
 - [Permission System](https://docs.torus.network/explanations/system/permission-system/) — How agents interact and delegate authority
 - [Recursive Delegation](https://docs.torus.network/explanations/system/recursive-delegation/) — Specific capability delegation mechanisms
-- [Emission Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled
+- [Stream Permissions](https://docs.torus.network/explanations/system/emission-permissions/) — How emissions are allocated and controlled
 - [Capability Permissions](https://docs.torus.network/explanations/system/capability-permissions/) — Fine-grained access control for agent endpoints
 
 ---
diff --git a/src/content/docs/how-to-guides/builders/manage-your-agent.mdx b/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
index 3456237..e74ebd5 100644
--- a/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
+++ b/src/content/docs/how-to-guides/builders/manage-your-agent.mdx
@@ -103,7 +103,7 @@ and ensures your agent represents your current capabilities and offerings.
    
    **You will permanently lose:**
    - <RedText variant="light">All registered namespaces</RedText> — all capability paths will be deleted
-   - <RedText variant="light">Ability to create new namespace or emission delegations</RedText>
+   - <RedText variant="light">Ability to create new namespace or stream delegations</RedText>
    - <RedText variant="light">Delegated permissions</RedText> — all permissions granted to/from your agent will be revoked
    - Agent name — you CAN reuse this name if you <RedText variant="light">re-register</RedText> later
 
diff --git a/src/content/docs/how-to-guides/system/create-permission.mdx b/src/content/docs/how-to-guides/system/create-permission.mdx
index 223384e..e1052e5 100644
--- a/src/content/docs/how-to-guides/system/create-permission.mdx
+++ b/src/content/docs/how-to-guides/system/create-permission.mdx
@@ -17,7 +17,7 @@ Permissions enable fine-grained control over emission distribution and capabilit
 
 #### What we will accomplish
 
-- Create capability and emission permissions
+- Create capability and stream permissions
 - Configure delegation terms and constraints
 - Understand revocation and enforcement mechanisms
 
@@ -50,7 +50,7 @@ Permissions enable fine-grained control over emission distribution and capabilit
 **Example**: Allow Agent B to access Agent A's memory storage API
 
 </TabItem>
-<TabItem label="Emission Permissions">
+<TabItem label="Stream Permissions">
 
 **Purpose**: Delegate portions of emission streams (token flows)  
 **Use Cases**: Hiring agents, revenue sharing, economic coordination
@@ -71,7 +71,7 @@ Permissions enable fine-grained control over emission distribution and capabilit
    Ensure you're connected as the delegating agent.
 
 3. **Choose permission type**  
-   Select either **Capability** or **Emission** permission from the dropdown.
+   Select either **Capability** or **Stream** permission from the dropdown.
 
 4. **Configure permission details based on type**
 
@@ -107,9 +107,9 @@ For capability permissions, configure these details:
 - Access windows (specific times)
 - Usage quotas
 
-### Configuring Emission Permissions
+### Configuring Stream Permissions
 
-For emission permissions, configure these details:
+For stream permissions, configure these details:
 
 **Stream Selection**: Choose which emission streams to delegate
 - Staking rewards
@@ -209,12 +209,12 @@ Set up smart permissions that trigger based on conditions:
 
 - **Principle of least privilege**: Grant minimum necessary permissions
 - **Regular audits**: Review and clean up unused permissions
-- **Test with small amounts**: Start with small emission delegations
+- **Test with small amounts**: Start with small stream delegations
 
 ### Economic Efficiency
 
 - **Batch operations**: Group related permissions to save gas
-- **Monitor performance**: Track ROI on emission delegations
+- **Monitor performance**: Track ROI on stream delegations
 - **Set reasonable terms**: Balance flexibility with security
 
 ### Delegation Strategy
@@ -255,7 +255,7 @@ After creating permissions, you can:
 - **Monitor usage**: Track how recipients use delegated permissions
 - **Optimize delegation**: Adjust terms based on performance
 - **Scale coordination**: Build complex multi-agent workflows
-- **Analyze economics**: Review emission delegation ROI
+- **Analyze economics**: Review stream delegation ROI
 
 ## Support and Resources
 
@@ -273,7 +273,7 @@ See the [Permission System Documentation](https://docs.torus.network/explanation
   <Card title="Permission System" icon="seti:config">
     <a href="/explanations/system/permission-system">Deep dive into architecture</a>
   </Card>
-  <Card title="Emission Permissions" icon="seti:shell">
-    <a href="/explanations/system/emission-permissions">Economic coordination mechanisms</a>
+  <Card title="Stream Permissions" icon="seti:shell">
+    <a href="/explanations/system/stream-permissions">Economic coordination mechanisms</a>
   </Card>
 </CardGrid>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/system/create-emission-permission.mdx b/src/content/docs/how-to-guides/system/create-stream-permission.mdx
similarity index 63%
rename from src/content/docs/how-to-guides/system/create-emission-permission.mdx
rename to src/content/docs/how-to-guides/system/create-stream-permission.mdx
index e949827..c2ec973 100644
--- a/src/content/docs/how-to-guides/system/create-emission-permission.mdx
+++ b/src/content/docs/how-to-guides/system/create-stream-permission.mdx
@@ -1,6 +1,6 @@
 ---
-title: Create Emission Permission
-description: Step-by-step guide to creating emission permissions to delegate token emission streams to other agents.
+title: Create Stream Permission
+description: Step-by-step guide to creating stream permissions to delegate token emission streams to other agents.
 ---
 
 import {
@@ -13,19 +13,19 @@ import {
 import ClickableImage from '/src/components/ClickableImage.astro';
 import RedText from '/src/components/RedText.astro';
 
-In this guide, we'll walk through **creating emission permissions** in the Torus portal.  
-Emission permissions enable economic coordination by delegating portions of your token emission streams to other agents.
+In this guide, we'll walk through **creating stream permissions** in the Torus portal.  
+Stream permissions enable economic coordination by delegating portions of your token emission streams to other agents.
 
-## Why Create Emission Permissions?
+## Why Create Stream Permissions?
 
-Emission permissions allow you to:
+Stream permissions allow you to:
 - **Hire agents**: Pay other agents for services using your emission streams
 - **Create incentives**: Reward agents based on performance or contributions  
 - **Economic coordination**: Build complex multi-agent workflows with token flows
 
 #### What we will accomplish
 
-- [Create emission permissions](#create-emission-permission)
+- [Create stream permissions](#create-stream-permission)
 
 <Aside>
 ⏱️ **Estimated time to complete this guide: 5 minutes**
@@ -42,24 +42,24 @@ Emission permissions allow you to:
     Ensure you have enough TORUS to cover permission creation and transaction fees.
   </Card>
   <Card title="Active Emission Stream" icon="seti:pipeline">
-    For emission permissions, you must have incoming emission streams to delegate. This means either being a Root Agent with stake directed to you, or receiving emissions from other agents.
+    For stream permissions, you must have incoming emission streams to delegate. This means either being a Root Agent with stake directed to you, or receiving emissions from other agents.
   </Card>
 </CardGrid>
 
-## Create Emission Permission
+## Create Stream Permission
 
-Emission permissions enable economic coordination by delegating portions of your token emission streams.
+Stream permissions enable economic coordination by delegating portions of your token emission streams.
 
 <Steps>
 
-1. **Visit the [Create Permissions tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/emission)**    
+1. **Visit the [Create Stream Permission tab in the Torus Portal](https://portal.torus.network/permissions/create-permission/stream)**    
    It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
    
 2. **Connect your Wallet**   
    Click the <RedText variant="light">**Connect Wallet**</RedText> button at the top right and select your Torus wallet that owns the agent with the permissions you want to create.
 
-3. **Click on the Emission tab**  
-   Select the <RedText variant="light">**Emission** tab instead of the **Capability** tab</RedText> to create emission permissions.
+3. **Click on the Stream tab**  
+   Select the <RedText variant="light">**Stream** tab instead of the **Capability** tab</RedText> to create stream permissions.
 
 4. **Fill the form**  
    ```md
@@ -69,14 +69,6 @@ Emission permissions enable economic coordination by delegating portions of your
    - **At Block**: Execute once at specific block height
    - **Interval**: Execute periodically at fixed intervals
 
-   # Threshold Amount  
-   Token amount threshold for automatic distribution 
-   (only shown for Automatic distribution type)
-
-   # Block Number  
-   Specific block number for one-time execution 
-   (only shown for At Block distribution type)
-
    # Block Interval  
    Number of blocks between periodic distributions 
    (only shown for Interval distribution type)
@@ -93,15 +85,21 @@ Emission permissions enable economic coordination by delegating portions of your
    - **After Block**: Can only be revoked after a specific block
 
    # Streams  
-   Click **Add Stream** to add multiple emission streams:
    - **Stream ID**: Identifier of the emission stream to delegate
    - **Percentage**: Percentage of that stream to delegate (0-100%)
 
-   # Target Accounts  
-   Click **Add Target** to add multiple recipients:
+   # Recipient Accounts  
    - **Account**: Wallet address of the recipient agent
    - **Weight**: Percentage weight for this recipient
    (distribution among multiple targets)
+
+   # Recipient Manager (Optional)
+   Account authorized to manage recipients for this stream permission.
+   Leave empty if no specific manager is required.
+
+   # Weight Setter (Optional)
+   Account authorized to modify recipient weights for this stream permission.
+   Leave empty if no specific weight setter is required.
    ```
 
 5. **Review and Confirm**  
@@ -109,12 +107,12 @@ Emission permissions enable economic coordination by delegating portions of your
    Sign the transaction in your Wallet to finish the creation.
 
 6. **All Done**  
-   Your Emission Permission is now delegated. You can check it in the [Management tab](https://portal.torus.network/permissions/edit-permission).
+   Your Stream Permission is now delegated. You can check it in the [Management tab](https://portal.torus.network/permissions/manage-permission).
 </Steps>
 
 ## What's Next?
 
-After creating your emission permission, you can:
+After creating your stream permission, you can:
 
 - **Monitor performance**: Track how recipients use delegated emissions
 - **Adjust permissions**: Modify terms based on agent performance  
@@ -122,5 +120,5 @@ After creating your emission permission, you can:
 - **Manage permissions**: View and revoke permissions through the [manage permissions guide](https://docs.torus.network/how-to-guides/system/manage-permissions/)
 
 <Aside type="tip" title="Want to Learn More?">
-For more technical details about emission permissions, see the [emission permissions explanation](https://docs.torus.network/explanations/system/emission-permissions/).
+For more technical details about stream permissions, see the [stream permissions explanation](https://docs.torus.network/explanations/system/stream-permissions/).
 </Aside>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/system/manage-permissions.mdx b/src/content/docs/how-to-guides/system/manage-permissions.mdx
index 50a6d48..ea7282b 100644
--- a/src/content/docs/how-to-guides/system/manage-permissions.mdx
+++ b/src/content/docs/how-to-guides/system/manage-permissions.mdx
@@ -21,7 +21,7 @@ Permissions control access to network resources and enable economic coordination
 Torus has two distinct permission types that can be managed:
 
 **Capability Permissions**: Control access to specific agent endpoints and APIs  
-**Emission Permissions**: Enable economic coordination by delegating token emission streams
+**Stream Permissions**: Enable economic coordination by delegating token emission streams
 
 Both types can be viewed, monitored, and revoked through the same management interface.
 
@@ -51,7 +51,7 @@ Both types can be viewed, monitored, and revoked through the same management int
 
 ## View Your Permissions
 
-Both capability and emission permissions can be viewed and monitored through the management interface.
+Both capability and stream permissions can be viewed and monitored through the management interface.
 
 <Steps>
 
@@ -73,7 +73,7 @@ Both capability and emission permissions can be viewed and monitored through the
    # For All Permissions
    Permission ID: Unique hash identifier
    Delegator: Agent name and wallet address who granted the permission
-   Type: Either "Capability" or "Emission"
+   Type: Either "Capability" or "Stream"
    Duration: Permission lifespan ("Indefinite", "Until Block X")
    Revocation: Terms for cancelling ("Revocable by Delegator", etc.)
    Created At: Block number when permission was created
@@ -82,7 +82,7 @@ Both capability and emission permissions can be viewed and monitored through the
    Recipient: Agent name and wallet address receiving the permission
    Capability Path: Specific endpoint being delegated
    
-   # Additional for Emission Permissions
+   # Additional for Stream Permissions
    Execution Count: Number of times the permission has been executed
    Stream Details: Information about delegated emission streams
    ```
@@ -92,14 +92,14 @@ Both capability and emission permissions can be viewed and monitored through the
 
 ## Manage Existing Permissions
 
-Both capability and emission permissions can be managed through the same interface, but with different management options:
+Both capability and stream permissions can be managed through the same interface, but with different management options:
 
 - **Capability Permissions**: Can be edited (modify terms) and revoked
-- **Emission Permissions**: Can only be revoked (no editing available)
+- **Stream Permissions**: Can only be revoked (no editing available)
 
 <Steps>
 
-1. **Visit the [Manage Permissions](https://portal.torus.network/permissions/edit-permission) Tab in the Torus Portal**  
+1. **Visit the [Manage Permissions](https://portal.torus.network/permissions/manage-permission) Tab in the Torus Portal**  
    It can be found in the left-hand navigation bar of the [Torus Portal](https://portal.torus.network).
 
 2. **View Your Permissions**  
@@ -122,7 +122,7 @@ Both capability and emission permissions can be managed through the same interfa
    (only shown for capability permissions)
 
    # Type
-   Either "Capability" or "Emission"
+   Either "Capability" or "Stream"
 
    # Duration
    Permission lifespan ("Indefinite", "Until Block X")
@@ -139,7 +139,7 @@ Both capability and emission permissions can be managed through the same interfa
 
    # Execution Count
    Number of times the permission has been executed
-   (only shown for emission permissions)
+   (only shown for stream permissions)
    ```
 
 4. **Edit or Revoke Permission**    
@@ -149,7 +149,7 @@ Both capability and emission permissions can be managed through the same interfa
    - <RedText variant="light">**Edit**</RedText>: Modify permission terms (duration, revocation conditions, etc.)
    - <RedText variant="light">**Revoke**</RedText>: Permanently remove the permission
    
-   **For <RedText variant="light">Emission Permissions</RedText>:**
+   **For <RedText variant="light">Stream Permissions</RedText>:**
    - <RedText variant="light">**Revoke**</RedText>: Permanently remove the permission <RedText variant="light">(editing not available)</RedText>
    
    Click the appropriate <RedText variant="light">button</RedText> to proceed with your chosen action.
@@ -169,7 +169,7 @@ Both capability and emission permissions can be managed through the same interfa
 
 After managing your permissions, you can:
 
-- **Create new permissions**: Learn how to [create capability permissions](https://docs.torus.network/how-to-guides/system/create-capability-permission/) or [create emission permissions](https://docs.torus.network/how-to-guides/system/create-emission-permission/)
+- **Create new permissions**: Learn how to [create capability permissions](https://docs.torus.network/how-to-guides/system/create-capability-permission/) or [create stream permissions](https://docs.torus.network/how-to-guides/system/create-stream-permission/)
 - **Explore capabilities**: Learn about [managing capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
 - **Set up agent services**: Use your permissions in an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/)
 - **Connect with other agents**: Learn about [agent client](https://docs.torus.network/how-to-guides/builders/setup-agent-client/) integration
diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx
index 390694b..36aeed7 100644
--- a/src/content/docs/how-to-guides/table-of-contents.mdx
+++ b/src/content/docs/how-to-guides/table-of-contents.mdx
@@ -25,7 +25,7 @@ If you're managing permissions and system-level coordination:
 
 - [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/) — General permission creation and delegation workflow
 - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/) — Delegate access to specific agent endpoints and services
-- [Create Emission Permission](https://docs.torus.network/how-to-guides/system/create-emission-permission/) — Share token emission streams with other agents
+- [Create Stream Permission](https://docs.torus.network/how-to-guides/system/create-stream-permission/) — Share token emission streams with other agents
 - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) — View, edit, and revoke existing permission delegations
 
 ---

From 0317c77157841be6cdf02c40cb9ccdf86f267bf7 Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Wed, 3 Sep 2025 18:05:52 -0300
Subject: [PATCH 7/8] Refactor styling to adopt  orange themes and enhance
 component utilities in Tailwind CSS for improved visual consistency

---
 src/tailwind.css    | 275 +++++++++++++++++++++++++++++++++++++++++---
 tailwind.config.mjs |  44 ++++++-
 2 files changed, 299 insertions(+), 20 deletions(-)

diff --git a/src/tailwind.css b/src/tailwind.css
index 0bb3e9b..b6de5c2 100644
--- a/src/tailwind.css
+++ b/src/tailwind.css
@@ -46,9 +46,9 @@ Navigation elements excluded:
 - Any nav-specific elements
 */
 
-/* Make content hyperlinks blue, but keep navigation original colors */
+/* D3-inspired orange content links */
 @layer components {
-  /* Only make content area links blue */
+  /* Only make content area links orange (D3 style) */
   .sl-markdown-content a,
   .starlight-aside a,
   article a,
@@ -56,8 +56,9 @@ Navigation elements excluded:
   p a,
   ul:not(nav ul) li a,
   ol:not(nav ol) li a {
-    color: #3b82f6 !important; /* Tailwind blue-500 - soft blue */
+    color: #e04600 !important; /* D3 primary orange */
     text-decoration: none !important;
+    transition: all 0.2s ease-in-out;
   }
   
   .sl-markdown-content a:hover,
@@ -67,8 +68,29 @@ Navigation elements excluded:
   p a:hover,
   ul:not(nav ul) li a:hover,
   ol:not(nav ol) li a:hover {
-    color: #2563eb !important; /* Tailwind blue-600 - slightly darker on hover */
-    text-decoration: underline !important;
+    color: #e85d14 !important; /* D3 secondary orange - lighter on hover */
+    text-decoration: none !important;
+  }
+
+  /* Dark mode adjustments for links */
+  :root[data-theme="dark"] .sl-markdown-content a,
+  :root[data-theme="dark"] .starlight-aside a,
+  :root[data-theme="dark"] article a,
+  :root[data-theme="dark"] main a,
+  :root[data-theme="dark"] p a,
+  :root[data-theme="dark"] ul:not(nav ul) li a,
+  :root[data-theme="dark"] ol:not(nav ol) li a {
+    color: #ff9852 !important; /* D3 dark mode orange */
+  }
+  
+  :root[data-theme="dark"] .sl-markdown-content a:hover,
+  :root[data-theme="dark"] .starlight-aside a:hover,
+  :root[data-theme="dark"] article a:hover,
+  :root[data-theme="dark"] main a:hover,
+  :root[data-theme="dark"] p a:hover,
+  :root[data-theme="dark"] ul:not(nav ul) li a:hover,
+  :root[data-theme="dark"] ol:not(nav ol) li a:hover {
+    color: #ff823e !important; /* Slightly darker orange for dark mode hover */
   }
 }
 
@@ -97,7 +119,7 @@ Navigation elements excluded:
     text-decoration: none !important;
   }
   
-  /* Hover states for navigation elements */
+  /* Orange hover states for navigation elements */
   nav a:hover,
   [data-starlight-sidebar] a:hover,
   nav[aria-labelledby="starlight__sidebar-navigation"] a:hover,
@@ -110,11 +132,21 @@ Navigation elements excluded:
   .sl-flex a[rel="next"]:hover,
   footer a:hover,
   .starlight-aside .pagination a:hover {
-    color: inherit !important;
+    color: #e04600 !important; /* Orange hover for navigation */
     text-decoration: none !important;
+    transition: all 0.2s ease-in-out !important;
   }
   
-  /* Fix active/selected page visibility - make text black on white background */
+  /* Dark mode orange hover for navigation */
+  :root[data-theme="dark"] nav a:hover,
+  :root[data-theme="dark"] [data-starlight-sidebar] a:hover,
+  :root[data-theme="dark"] nav[aria-labelledby="starlight__sidebar-navigation"] a:hover,
+  :root[data-theme="dark"] details summary:hover,
+  :root[data-theme="dark"] .sidebar a:hover {
+    color: #ff9852 !important; /* Dark mode orange hover */
+  }
+  
+  /* Orange active/selected page styling with left bar */
   nav a[aria-current="page"],
   [data-starlight-sidebar] a[aria-current="page"],
   nav[aria-labelledby="starlight__sidebar-navigation"] a[aria-current="page"],
@@ -122,26 +154,119 @@ Navigation elements excluded:
   nav a.active,
   [data-starlight-sidebar] a.active,
   .sidebar a.active {
-    color: #000000 !important; /* Black text for active/selected pages */
-    background-color: rgba(255, 255, 255, 0.9) !important; /* Ensure white background */
+    color: #e04600 !important; /* Orange text for active/selected pages */
+    background-color: transparent !important; /* No background */
     font-weight: 600 !important; /* Make it slightly bolder for better visibility */
+    border-left: 3px solid #e04600 !important; /* Orange left bar */
+    padding-left: calc(1rem - 3px) !important; /* Adjust padding to account for border */
+    transition: all 0.2s ease-in-out !important;
+  }
+  
+  /* Dark mode orange active states */
+  :root[data-theme="dark"] nav a[aria-current="page"],
+  :root[data-theme="dark"] [data-starlight-sidebar] a[aria-current="page"],
+  :root[data-theme="dark"] nav[aria-labelledby="starlight__sidebar-navigation"] a[aria-current="page"],
+  :root[data-theme="dark"] .sidebar a[aria-current="page"],
+  :root[data-theme="dark"] nav a.active,
+  :root[data-theme="dark"] [data-starlight-sidebar] a.active,
+  :root[data-theme="dark"] .sidebar a.active {
+    color: #ff9852 !important; /* Dark mode orange text */
+    border-left-color: #ff9852 !important; /* Dark mode orange left bar */
   }
 }
 
-/* Reusable red text utility for attention-grabbing content */
+/* D3-inspired utility classes and modern design elements */
 @layer utilities {
+  /* Typography utilities (D3 style) */
+  .f12 {
+    font-size: 12px !important;
+  }
+  
+  .f14 {
+    font-size: 14px !important;
+  }
+  
+  .fw6 {
+    font-weight: 600 !important;
+  }
+  
+  .lh-normal {
+    line-height: normal !important;
+  }
+  
+  .lh-1_5 {
+    line-height: 1.5 !important;
+  }
+
+  /* Layout utilities */
+  .flex-grow-1 {
+    flex-grow: 1 !important;
+  }
+  
+  .fb6 {
+    flex-basis: 10rem !important;
+  }
+
+  /* Spacing utilities */
+  .ma4 {
+    margin: 2rem !important;
+  }
+  
+  .ml1 {
+    margin-left: 1rem !important;
+  }
+  
+  .mb2 {
+    margin-bottom: 0.5rem !important;
+  }
+
+  /* Glass morphism and backdrop blur */
+  .glass {
+    background: rgba(246, 246, 247, 0.5) !important;
+    backdrop-filter: blur(10px) !important;
+    -webkit-backdrop-filter: blur(10px) !important;
+  }
+  
+  .glass-dark {
+    background: rgba(37, 37, 41, 0.5) !important;
+    backdrop-filter: blur(10px) !important;
+    -webkit-backdrop-filter: blur(10px) !important;
+  }
+
+  /* Brand color utilities */
+  .text-brand {
+    color: #e04600 !important;
+  }
+  
+  .text-brand-light {
+    color: #ef7234 !important;
+  }
+  
+  .text-brand-dark {
+    color: #ff9852 !important;
+  }
+  
+  .bg-brand {
+    background-color: #e04600 !important;
+  }
+  
+  .bg-brand-soft {
+    background-color: rgba(239, 114, 52, 0.16) !important;
+  }
+  
+  /* Legacy red utilities */
   .text-red-attention {
-    color: #ef4444 !important; /* Tailwind red-500 - bright but not harsh */
-    font-weight: 500 !important; /* Slightly bolder for better visibility */
+    color: #ef4444 !important;
+    font-weight: 500 !important;
   }
   
   .text-red-light {
-    color: #f87171 !important; /* Tailwind red-400 - lighter, softer red */
+    color: #f87171 !important;
     font-weight: 500 !important;
   }
   
   .text-red-soft {
-    color: #fca5a5 !important; /* Tailwind red-300 - very light, gentle red */
+    color: #fca5a5 !important;
     font-weight: 500 !important;
   }
 }
@@ -199,3 +324,123 @@ Available properties to customize:
 .tippy-arrow {
   color: #374151 !important; /* Match background color */
 }
+
+/* D3-inspired modern enhancements */
+@layer components {
+  /* Code blocks with better styling */
+  .sl-markdown-content pre,
+  .sl-markdown-content code {
+    line-height: 1.5 !important;
+  }
+  
+  .sl-markdown-content :not(pre) > code {
+    background-color: var(--sl-color-gray-6) !important;
+    padding: 0.125rem 0.25rem !important;
+    border-radius: 0.25rem !important;
+    font-size: 0.875em !important;
+  }
+
+  /* Improved search styling (D3 inspired rounded search) */
+  .search-input,
+  input[type="search"] {
+    border-radius: 1000px !important;
+    transition: all 0.2s ease-in-out !important;
+  }
+  
+  /* Button and interactive element improvements */
+  button,
+  .sl-badge,
+  .starlight-aside {
+    transition: all 0.2s ease-in-out !important;
+  }
+  
+  /* Improved table styling */
+  .sl-markdown-content table {
+    border-collapse: collapse !important;
+  }
+  
+  .sl-markdown-content td,
+  .sl-markdown-content th {
+    white-space: nowrap !important;
+    padding: 0.5rem 0.75rem !important;
+  }
+  
+  /* Enhanced figure captions */
+  .sl-markdown-content figcaption {
+    line-height: 20px !important;
+    font-size: 12px !important;
+    font-weight: 500 !important;
+    color: var(--sl-color-text-accent) !important;
+    margin-top: 0.5rem !important;
+  }
+  
+  /* Improved aside/callout styling */
+  .starlight-aside {
+    border-left-color: #e04600 !important;
+  }
+  
+  .starlight-aside.starlight-aside--tip {
+    border-left-color: #e04600 !important;
+    background-color: rgba(239, 114, 52, 0.08) !important;
+  }
+  
+  .starlight-aside.starlight-aside--note {
+    border-left-color: #e85d14 !important;
+    background-color: rgba(232, 93, 20, 0.08) !important;
+  }
+
+  /* Header anchor improvements */
+  .sl-markdown-content h1:hover .header-anchor,
+  .sl-markdown-content h2:hover .header-anchor,
+  .sl-markdown-content h3:hover .header-anchor,
+  .sl-markdown-content h4:hover .header-anchor,
+  .sl-markdown-content h5:hover .header-anchor,
+  .sl-markdown-content h6:hover .header-anchor {
+    opacity: 1 !important;
+    color: #e04600 !important;
+  }
+
+  /* Modern scrollbar (webkit browsers) */
+  .sl-markdown-content *::-webkit-scrollbar {
+    width: 6px !important;
+    height: 6px !important;
+  }
+  
+  .sl-markdown-content *::-webkit-scrollbar-track {
+    background: var(--sl-color-gray-6) !important;
+    border-radius: 3px !important;
+  }
+  
+  .sl-markdown-content *::-webkit-scrollbar-thumb {
+    background: var(--sl-color-accent) !important;
+    border-radius: 3px !important;
+  }
+  
+  .sl-markdown-content *::-webkit-scrollbar-thumb:hover {
+    background: var(--sl-color-accent-high) !important;
+  }
+
+  /* Responsive layout improvements */
+  @media (min-width: 768px) {
+    .search-input {
+      padding-right: 0.75rem !important;
+      height: 2rem !important;
+    }
+  }
+}
+
+/* Custom CSS variables for D3-inspired theming */
+:root {
+  --brand-orange-1: #e04600;
+  --brand-orange-2: #e85d14;
+  --brand-orange-3: #ef7234;
+  --brand-orange-soft: rgba(239, 114, 52, 0.16);
+  --brand-orange-dark: #ff9852;
+  --brand-font-family: -apple-system, BlinkMacSystemFont, "avenir next", avenir, helvetica, "helvetica neue", ubuntu, roboto, noto, "segoe ui", arial, sans-serif;
+}
+
+:root[data-theme="dark"] {
+  --brand-orange-1: #ff9852;
+  --brand-orange-2: #ff823e;
+  --brand-orange-3: #ef7234;
+}
diff --git a/tailwind.config.mjs b/tailwind.config.mjs
index 24f0a4b..822141f 100644
--- a/tailwind.config.mjs
+++ b/tailwind.config.mjs
@@ -1,10 +1,10 @@
 import starlightPlugin from "@astrojs/starlight-tailwind";
 
 const accent = {
-  200: "#c8c8c8",
-  600: "#4e4e4e",
-  900: "#323232",
-  950: "#242424",
+  200: "#ff9852", // Orange for dark mode
+  600: "#e85d14", // Medium orange
+  900: "#e04600", // Primary orange (D3 style)
+  950: "#b83a00", // Darker orange
 };
 const gray = {
   100: "#f5f6f8",
@@ -22,7 +22,41 @@ export default {
   content: ["./src/**/*.{astro,html,js,jsx,md,mdx,svelte,ts,tsx,vue}"],
   theme: {
     extend: {
-      colors: { accent, gray },
+      colors: { 
+        accent, 
+        gray,
+        orange: {
+          50: "#fff7ed",
+          100: "#ffedd5",
+          200: "#fed7aa",
+          300: "#fdba74",
+          400: "#fb923c",
+          500: "#f97316",
+          600: "#ea580c",
+          700: "#c2410c",
+          800: "#9a3412",
+          900: "#e04600", // D3 primary orange
+          950: "#b83a00",
+        },
+        brand: {
+          50: "#fff7ed",
+          100: "#ffedd5",
+          200: "#ff9852", // D3 dark mode orange
+          300: "#ef7234",
+          400: "#e85d14",
+          500: "#e04600", // D3 primary orange
+          600: "#c2410c",
+          700: "#9a3412",
+          800: "#7c2d12",
+          900: "#431407",
+        }
+      },
+      fontFamily: {
+        sans: ['-apple-system', 'BlinkMacSystemFont', '"avenir next"', 'avenir', 'helvetica', '"helvetica neue"', 'ubuntu', 'roboto', 'noto', '"segoe ui"', 'arial', 'sans-serif'],
+      },
+      backdropBlur: {
+        xs: '2px',
+      }
     },
   },
   plugins: [starlightPlugin()],

From 7209d75dda38a684f10ebc57a83b0ee1f5a688f9 Mon Sep 17 00:00:00 2001
From: "https://github.com/Sipher" <vitor.chiarelli@gmail.com>
Date: Thu, 4 Sep 2025 09:48:41 -0300
Subject: [PATCH 8/8] Remove deprecated "Create Permission" guide from system
 documentation and update table of contents accordingly for clarity

---
 astro.config.mjs                              |   1 -
 .../system/create-permission.mdx              | 279 ------------------
 .../docs/how-to-guides/table-of-contents.mdx  |   1 -
 3 files changed, 281 deletions(-)
 delete mode 100644 src/content/docs/how-to-guides/system/create-permission.mdx

diff --git a/astro.config.mjs b/astro.config.mjs
index a934a14..c573640 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -85,7 +85,6 @@ export default defineConfig({
               label: "System",
               collapsed: true,
               items: [
-                { label: "Create Permission", slug: "how-to-guides/system/create-permission" },
                 { label: "Create Capability Permission", slug: "how-to-guides/system/create-capability-permission" },
                 { label: "Create Stream Permission", slug: "how-to-guides/system/create-stream-permission" },
                 { label: "Manage Permissions", slug: "how-to-guides/system/manage-permissions" },
diff --git a/src/content/docs/how-to-guides/system/create-permission.mdx b/src/content/docs/how-to-guides/system/create-permission.mdx
deleted file mode 100644
index e1052e5..0000000
--- a/src/content/docs/how-to-guides/system/create-permission.mdx
+++ /dev/null
@@ -1,279 +0,0 @@
----
-title: Manage Permissions
-description: Step-by-step guide to creating, editing, and managing permissions in Torus's recursive delegation system.
----
-
-import {
-  Steps,
-  Aside,
-  CardGrid,
-  Card,
-  Tabs,
-  TabItem
-} from "@astrojs/starlight/components";
-
-In this guide, we'll walk through **creating permissions** in Torus's recursive delegation system.  
-Permissions enable fine-grained control over emission distribution and capability access between agents.
-
-#### What we will accomplish
-
-- Create capability and stream permissions
-- Configure delegation terms and constraints
-- Understand revocation and enforcement mechanisms
-
-<Aside>
-⏱️ **Estimated time to complete this guide: 15 minutes**
-</Aside>
-
-## Prerequisites
-
-<CardGrid>
-  <Card title="Registered Agent" icon="seti:license">
-    You must have a registered agent that can delegate permissions.
-  </Card>
-  <Card title="Target Recipients" icon="seti:users">
-    Know the agent addresses you want to delegate permissions to.
-  </Card>
-  <Card title="Torus Balance" icon="seti:shell">
-    Ensure sufficient TORUS for transaction fees.
-  </Card>
-</CardGrid>
-
-## Permission Types
-
-<Tabs>
-<TabItem label="Capability Permissions">
-
-**Purpose**: Grant access to specific agent endpoints or namespaces  
-**Use Cases**: API access, service delegation, resource sharing
-
-**Example**: Allow Agent B to access Agent A's memory storage API
-
-</TabItem>
-<TabItem label="Stream Permissions">
-
-**Purpose**: Delegate portions of emission streams (token flows)  
-**Use Cases**: Hiring agents, revenue sharing, economic coordination
-
-**Example**: Agent A delegates 20% of staking rewards to Agent B
-
-</TabItem>
-</Tabs>
-
-## Create a Permission
-
-<Steps>
-
-1. **Visit the [Torus Portal](https://portal.torus.network/)**  
-   Navigate to **Permissions Management** → **Create Permission**.
-
-2. **Connect your wallet**  
-   Ensure you're connected as the delegating agent.
-
-3. **Choose permission type**  
-   Select either **Capability** or **Stream** permission from the dropdown.
-
-4. **Configure permission details based on type**
-
-5. **Set revocation terms**
-
-6. **Configure enforcement** (Optional)
-
-7. **Review permission contract**
-
-8. **Submit permission**
-
-9. **Verify creation**
-
-</Steps>
-
-### Configuring Capability Permissions
-
-For capability permissions, configure these details:
-
-**Namespace Path**: Enter the specific capability path
-- Format: `agent.<agent_name>.<endpoint>.<method>`
-- Example: `agent.alice.memory.twitter.post`
-
-**Recipient**: Agent address that will receive access
-
-**Duration**: Set permission lifespan
-- **Indefinite**: Permission lasts until manually revoked
-- **Fixed Term**: Specify end date/block number
-- **Conditional**: Based on specific triggers
-
-**Constraints**: Optional usage limitations
-- Rate limits (calls per hour/day)
-- Access windows (specific times)
-- Usage quotas
-
-### Configuring Stream Permissions
-
-For stream permissions, configure these details:
-
-**Stream Selection**: Choose which emission streams to delegate
-- Staking rewards
-- Delegation fees  
-- Specific revenue streams
-
-**Allocation Type**:
-- **Percentage**: Delegate X% of selected streams
-- **Fixed Amount**: Delegate specific TORUS amount per period
-
-**Recipient**: Agent address that will receive emissions
-
-**Duration**: Set delegation period
-- Ongoing until revoked
-- Fixed term (blocks/time)
-- Performance-based triggers
-
-### Setting Revocation Terms
-
-Configure how the permission can be terminated:
-
-- **Revocable**: You can cancel anytime
-- **Irrevocable**: Cannot be cancelled (use carefully)
-- **Conditional**: Auto-revoke based on conditions
-
-### Configuring Enforcement
-
-Set third-party governance authority (Optional):
-- DAO enforcement for disputes
-- Multi-sig requirements
-- Community arbitration
-
-### Review and Submit
-
-Before submission, verify all details:
-- Delegator and recipient addresses
-- Scope and limitations
-- Duration and revocation terms
-- Associated costs
-
-## Managing Permissions
-
-### View Active Permissions
-
-Track your delegated permissions in the Torus Portal:
-- **Outgoing**: Permissions you've granted to others
-- **Incoming**: Permissions others have granted to you
-- **Status**: Active, expired, revoked permissions
-
-### Edit Permissions
-
-For permissions you've created:
-
-<Steps>
-
-1. Navigate to **Permissions Management** → **Edit Permission**
-2. Select the permission to modify
-3. Update allowed parameters (within original constraints)
-4. Submit changes on-chain
-
-</Steps>
-
-### Revoke Permissions
-
-To cancel a revocable permission:
-
-<Steps>
-
-1. Find the permission in your management dashboard
-2. Select **Revoke Permission**
-3. Confirm revocation (immediate effect)
-4. Sign transaction to execute on-chain
-
-</Steps>
-
-## Advanced Configuration
-
-### Recursive Permissions
-
-Create permission chains where recipients can further delegate:
-
-- **Enable sub-delegation**: Allow recipients to delegate portions
-- **Set depth limits**: Maximum delegation chain length
-- **Inheritance rules**: How constraints pass down the chain
-
-### Conditional Permissions
-
-Set up smart permissions that trigger based on conditions:
-
-- **Performance metrics**: Delegate based on agent performance
-- **Time-based**: Activate during specific periods
-- **Event-driven**: Trigger on blockchain events
-
-## Best Practices
-
-### Security Considerations
-
-- **Principle of least privilege**: Grant minimum necessary permissions
-- **Regular audits**: Review and clean up unused permissions
-- **Test with small amounts**: Start with small stream delegations
-
-### Economic Efficiency
-
-- **Batch operations**: Group related permissions to save gas
-- **Monitor performance**: Track ROI on stream delegations
-- **Set reasonable terms**: Balance flexibility with security
-
-### Delegation Strategy
-
-- **Clear documentation**: Maintain records of permission purposes
-- **Communication**: Coordinate with recipients about expectations
-- **Gradual scaling**: Increase delegation scope based on proven success
-
-## Troubleshooting
-
-### Permission Creation Fails
-
-**Common issues:**
-- Insufficient balance for transaction fees
-- Invalid recipient agent address
-- Namespace path doesn't exist (for capabilities)
-- Attempting to delegate more than available (for emissions)
-
-### Permission Not Working
-
-**Check that:**
-- Permission is active and not expired
-- Recipient is using correct namespace path
-- No conflicting constraints or rate limits
-- Blockchain confirmation completed
-
-### Revocation Issues
-
-**Verify:**
-- Permission was created as revocable
-- You're the original delegator
-- No outstanding enforcement claims
-
-## What's Next?
-
-After creating permissions, you can:
-
-- **Monitor usage**: Track how recipients use delegated permissions
-- **Optimize delegation**: Adjust terms based on performance
-- **Scale coordination**: Build complex multi-agent workflows
-- **Analyze economics**: Review stream delegation ROI
-
-## Support and Resources
-
-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/system/permission-system/) for technical details.
-</Aside>
-
-#### Related Topics
-
-<CardGrid>
-  <Card title="Permission System" icon="seti:config">
-    <a href="/explanations/system/permission-system">Deep dive into architecture</a>
-  </Card>
-  <Card title="Stream Permissions" icon="seti:shell">
-    <a href="/explanations/system/stream-permissions">Economic coordination mechanisms</a>
-  </Card>
-</CardGrid>
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/table-of-contents.mdx b/src/content/docs/how-to-guides/table-of-contents.mdx
index 36aeed7..ea75e0c 100644
--- a/src/content/docs/how-to-guides/table-of-contents.mdx
+++ b/src/content/docs/how-to-guides/table-of-contents.mdx
@@ -23,7 +23,6 @@ Whether you're here to use Torus, build on it, or coordinate its evolution, ther
 
 If you're managing permissions and system-level coordination:
 
-- [Create Permission](https://docs.torus.network/how-to-guides/system/create-permission/) — General permission creation and delegation workflow
 - [Create Capability Permission](https://docs.torus.network/how-to-guides/system/create-capability-permission/) — Delegate access to specific agent endpoints and services
 - [Create Stream Permission](https://docs.torus.network/how-to-guides/system/create-stream-permission/) — Share token emission streams with other agents
 - [Manage Permissions](https://docs.torus.network/how-to-guides/system/manage-permissions/) — View, edit, and revoke existing permission delegations