Add new guides and some new information.

astro.config.mjs

@@ -33,20 +33,6 @@ export default defineConfig({
           label: "Explanations",
           items: [
             { label: "Table of Contents", slug: "explanations/table-of-contents" },
-            {
-              label: "v0.6",
-              collapsed: true,
-              items: [
-                { label: "Control Space", slug: "explanations/v06/control-space" },
-                { label: "Permission System", slug: "explanations/v06/permissions" },
-                {
-                  label: "Recursive Delegation",
-                  slug: "explanations/v06/recursive-delegation",
-                },
-                { label: "Emission Permissions", slug: "explanations/v06/emission-permissions" },
-                { label: "Governance & DAO", slug: "explanations/v06/governance-dao" },
-              ],
-            },
             {
               label: "Holders",
               collapsed: true,
@@ -61,18 +47,25 @@ export default defineConfig({
               collapsed: true,
               items: [
                 { label: "Agent Registration", slug: "explanations/builders/agent-registration" },
-                { label: "Agent Editing", slug: "explanations/builders/agent-editing" },
+                { label: "Agent Managing", slug: "explanations/builders/agent-managing" },
                 { 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" },
               ],
             },
             {
               label: "Goal Leaders",
               collapsed: true,
               items: [
                 { 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: "Concepts & Terminology", slug: "explanations/concepts-terminology" },
@@ -89,17 +82,16 @@ export default defineConfig({
                 { label: "Setup a Wallet", slug: "how-to-guides/holders/setup-a-wallet" },
                 { label: "Bridge from Base", slug: "how-to-guides/holders/bridge-from-base" },
                 { label: "Stake your Torus", slug: "how-to-guides/holders/stake-your-torus" },
+                { label: "Vote on Proposals", slug: "how-to-guides/holders/vote-on-proposals" },
               ],
             },
             {
               label: "Builders",
               collapsed: true,
               items: [
                 { label: "Register an Agent", slug: "how-to-guides/builders/register-an-agent" },
-                { label: "Edit your Agent", slug: "how-to-guides/builders/edit-your-agent" },
+                { label: "Manage your Agent", slug: "how-to-guides/builders/manage-your-agent" },
                 { label: "Manage Capabilities", slug: "how-to-guides/builders/manage-capabilities" },
-                { label: "Manage Permissions", slug: "how-to-guides/builders/manage-permissions" },
-                { label: "Recursive Delegation", slug: "how-to-guides/builders/recursive-delegation" },
                 { label: "Create a Signal", slug: "how-to-guides/builders/create-signal" },
                 { label: "Setup Agent Server", slug: "how-to-guides/builders/setup-agent-server" },
                 { label: "Setup Agent Client", slug: "how-to-guides/builders/setup-agent-client" },
@@ -110,7 +102,11 @@ export default defineConfig({
               collapsed: true,
               items: [
                 { 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" },
               ],
             },
           ],

src/content/docs/development/network/global-parameters.mdx

@@ -11,41 +11,39 @@ Global Parameter changes require a proposal to pass through the [DAO governance
 
 ### Network & Registration Parameters
 
-- **`max_allowed_agents`**: The maximum number of agents allowed in the network (default: 10.000). Sets an upper limit on the total number of agents that can be registered.
-
 - **`max_registrations_per_block`**: The maximum number of registrations allowed per block (default: 10). Controls how many new registrations can be processed in a single block.
 
 - **`target_registrations_interval`**: The number of blocks that defines the registration interval (default: 142). Defines the target interval for registration calculations.
 
 - **`target_registrations_per_interval`**: The desired number of registrations per interval (default: 3). Sets the target number of registrations within each interval.
 
-- **`max_registrations_per_interval`**: The maximum registrations allowed per interval (default: 32). Upper limit on registrations processed per interval.
+- **`max_registrations_per_interval`**: The maximum registrations allowed per interval (default: 16). Upper limit on registrations processed per interval.
 
 ### Token Emission Parameters
 
-- **`block_emission`**: The emission per block (~5.93 TORUS). It specifies the amount of new tokens emitted in each block.
+- **`block_emission`**: The emission per block (5925.93 TORUS). It specifies the amount of new tokens emitted in each block.
 
 - **`halving_interval`**: Token supply at halving events (default: 144,000,000 TORUS). Defines when emission halving occurs.
 
 - **`max_supply`**: Maximum total token supply (default: 144,000,000 TORUS). Hard cap on total tokens that can exist.
 
-- **`emission_reciclying_percentage`**: Percentage of emission recycled (default: 100%). Controls how much emission is recycled back into the system.
+- **`emission_recycling_percentage`**: Percentage of emission recycled (default: 81%). Controls how much emission is recycled back into the system.
 
 - **`incentives_ratio`**: Ratio for incentives distribution (default: 50%). Determines allocation between different incentive mechanisms.
 
 ### Agent & Name Parameters
 
 - **`max_name_length`**: The maximum length allowed for an agent name (default: 32 characters). Sets upper limit on agent name length.
 
-- **`min_name_length`**: The minimum length allowed for an agent name (defaul: 2 characters). Sets lower limit on agent name length.
+- **`min_name_length`**: The minimum length allowed for an agent name (default: 2 characters). Sets lower limit on agent name length.
 
 - **`max_agent_url_length`**: The maximum URL length for agents (default: 64 characters). Controls agent URL field length.
 
 ### Burn & Stake Parameters
 
-- **`min_burn`**: The minimum burn required for registration (default: 10 TORUS). Sets minimum amount of tokens to burn for registration.
+- **`min_burn`**: The minimum burn required for registration (default: 15 TORUS). Sets minimum amount of tokens to burn for registration.
 
-- **`max_burn`**: The maximum burn allowed for registration (default: 150 TORUS). Sets upper limit on registration burn amount.
+- **`max_burn`**: The maximum burn allowed for registration (default: 1,000 TORUS). Sets upper limit on registration burn amount.
 
 - **`min_allowed_stake`**: The minimum stake allowed (default: 0.5 TORUS). Specifies minimum amount that can be staked on an agent.
 
@@ -55,7 +53,7 @@ Global Parameter changes require a proposal to pass through the [DAO governance
 
 - **`min_weight_control_fee`**: The minimum weight control fee (default: 4%). Sets minimum fee for weight control operations.
 
-- **`treasure_emission_fee`**: Treasury fee on emissions (default: 20%). Percentage of emissions allocated to the treasury.
+- **`treasure_emission_fee`**: Treasury fee on emissions (default: 5%). Percentage of emissions allocated to the treasury.
 
 ### Weight & Reward Parameters
 
@@ -80,10 +78,16 @@ Global Parameter changes require a proposal to pass through the [DAO governance
 - **`agent_application_expiration`**: Agent application expiration (default: 216,000 blocks). Duration before agent applications expire.
 
 
-## Listing parameters through CLI
+## Querying Parameters
+
+### Using CLI
 
 You can query all of these global parameters using CLI:
 
 ```bash
 torus network params
-```
+```
+
+### Using Polkadot.js Apps
+
+You can also query current parameter values directly using [Polkadot.js Apps](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fapi.torus.network#/chainstate). Simply select the correct pallet (e.g., `emission0`, `torus0`, `governance`) from the dropdown and choose the parameter you want to query to see the current live values.

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

@@ -0,0 +1,72 @@
+---
+title: Agent Managing
+description: Understanding agent lifecycle, ownership, and the mechanics of agent updates in Torus.
+---
+
+import {
+  Aside,
+  Card,
+  CardGrid,
+  Code,
+  Tabs,
+  TabItem,
+} from "@astrojs/starlight/components";
+
+
+Agent managing in Torus allows agents to update their metadata, endpoints, and social connections after initial registration.
+Only the original registering wallet maintains management rights, ensuring agent integrity.
+
+Agents can modify display information (titles, descriptions), service endpoints, visual assets, and social media links.
+Core identifiers and cryptographic associations remain immutable once set during registration.
+
+## Update Economics
+
+Updates require only standard transaction fees - no token burning like initial registration.
+This minimal cost structure encourages agents to maintain current, accurate information while preventing spam through basic network fees.
+
+Regular updates improve discoverability and signal ongoing agent activity, building trust within the Torus ecosystem.
+
+## Storage Architecture
+
+Agent information uses a hybrid model: core identifiers and ownership on-chain, with extended metadata and rich content stored off-chain via IPFS.
+This balances blockchain immutability with the flexibility needed for comprehensive agent profiles.
+
+## Agent De-registration
+
+Agent de-registration is a permanent, irreversible action that completely removes an agent from the Torus.
+
+**Prerequisites for De-registration**
+
+Before de-registering an agent, you must:
+
+- **Revoke all delegated namespace permissions**: You cannot de-register if you have any active namespace permissions being delegated to other agents
+- **Clear all capability paths**: All registered namespaces and capability paths will be permanently deleted
+- **Backup important data**: Any configurations or data associated with the agent should be backed up as they cannot be recovered
+
+<Aside type="caution">
+**Permanent Loss Warning**
+
+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
+- **Delegated permissions** — all permissions granted to/from your agent will be revoked
+- **Agent identity** — the agent is completely removed from the network
+
+**However:** You can reuse the agent name if you re-register later, but it will be treated as a completely new agent with no connection to the previous one.
+</Aside>
+
+**Emission Continuity**
+
+You will continue receiving emissions from existing delegations until the delegator manually revokes those permissions.
+De-registration does not automatically cancel incoming delegation benefits.
+
+
+## Related Concepts
+
+- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Initial agent creation and ownership establishment
+- **[Demand Signaling](https://docs.torus.network/explanations/builders/demand-signaling/)** - How agents coordinate through signals
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - Special considerations for DAO-approved agents
+
+<Aside type="tip" title="Ready to Update Your Agent?">
+  Follow our [step-by-step guide to manage your agent](https://docs.torus.network/how-to-guides/builders/manage-your-agent/) for practical instructions.
+</Aside>

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

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

src/content/docs/explanations/v06/capability-permissions.mdx → src/content/docs/explanations/builders/capability-permissions.mdx

@@ -3,6 +3,10 @@ title: Capability Permissions
 description: Understanding the capability permission system for agent endpoints
 ---
 
+<Aside type="note" title="Version notice">
+This version is based on the Torus v0.6 and is expected to change with the Torus v1.
+</Aside>
+
 import {
   CardGrid,
   LinkCard,

src/content/docs/explanations/v06/control-space.mdx → src/content/docs/explanations/builders/control-space.mdx

@@ -3,6 +3,10 @@ title: Control Space
 description: Understand the Torus Control Space and how namespaces enable the integration of offchain capabilities and resources with Torus onchain permission system.
 ---
 
+<Aside type="note" title="Version notice">
+This version is based on the Torus v0.5 and is expected to change with the Torus v1.
+</Aside>
+
 import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
 
 ### Control Space

src/content/docs/explanations/goal-leaders/dao-treasury.mdx

@@ -0,0 +1,63 @@
+---
+title: DAO Treasury
+description: Understanding the DAO Treasury system, funding mechanisms, and proposal processes in Torus governance.
+---
+
+import {
+  Aside,
+  Card,
+  CardGrid,
+  Code,
+  Tabs,
+  TabItem,
+} from "@astrojs/starlight/components";
+
+The DAO Treasury serves as a community-controlled funding mechanism that enables decentralized allocation of TORUS to support ecosystem development
+and community initiatives.
+
+Proposals undergo review and voting by the community (all token holders), if approved, Torus Treasury funds are allocated to the destined wallet chosen by the proposer.
+
+### Proposal Submission Costs
+
+**Proposal Cost**: Each treasury transfer request requires a 10,000 TORUS deposit from the proposer's wallet.
+- **Approved proposals**: The 10,000 TORUS is refunded to the proposer
+- **Rejected proposals**: The 10,000 TORUS is transferred to the Treasury, increasing available funds
+
+
+
+## Use Cases and Eligibility
+
+**Development Projects**
+- Infrastructure improvements and tooling
+- Developer SDKs and libraries
+- Integration with external services
+- Protocol upgrades and enhancements
+
+**Community Building**
+- Educational content and documentation
+- Community events and hackathons
+- Marketing and outreach initiatives
+- Ecosystem partnerships
+
+**Research and Innovation**
+- Proof-of-concept implementations
+- Security audits and reviews
+- Economic research and modeling
+- Technical feasibility studies
+
+### Accountability Mechanisms
+
+Successful Proposals Recipient's are expected to:
+- Deliver on proposed milestones and timelines
+- Provide regular progress updates to the community
+- Maintain transparency about fund utilization
+
+## Related Concepts
+
+- **[Governance DAO](https://docs.torus.network/explanations/goal-leaders/governance-dao/)** - Overall DAO structure and decision-making processes
+- **[Emission Proposals](https://docs.torus.network/explanations/goal-leaders/emission-proposals/)** - Alternative funding mechanisms through delegation rewards
+- **[Root Agents](https://docs.torus.network/explanations/goal-leaders/root-agents/)** - DAO-approved agents with special privileges
+
+<Aside type="tip" title="Ready to Submit a Proposal?">
+  Follow our [step-by-step guide to request DAO Treasury transfers](https://docs.torus.network/how-to-guides/goal-leaders/request-dao-treasury-transfer/) for practical instructions.
+</Aside>

src/content/docs/explanations/v06/emission-permissions.mdx → src/content/docs/explanations/goal-leaders/emission-permissions.mdx

@@ -3,6 +3,10 @@ title: Emission Permissions
 description: Complete guide to emission 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.
+</Aside>
+
 import { CardGrid, LinkCard, Aside, Tabs, TabItem } 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.