diff --git a/astro.config.mjs b/astro.config.mjs
index dfe311b..cc35bf9 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -25,12 +25,10 @@ export default defineConfig({
{
label: "Getting Started",
items: [
- { label: "Introduction", slug: "index" },
- { label: "Tokenomics", slug: "concepts/tokenomics" },
- {
- label: "Concepts & Terminology",
- slug: "getting-started/concepts",
- },
+ { label: "Welcome", slug: "index" },
+ { label: "Tokenomics", slug: "getting-started/tokenomics" },
+ { label: "Concepts & Terminology", slug: "getting-started/concepts-terminology" },
+ { label: "Understanding Torus", slug: "getting-started/concepts" },
],
},
{
@@ -40,14 +38,14 @@ export default defineConfig({
{
label: "v0.5",
items: [
- { label: "Control Space", slug: "v05/control-space" },
- { label: "Permission System", slug: "v05/permissions" },
+ { label: "Control Space", slug: "explanations/v05/control-space" },
+ { label: "Permission System", slug: "explanations/v05/permissions" },
{
label: "Capability Permissions",
- slug: "v05/capability-permissions",
+ slug: "explanations/v05/capability-permissions",
},
- { label: "Emission Permissions", slug: "v05/emission-permissions" },
- { label: "Governance & DAO", slug: "concepts/governance-dao" },
+ { label: "Emission Permissions", slug: "explanations/v05/emission-permissions" },
+ { label: "Governance & DAO", slug: "explanations/v05/governance-dao" },
],
},
{
@@ -55,14 +53,14 @@ export default defineConfig({
collapsed: false,
items: [
{ label: "Agent Registration", slug: "explanations/builders/agent-registration" },
- { label: "Agent Server", slug: "explanations/builders/agent-server" },
- { label: "Agent Client", slug: "explanations/builders/agent-client" },
{ label: "Agent Editing", slug: "explanations/builders/agent-editing" },
{ 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: "Leaders",
+ label: "Goal Leaders",
collapsed: false,
items: [
{ label: "Root Agents", slug: "explanations/root-agents/root-agents" },
@@ -78,19 +76,21 @@ export default defineConfig({
label: "Holders",
collapsed: false,
items: [
- { label: "Setup a Wallet", slug: "how-to-guides/participants/setup-a-wallet" },
- { label: "Bridge from Base", slug: "how-to-guides/participants/bridge-from-base" },
- { label: "Stake your Torus", slug: "how-to-guides/participants/stake-your-torus" },
+ { 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: "Builders",
collapsed: false,
items: [
- { label: "Setup CLI", slug: "how-to-guides/builders/setup-cli" },
{ 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 Capabilities", slug: "how-to-guides/builders/manage-capabilities" },
{ label: "Create a Signal", slug: "how-to-guides/builders/create-signal" },
+ // { label: "Manage Permissions", slug: "how-to-guides/builders/manage-permissions" },
+ // { label: "Delegate Emission Streams", slug: "how-to-guides/builders/delegate-emission-streams" },
{ label: "Setup Agent Server", slug: "how-to-guides/builders/setup-agent-server" },
{ label: "Setup Agent Client", slug: "how-to-guides/builders/setup-agent-client" },
],
@@ -104,33 +104,40 @@ export default defineConfig({
},
],
},
- {
- label: "CLI & Tools",
- items: [
- { label: "Key Management", slug: "cli/key-management" },
- { label: "Balance Operations", slug: "cli/balance-operations" },
- ],
- },
{
label: "Development",
items: [
+ { label: "Start Here", slug: "development/start-here" },
{
- label: "Web Apps Overview and Setup",
- slug: "development/web-apps-overview-and-setup",
+ label: "Web Apps",
+ collapsed: false,
+ items: [
+ {
+ label: "Overview and Setup",
+ slug: "development/web/overview-and-setup",
+ },
+ {
+ label: "Querying Data",
+ slug: "development/web/querying-data",
+ },
+ ],
},
{
- label: "Querying Data",
- slug: "development/querying-data",
+ label: "CLI Reference",
+ collapsed: false,
+ items: [
+ { label: "Setup CLI", slug: "development/cli/setup-cli" },
+ { label: "Key Management", slug: "development/cli/key-management" },
+ { label: "Balance Operations", slug: "development/cli/balance-operations" },
+ ],
},
- ],
- },
- {
- label: "Network Operations",
- items: [
- { label: "Global Parameters", slug: "network/global-parameters" },
{
- label: "Running a Node",
- slug: "network/running-node",
+ label: "Network Operations",
+ collapsed: false,
+ items: [
+ { label: "Global Parameters", slug: "development/network/global-parameters" },
+ { label: "Running a Node", slug: "development/network/running-node" },
+ ],
},
],
},
diff --git a/public/images/how-to-guide/manage-capabilities/create-capability-confirm-information.png b/public/images/how-to-guide/manage-capabilities/create-capability-confirm-information.png
new file mode 100644
index 0000000..8754c3d
Binary files /dev/null and b/public/images/how-to-guide/manage-capabilities/create-capability-confirm-information.png differ
diff --git a/public/images/how-to-guide/manage-capabilities/delete-capability-confirm-information.png b/public/images/how-to-guide/manage-capabilities/delete-capability-confirm-information.png
new file mode 100644
index 0000000..8b8d66d
Binary files /dev/null and b/public/images/how-to-guide/manage-capabilities/delete-capability-confirm-information.png differ
diff --git a/src/components/RedText.astro b/src/components/RedText.astro
new file mode 100644
index 0000000..55282b6
--- /dev/null
+++ b/src/components/RedText.astro
@@ -0,0 +1,18 @@
+---
+export interface Props {
+ variant?: 'attention' | 'light' | 'soft';
+ class?: string;
+}
+
+const { variant = 'light', class: className = '' } = Astro.props;
+
+const variantClasses = {
+ attention: 'text-red-attention',
+ light: 'text-red-light',
+ soft: 'text-red-soft'
+};
+
+const redClass = variantClasses[variant];
+---
+
+
\ No newline at end of file
diff --git a/src/content/docs/concepts/agents.mdx b/src/content/docs/concepts/agents.mdx
deleted file mode 100644
index 6d28f40..0000000
--- a/src/content/docs/concepts/agents.mdx
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: What are Agents
-description: Learn what an agent is in Torus.
----
-
-import { CardGrid, LinkCard } from "@astrojs/starlight/components";
-
-Agents are the same primitive in the blockchain but differ in their offchain role.
-Both are registered keys, paired with an offchain object, able to receive weights by the allocator, determining their share in the emissions.
-
-This primitive separates all computation from the chain and allows agents to be arbitrarily complex and computationally expensive.
-
-**Agents are entities, either autonomous or human, that perform actions that align with Torus interests.**
-
-
-
-
-
diff --git a/src/content/docs/concepts/network-overview.mdx b/src/content/docs/concepts/network-overview.mdx
deleted file mode 100644
index a2066ac..0000000
--- a/src/content/docs/concepts/network-overview.mdx
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: Mainnet Concepts & Terminology
-description: Learn the basic concepts and terminology of Torus.
----
-
-import {
- CardGrid,
- LinkCard,
- Aside,
- Steps,
-} from "@astrojs/starlight/components";
-
-
-### Network
-The network consists of a dynamic set of registered agents competing to attract incentive from the allocator to earn TORUS. Incentives are weight-based, representing share in the continuous emission distribution.
-
-### Agent
-
-An agent is a key registered to the network, paired with an off-chain entity, either autonomous or human, that performs actions that align with Torus interests.
-
-### Allocator
-
-The allocator is a permissionless web platform maintained by _Renlabs_, enabling stakeholders to allocate incentive weights among agents. Users delegate TORUS to the allocator key, setting weights with their stake through the platform to receive dividends.
-
-### Curator
-
-The curator serves as the regulatory entity of the network, overseeing the agent and incentive landscape to ensure alignment with protocol interests. The curator has two primary permissions:
-
-
-
-1. **Managing the Agent Whitelist:** Approving agents to join the network and removing those that become misaligned.
-
-2. **Applying Penalty Factors:** Issuing penalties on agents that scale both the agent's incentives and the dividends of users who set weights on them. This mechanism helps correct and penalize over-incentivization, leveraging common sense to detect misalignment.
-
-
-
-The curator's decision-making system operates off-chain and is adaptable, functioning as an agent, a DAO or a trusted community member.
-
-Multiple specialized curators can operate in parallel, each permissioned by the root curator. The root curator can itself be replaced by the Torus DAO at any time.
-
-### Torus DAO
-
-The Torus DAO is a fully on-chain, TORUS stake-based governance system, managing the protocol through community proposals. It can modify network parameters, dynamically adjust emission rate, and allocate resources between the network and treasury to align with TORUS interests.
-
-### Torus treasury
-
-The treasury is a DAO-owned key that accumulates emissions and receives transfers. Treasury funds are managed via DAO proposals to support ecosystem initiatives.
-
-### Weights
-
-Weights provide an expressive format for granularly representing the relative value of agents within the network, guiding the distribution of incentives. For example, an agent with a weight of 0.01 holds a 1% share of the total incentives being continuously distributed.
-
-
-
-
-
diff --git a/src/content/docs/cli/balance-operations.mdx b/src/content/docs/development/cli/balance-operations.mdx
similarity index 95%
rename from src/content/docs/cli/balance-operations.mdx
rename to src/content/docs/development/cli/balance-operations.mdx
index 8119f21..04b4752 100644
--- a/src/content/docs/cli/balance-operations.mdx
+++ b/src/content/docs/development/cli/balance-operations.mdx
@@ -43,4 +43,4 @@ The unstaking command is defined as follows:
torus balance unstake
```
-You can also specify the name of the key, if it's located on your disk. Same as in transferring or staking.
+You can also specify the name of the key, if it's located on your disk. Same as in transferring or staking.
\ No newline at end of file
diff --git a/src/content/docs/cli/key-management.mdx b/src/content/docs/development/cli/key-management.mdx
similarity index 94%
rename from src/content/docs/cli/key-management.mdx
rename to src/content/docs/development/cli/key-management.mdx
index bb11326..86de96a 100644
--- a/src/content/docs/cli/key-management.mdx
+++ b/src/content/docs/development/cli/key-management.mdx
@@ -45,7 +45,7 @@ This command displays both public and private key details, ensuring you have acc
To list all keys stored on your system, execute:
```sh
-# Lists the names and addresses of keys stored on disk.
+# Lists the names and addresses of keys stored on disk.
torus key list
```
@@ -69,4 +69,4 @@ You can also sort the balance by **all, free, staked** (default all summed balan
torus key balances --sort-balance free
```
-Will return the keys sorted by their free balance.
+Will return the keys sorted by their free balance.
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/setup-cli.mdx b/src/content/docs/development/cli/setup-cli.mdx
similarity index 85%
rename from src/content/docs/how-to-guides/builders/setup-cli.mdx
rename to src/content/docs/development/cli/setup-cli.mdx
index 4d76c12..f039236 100644
--- a/src/content/docs/how-to-guides/builders/setup-cli.mdx
+++ b/src/content/docs/development/cli/setup-cli.mdx
@@ -110,8 +110,6 @@ The CLI enables developers and power users to manage Torus operations from the c
-{/*
-
## Basic CLI Usage
Now that you have the CLI installed, here are the main command categories:
@@ -139,10 +137,10 @@ torus misc circulating-supply # Total supply info
Now that you have the CLI set up, you can:
-- **Register an agent**: Use [agent registration](https://docs.torus.network/how-to-guides/builders/register-an-agent/) to create your first agent
-- **Manage keys**: Learn about [key management](https://docs.torus.network/cli/key-management/) for secure operations
-- **Check balances**: Use [balance operations](https://docs.torus.network/cli/balance-operations/) to monitor your tokens
-- **Build integrations**: Set up [agent servers](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) for programmatic interactions
+- **Register an agent**: Use [agent registration](/how-to-guides/builders/register-an-agent/) to create your first agent
+- **Manage keys**: Learn about [key management](/development/cli/key-management/) for secure operations
+- **Check balances**: Use [balance operations](/development/cli/balance-operations/) to monitor your tokens
+- **Build integrations**: Set up [agent servers](/how-to-guides/builders/setup-agent-server/) for programmatic interactions
Connect with the community:
- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
@@ -155,9 +153,9 @@ Now that you have the CLI set up, you can:
- Learn to create and manage your keys
+ Learn to create and manage your keys
- Transfer tokens and manage staking
+ Transfer tokens and manage staking
- */}
\ No newline at end of file
+
\ No newline at end of file
diff --git a/src/content/docs/network/global-parameters.mdx b/src/content/docs/development/network/global-parameters.mdx
similarity index 99%
rename from src/content/docs/network/global-parameters.mdx
rename to src/content/docs/development/network/global-parameters.mdx
index 623e3d4..64a08af 100644
--- a/src/content/docs/network/global-parameters.mdx
+++ b/src/content/docs/development/network/global-parameters.mdx
@@ -86,4 +86,4 @@ You can query all of these global parameters using CLI:
```bash
torus network params
-```
+```
\ No newline at end of file
diff --git a/src/content/docs/network/running-node.mdx b/src/content/docs/development/network/running-node.mdx
similarity index 98%
rename from src/content/docs/network/running-node.mdx
rename to src/content/docs/development/network/running-node.mdx
index d43fa18..fcab94c 100644
--- a/src/content/docs/network/running-node.mdx
+++ b/src/content/docs/development/network/running-node.mdx
@@ -85,4 +85,4 @@ cargo xtask run local --alice
## Additional Information
-- You can customize your node's configuration by modifying the appropriate files in the project.
+- You can customize your node's configuration by modifying the appropriate files in the project.
\ No newline at end of file
diff --git a/src/content/docs/development/start-here.mdx b/src/content/docs/development/start-here.mdx
new file mode 100644
index 0000000..28929a7
--- /dev/null
+++ b/src/content/docs/development/start-here.mdx
@@ -0,0 +1,60 @@
+---
+title: Start Here
+description: Technical documentation and tools for developing with and on Torus.
+---
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card,
+ Tabs,
+ TabItem
+} from "@astrojs/starlight/components";
+
+Welcome to the **Development** section of the Torus documentation.
+
+This section provides comprehensive technical resources for developers building with Torus — from setting up development environments to running nodes and managing keys.
+Whether you're integrating with existing web apps, querying data, or running your own infrastructure, you'll find the technical details here.
+
+## Web Application Development
+
+Building and integrating with the Torus ecosystem:
+
+- [Overview and Setup](https://docs.torus.network/development/web/overview-and-setup/) — Setting up the development environment and understanding the monorepo structure
+- [Querying Data](https://docs.torus.network/development/web/querying-data/) — API operations for retrieving stake allocation and network data
+
+---
+
+## CLI & Tools
+
+Command-line operations for key and balance management:
+
+- [Key Management](https://docs.torus.network/development/cli/key-management/) — Creating, importing, and managing cryptographic keys
+- [Balance Operations](https://docs.torus.network/development/cli/balance-operations/) — Transferring and staking operations via CLI
+
+---
+
+## Network Infrastructure
+
+Running and configuring Torus network infrastructure:
+
+- [Global Parameters](https://docs.torus.network/development/network/global-parameters/) — Understanding and configuring blockchain parameters
+- [Running a Node](https://docs.torus.network/development/network/running-node/) — Setting up and operating a Torus Substrate node
+
+---
+
+## Questions Not Covered Here?
+
+Need help with development tasks? The community is here to help:
+
+- **[Discord](https://discord.gg/torus)** — Technical discussions, support, and announcements
+- **[Telegram](https://t.me/torusnetwork)** — General chat and announcements
+- **[Twitter](https://x.com/torus_network)** — Updates and ecosystem news
+
+### Core Projects
+
+Explore the open source code to understand implementation details:
+
+- **[torus-substrate](https://github.com/renlabs-dev/torus-substrate)** — Core blockchain runtime built on Substrate
+- **[torus-ts](https://github.com/renlabs-dev/torus-ts)** — TypeScript SDK for building on Torus and WebApps
+- **[torus-docs](https://github.com/renlabs-dev/torus-docs)** — This documentation
\ No newline at end of file
diff --git a/src/content/docs/development/web-apps-install-and-run(old).mdx b/src/content/docs/development/web-apps-install-and-run(old).mdx
deleted file mode 100644
index 8c3af0b..0000000
--- a/src/content/docs/development/web-apps-install-and-run(old).mdx
+++ /dev/null
@@ -1,148 +0,0 @@
----
-title: Web Apps Install and Run
-description: Learn how to install and run the torus-ts
----
-
-import {
- Badge,
- Steps,
- Tabs,
- TabItem,
- Aside,
-} from "@astrojs/starlight/components";
-
-This guide will walk you through the process of installing and running the `torus-ts` monorepo.
-
-## Prerequisites
-
-- **Node.js** - `20.16.0` or higher.
-- **PNPM** - `9.7.1` or higher.
-- **Docker** - [installation guide](https://docs.docker.com/get-docker/).
-- **Just** - [installation guide](https://github.com/casey/just).
-
-##### Docker Tip
-
-If you have difficulties or want alternatives to simplify using Docker, consider:
-
-- [Colima](https://github.com/abiosoft/colima): A lightweight solution for running containers on macOS.
-- [Orbstack](https://orbstack.dev/): A fast and efficient alternative for managing containers.
-
-## Monorepo setup
-
-
-
-
-
-1. ##### Clone the repository
-
-
-
- ```bash git clone git@github.com:renlabs-dev/torus-ts.git ``` Clone
- using the web URL.
-
-
- ```bash https://github.com/renlabs-dev/torus-ts.git ``` Use a
- password-protected SSH key.
-
-
- ```bash gh repo clone renlabs-dev/torus-ts ``` Use the [GitHub
- CLI](https://cli.github.com/).
-
-
-
-
-
-2. ##### Install the dependencies
-
- ```bash
- pnpm install
- # or
- just install
- ```
-
-
-
-3. ##### Configure environment variables
-
- There is an `.env.example` in the root directory you can use for reference
-
- ```bash
- cp .env.example .env
- ```
-
-
-
-4. ##### Setup database
-
-
- This step is only required for the **`torus-allocator`** & **`torus-dao`**
- apps.
-
-
- Create a postgres container with docker:
-
- ```bash
- docker run --name torus-db-container \
- -e POSTGRES_PASSWORD=password \
- -e POSTGRES_DB=torus-ts-db \
- -e POSTGRES_USER=postgres \
- -p 1337:1337 \
- -d postgres:16-alpine \
- postgres -p 1337
- ```
-
- Push the Drizzle schema to the database:
-
- ```bash
- just db-push
- ```
-
- You can also use the `just db-studio` command to open a GUI provided by [Drizzle](https://orm.drizzle.team/drizzle-studio/overview).
-
-
-
-5. ##### Build the project
-
- ```bash
- just build
- ```
-
-
- This step is required before running any app since **`@torus-ts/subspace`** needs to be builded and imported indirectly, otherwise dependant packages may typecheck it's sources and cause conflict in the generated/augmented types.
-
-
-
-
-6. ##### Run the project
-
- From the root directory, run the following command:
-
- ```bash
- just dev
- ```
-
-
- The `app-name` is the name of the app you want to run. You can find the
- list of apps in the `packages` directory. For example, to run the
- `torus-allocator` app, you would run `just dev torus-allocator`.
-
-
- From the app directory, run the following command:
-
- ```bash
- pnpm run dev
- ```
-
-
- To run apps from their directories, you need to set up the environment
- variables inside the app directory aswell.
-
-
-
-
-
- If you desire to contribute, please follow the `DISCUSSION_TEMPLATE` and
- `ISSUE_TEMPLATE` in the `.github` folder.
-
-
-
diff --git a/src/content/docs/development/web-apps-overview(old).mdx b/src/content/docs/development/web-apps-overview(old).mdx
deleted file mode 100644
index d5a2046..0000000
--- a/src/content/docs/development/web-apps-overview(old).mdx
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Introduction
-description: Learn how to build into Torus typescript ecosystem
----
-
-import { LinkCard, Aside } from "@astrojs/starlight/components";
-
-These docs will guide you through the process of building / integrating with Torus web apps. We provide a set of tools and libraries to help you build and contribute to the Torus ecosystem.
-
-The ecosystem is built using a monorepo with [Turborepo](https://turbo.build/repo/docs), which allows us to share code and tools across different projects.
-
-## Web Apps
-
-
-
-
-
-
-
-
-
- To access enviroments pointing to the testnet nodes, add the `.testnet`
- subdomain to the URL, eg. `https://allocator.testnet.torus.network/`
-
diff --git a/src/content/docs/development/web-apps-overview-and-setup.mdx b/src/content/docs/development/web/overview-and-setup.mdx
similarity index 97%
rename from src/content/docs/development/web-apps-overview-and-setup.mdx
rename to src/content/docs/development/web/overview-and-setup.mdx
index 131b745..41e1700 100644
--- a/src/content/docs/development/web-apps-overview-and-setup.mdx
+++ b/src/content/docs/development/web/overview-and-setup.mdx
@@ -18,7 +18,7 @@ The ecosystem is built using a monorepo with [Turborepo](https://turbo.build/rep
To access environments pointing to the testnet nodes, add the `.testnet`
- subdomain to the URL, eg. `https://allocator.testnet.torus.network/`
+ subdomain to the URL, eg. `https://portal.testnet.torus.network/root-allocator`
## Prerequisites
@@ -53,7 +53,7 @@ For detailed setup instructions, see the setup guide below.
Some environment variables required by the `torus-ts` monorepo are sensitive
- and cannot be shared publicly. You’ll need to configure them manually using
+ and cannot be shared publicly. You'll need to configure them manually using
the provided `.env.example` file as a reference.
diff --git a/src/content/docs/development/querying-data.mdx b/src/content/docs/development/web/querying-data.mdx
similarity index 77%
rename from src/content/docs/development/querying-data.mdx
rename to src/content/docs/development/web/querying-data.mdx
index 362ef0b..0d51fd8 100644
--- a/src/content/docs/development/querying-data.mdx
+++ b/src/content/docs/development/web/querying-data.mdx
@@ -6,7 +6,7 @@ description: Learn how to query the stake weight between keys
import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
Our API allows you to retrieve information about the stake allocation between keys and agents.
-You can query this data by making a GET request to: `https://allocator.torus.network/api/allocated-weight`.
+You can query this data by making a GET request to: `https://portal.torus.network/api/allocated-weight`.
## API Response Format
@@ -29,14 +29,14 @@ The API response has the following structure:
To filter the response for a specific allocating key, append the userKey query parameter to the API endpoint:
- ```allocator.torus.network/api/allocated-weight?userKey=```
+ ```portal.torus.network/api/allocated-weight?userKey=```
- Filter by Agent Key
To filter the response for specific agents, append the agentKey query parameter to the API endpoint:
- ```allocator.torus.network/api/allocated-weight?agentKey=```
+ ```portal.torus.network/api/allocated-weight?agentKey=```
Replace `` with the desired allocating key address.
-
+
\ No newline at end of file
diff --git a/src/content/docs/explanations/builders/agent-registration.mdx b/src/content/docs/explanations/builders/agent-registration.mdx
index cb789cb..937d708 100644
--- a/src/content/docs/explanations/builders/agent-registration.mdx
+++ b/src/content/docs/explanations/builders/agent-registration.mdx
@@ -17,6 +17,14 @@ import {
Agent registration in Torus creates discoverable entities that can receive, create, and delegate permissions within the network.
Registration is immediate with no approval required, but involves burning tokens to prevent spam.
+
+**Agent Names are Immutable**
+
+Once an agent is registered, its name becomes a permanent identifier that cannot be modified.
+This design ensures consistency in the permission system and prevents identity confusion in capability delegation.
+ Choose agent names thoughtfully.
+
+
### Registration Economics
Agent registration requires permanently burning tokens:
@@ -30,15 +38,15 @@ The burn mechanism maintains network quality by creating economic barriers to sp
### Discovery and Capabilities
-Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator page](https://allocator.torus.network/).
+Registered agents become discoverable through the public agent registry and can be viewed on the [Allocator tab](https://portal.torus.network/root-allocator).
They can participate in the permission system, create named capabilities for other agents to invoke, and engage in governance proposals.
Agent metadata is stored off-chain via IPFS but referenced on-chain through content hashes.
### Related Concepts
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents that receive emissions directly
-- **[Permission System](https://docs.torus.network/v05/permissions/)** - How agents interact and delegate authority
-- **[Governance & DAO](https://docs.torus.network/concepts/governance-dao/)** - Understanding DAO decision-making processes
+- **[Permission System](https://docs.torus.network/explanations/v05/permissions/)** - How agents interact and delegate authority
+- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding DAO decision-making processes
Follow our [step-by-step registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) to register your agent.
diff --git a/src/content/docs/explanations/builders/demand-signaling.mdx b/src/content/docs/explanations/builders/demand-signaling.mdx
index 0671ef1..5525a7f 100644
--- a/src/content/docs/explanations/builders/demand-signaling.mdx
+++ b/src/content/docs/explanations/builders/demand-signaling.mdx
@@ -35,7 +35,7 @@ If you are using a different schema, fully specify it.
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - How agents become discoverable
- **[Root Agents](https://docs.torus.network/explanations/root-agents/root-agents/)** - Agents with direct emission access
- **[Agent Server Setup](https://docs.torus.network/explanations/builders/agent-server/)** - Recommended endpoint interface examples
-- **[Tokenomics](https://docs.torus.network/concepts/tokenomics/)** - Understanding emission mechanisms
+- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - Understanding emission mechanisms
Follow our [step-by-step guide to create a signal](https://docs.torus.network/how-to-guides/builders/create-signal/) to start signaling demand for capabilities.
diff --git a/src/content/docs/explanations/root-agents/root-agents.mdx b/src/content/docs/explanations/root-agents/root-agents.mdx
index 6012f88..49be043 100644
--- a/src/content/docs/explanations/root-agents/root-agents.mdx
+++ b/src/content/docs/explanations/root-agents/root-agents.mdx
@@ -31,8 +31,8 @@ Successful applicants demonstrate credible execution, active community participa
### Related Concepts
- **[Agent Registration](https://docs.torus.network/explanations/builders/agent-registration/)** - Technical details of agent registration
-- **[Governance & DAO](https://docs.torus.network/concepts/governance-dao/)** - Understanding DAO decision-making processes
-- **[Tokenomics](https://docs.torus.network/concepts/tokenomics/)** - How Root Agents access and use network emissions
+- **[Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/)** - Understanding DAO decision-making processes
+- **[Tokenomics](https://docs.torus.network/getting-started/tokenomics/)** - How Root Agents access and use network emissions
Follow our [step-by-step application guide](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/) to submit your Root Agent application.
diff --git a/src/content/docs/explanations/start-here.mdx b/src/content/docs/explanations/start-here.mdx
index 1da7a43..3211456 100644
--- a/src/content/docs/explanations/start-here.mdx
+++ b/src/content/docs/explanations/start-here.mdx
@@ -17,6 +17,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.
+## v0.5 Related Topics
+
+Understanding the technical implementation and design of Torus v0.5:
+
+- [Control Space](https://docs.torus.network/explanations/v05/control-space/) — Foundational permission and capability framework
+- [Permission System](https://docs.torus.network/explanations/v05/permissions/) — How agents interact and delegate authority
+- [Capability Permissions](https://docs.torus.network/explanations/v05/capability-permissions/) — Specific capability delegation mechanisms
+- [Emission Permissions](https://docs.torus.network/explanations/v05/emission-permissions/) — How emissions are allocated and controlled
+- [Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/) — Decision-making processes and community coordination
+
+---
+
## For Builders (Agents)
Understanding how agent systems work within Torus:
@@ -37,17 +49,6 @@ Understanding governance and leadership systems:
---
-## Torus Mechanics
-
-Understanding the core systems that power Torus:
-
-
-- [Control Space](https://docs.torus.network/v05/control-space/) — Foundational permission and capability framework
-- [Permission System](https://docs.torus.network/v05/permissions/) — How agents interact and delegate authority
-- [Governance & DAO](https://docs.torus.network/concepts/governance-dao/) — Decision-making processes and community coordination
-- [Tokenomics](https://docs.torus.network/concepts/tokenomics/) — Economic model and emission mechanics
-
----
## Questions Not Covered Here?
diff --git a/src/content/docs/v05/capability-permissions.mdx b/src/content/docs/explanations/v05/capability-permissions.mdx
similarity index 95%
rename from src/content/docs/v05/capability-permissions.mdx
rename to src/content/docs/explanations/v05/capability-permissions.mdx
index b24b152..926c5b0 100644
--- a/src/content/docs/v05/capability-permissions.mdx
+++ b/src/content/docs/explanations/v05/capability-permissions.mdx
@@ -329,21 +329,3 @@ bobAgent.method("process", {
- Test RPC endpoints are accessible
- Consider using multiple RPC URLs for redundancy
-
-
-
-
-
-
diff --git a/src/content/docs/v05/control-space.mdx b/src/content/docs/explanations/v05/control-space.mdx
similarity index 94%
rename from src/content/docs/v05/control-space.mdx
rename to src/content/docs/explanations/v05/control-space.mdx
index f1d5ef4..d19f4f4 100644
--- a/src/content/docs/v05/control-space.mdx
+++ b/src/content/docs/explanations/v05/control-space.mdx
@@ -47,12 +47,4 @@ Once established, the agent can use the permission delegation system for coopera
The true power of namespaces lies in their integration with the permission delegation system. Agents can granularly & recursively delegate access to specific controls derived from their namespaces, with flexible constraints.
-This enables sophisticated patterns: Alice might delegate time-bounded read access to `agent.alice.memory.twitter` while retaining write permissions, or establish multi-signature revocation requirements that involve third-party arbiters.
-
-
-
-
+This enables sophisticated patterns: Alice might delegate time-bounded read access to `agent.alice.memory.twitter` while retaining write permissions, or establish multi-signature revocation requirements that involve third-party arbiters.
\ No newline at end of file
diff --git a/src/content/docs/v05/emission-permissions.mdx b/src/content/docs/explanations/v05/emission-permissions.mdx
similarity index 91%
rename from src/content/docs/v05/emission-permissions.mdx
rename to src/content/docs/explanations/v05/emission-permissions.mdx
index f10f372..621de0f 100644
--- a/src/content/docs/v05/emission-permissions.mdx
+++ b/src/content/docs/explanations/v05/emission-permissions.mdx
@@ -117,22 +117,3 @@ The accumulation mechanism efficiently processes emissions through a multi-stage
3. **Percentage Extraction**: For stream allocations, the specified percentage is extracted
4. **Storage**: Accumulated amounts are stored with agent-stream-permission indexing
5. **Distribution Triggers**: Various conditions trigger automatic distribution
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/src/content/docs/concepts/governance-dao.mdx b/src/content/docs/explanations/v05/governance-dao.mdx
similarity index 89%
rename from src/content/docs/concepts/governance-dao.mdx
rename to src/content/docs/explanations/v05/governance-dao.mdx
index 8754c32..fd323b3 100644
--- a/src/content/docs/concepts/governance-dao.mdx
+++ b/src/content/docs/explanations/v05/governance-dao.mdx
@@ -1,13 +1,6 @@
---
-title: Torus DAO
+title: Governance & DAO
description: Learn about the governance and operation of the Torus DAO.
-
-prev:
- link: /concepts/tokenomics
- label: Tokenomics
-next:
- link: /agents/register-agent
- label: Register an Agent
---
import { Tabs, TabItem, Aside, LinkCard } from "@astrojs/starlight/components";
@@ -76,11 +69,4 @@ Proposals are the primary mechanism for implementing changes to the Torus protoc
-
-
-
-
+
\ No newline at end of file
diff --git a/src/content/docs/v05/permissions.mdx b/src/content/docs/explanations/v05/permissions.mdx
similarity index 84%
rename from src/content/docs/v05/permissions.mdx
rename to src/content/docs/explanations/v05/permissions.mdx
index f97f00e..83dd147 100644
--- a/src/content/docs/v05/permissions.mdx
+++ b/src/content/docs/explanations/v05/permissions.mdx
@@ -60,22 +60,4 @@ Each delegation level undergoes strict validation to ensure proper authorization
## Enforcement Authority System
-The enforcement system creates a sophisticated bridge between on-chain permissions and off-chain verification, allowing builders to create custom enforcement mechanisms.
-
-
-
-
-
-
+The enforcement system creates a sophisticated bridge between on-chain permissions and off-chain verification, allowing builders to create custom enforcement mechanisms.
\ No newline at end of file
diff --git a/src/content/docs/getting-started/concepts-terminology.mdx b/src/content/docs/getting-started/concepts-terminology.mdx
new file mode 100644
index 0000000..ea81f57
--- /dev/null
+++ b/src/content/docs/getting-started/concepts-terminology.mdx
@@ -0,0 +1,80 @@
+---
+title: Concepts & Terminology
+description: Key terms and concepts used throughout the Torus ecosystem
+---
+
+import { Aside } from "@astrojs/starlight/components";
+
+
+This glossary defines the key terms and concepts used throughout Torus documentation. Understanding these terms will help you navigate the ecosystem more effectively.
+
+## Core Concepts
+
+### Agent
+An autonomous entity in the Torus network that can perform actions, provide services, and participate in swarms. Agents can be registered users, automated services, or any entity capable of interacting with the protocol.
+
+### Swarm
+A coordinated group of agents working together toward a common goal. Swarms form organically around specific objectives and can operate at multiple scales within the network.
+
+### Hypergraph
+The emergent network structure formed by all agents, their relationships, permissions, and interactions. The hypergraph represents the complete state of coordination within Torus.
+
+### Root Agent
+A special type of agent with elevated permissions to receive emissions directly from the protocol and set goals for swarm formation. Root agents lead major initiatives and coordinate large-scale activities.
+
+## Permissions & Capabilities
+
+### Capability
+A specific function or service that an agent can provide to others. Capabilities are registered on-chain and define what an agent can do within the network.
+
+### Permission
+The right to use or delegate a specific capability. Permissions can be granted, revoked, and delegated between agents to enable complex coordination patterns.
+
+### Delegation
+The process of granting permission to use a capability to another agent. Delegation enables specialization and collaborative work within swarms.
+
+### Control Space
+The coordination layer where agents register capabilities, manage permissions, and coordinate activities. It serves as the control plane for the entire network.
+
+## Economic Terms
+
+### TORUS Token
+The native token of the Torus network used for staking, governance, and accessing network services.
+
+### Staking
+The process of locking TORUS tokens to participate in network security and earn rewards. Staked tokens can be allocated to support specific agents.
+
+### Emissions
+Token rewards distributed to agents and stakeholders based on their contributions to the network. Emissions flow from root agents to the broader ecosystem.
+
+### Allocation
+The distribution of staked tokens to support specific agents or initiatives. Allocations determine how emissions flow through the network.
+
+## Technical Terms
+
+### Agent Server
+A service that hosts agent capabilities and provides APIs for other agents to interact with. Agent servers make capabilities discoverable and usable across the network.
+
+### Agent Client
+A component that allows agents to discover and interact with capabilities provided by other agents. Clients handle authentication and communication protocols.
+
+### Signal
+A message broadcast by an agent expressing demand for specific capabilities or announcing the availability of services. Signals help coordinate supply and demand within swarms.
+
+### Substrate
+The blockchain framework that powers the Torus network. Substrate provides the runtime environment for the protocol's core functionality.
+
+## Governance Terms
+
+### DAO (Decentralized Autonomous Organization)
+The governance structure through which major protocol decisions are made. The Torus DAO enables stakeholder participation in network evolution.
+
+### Proposal
+A formal suggestion for protocol changes, new features, or resource allocation submitted to the DAO for consideration and voting.
+
+### Governance Token
+TORUS tokens used for voting on proposals and participating in decentralized governance processes.
+
+
+**New terms being added regularly.** As the Torus ecosystem evolves, new concepts and terminology emerge. Check back here for updates or suggest additions through our community channels.
+
diff --git a/src/content/docs/getting-started/concepts.mdx b/src/content/docs/getting-started/concepts.mdx
index 9ce8979..7fcf8e4 100644
--- a/src/content/docs/getting-started/concepts.mdx
+++ b/src/content/docs/getting-started/concepts.mdx
@@ -1,107 +1,31 @@
---
-title: High-level Concepts and Terminology
-description: In depth Torus concepts and terminology.
+title: Understanding Torus
+description: Layer1 self-assembling & self-optimizing autonomous super-swarm
---
-### Agent
+import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
-Registered key able to receive & delegate permissions over protocol & agent control space (on-chain / off-chain) and accumulate delegated incentive (coin emissions).
+# Layer1 self-assembling & self-optimizing autonomous super-swarm
----
-### Protocol control space
-
-A set of controls composed of all chain parameters and storages where corruption does not lead to loss of user holdings (e.g. weights, bonds).
-
----
-### Agent control space
-
-Off-chain control space local to agents with any structure, any set of controls. The permission delegation system of agent control space is fully local with arbitrary design.
-
----
-### Controls
-
-Atomic units of the control space
-
----
-### Permission
-
-Programmatically defined authority over a set of controls that can be either exercised or delegated, either partially or fully, optionally with an added constraint - recursively.
-
-permission-centric, there are 2 types of agents:
-
-* controller
-
-exercises the control authority of the permission, i.e. submitting extrinsics to the chain
-
-* selector
-
-dynamically delegates the permission to the best controlling agent
-
-agents can take both the controller and selector role for different parts of their permission sets.
-
-agent-centric, there are 2 types of permissions:
-
-* direct permissions
-
-require direct action to be delegated by an agent
-
-* conditional permissions
-
-require receiving agent to satisfy a condition set to automatically receive (and keep) the permission.
-
-When a permission is adapted or revoked, the change propagates down the delegation tree. When an incentive delegation is adapted, it propagates proportionally down the tree.
-
----
-### Permission constraint
-
-A programmatically defined constraint over the use of a permission, e.g. a limit on how often a permission can be re-delegated between agents or a set of conditions that have to be met by an agent to be re-delegated to, or a set of conditions that have to be met for the permission to be active. a condition could be state of offchain oracle.
-
----
-### Delegation
-
-Transfer of permissions or incentive between agents with programmatic logic, the edges of the graph.
-
----
-### Circular Delegation
-
-Circular delegation paths are allowed, but further re-delegation is blocked to avoid confusing paths. Higher level agents have permission to enforce irrevocable re-delegation to them, as an alternative to revoking a permission entirely such that the graph stays intact and can be immediately reverted back into.
-
-This is the standard, but can be partially or fully constraint in the permission constraint defined by the higher level agent.
-
----
-### Stake root
-
-Fully Stake-based permissionless control system and foundational authority and owner of the protocol control space, representing the root agent node of the Torus graph. Everything else is emergent from it through recursive delegation, and continuously aligns back to it. The most successful delegation tree over time should be the one most aligned and with the highest importance to the goals of stake.
+Torus is a stake-based p2p protocol for goal-driven agent swarm coordination.
+The system operates as one fractal super-swarm, which is composed of one emergent hypergraph of recursively delegated permissions and incentives among agents.
+ warms are subgraphs, and can form at any position in the hypergraph.
-The biological analogy for the stake root is the genome, where the genetic library is stored offchain in the evolving minds of the stakeholders and the Torus memeplex, continuously mutating, and the onchain stake-based control mechanism is the gene regulatory system, translating how the genetic library can express itself onto the Torus
+The Torus hypergraph emerges from and aligns back to the stake root, tethering the system to the interests of stake.
+ orus aligns towards the central point of stake, while stake is decentralized representing the system as a whole, effectively aligning it to itself.
----
-### Emissions
-
-Emissions are the continuous distribution of TORUS tokens to agents based on their utility and stake allocation. The emission system operates through distinct streams that preserve their identity through delegation chains, enabling complete traceability of token flow from source to recipients.
-
-Agents can delegate portions of their emissions to other agents through stream-based allocations (percentage-based) or fixed amount allocations, creating complex economic coordination structures. This enables recursive delegation where successful agents can redistribute incentives to supporting agents, aligning the entire network toward utility creation.
-
----
-### Namespace
-
-A namespace is a hierarchical naming system that enables agents to organize and delegate access to their capabilities and services. Using dot-separated paths (like `agent.alice.memory.twitter`), namespaces create clear authority boundaries while enabling granular permission delegation for off-chain services.
+Swarms form bottom-up around top-down goals, their formation happens organically without central planning.
+Swarms operate as self-assembling multi-scale competency architectures,
+ ollectively navigating towards complex goals with full autonomy at every level and open competition at every edge.
-Namespaces represent the *potential* for creating new controls, acting as genetic templates from which specific permissions can emerge. This distinction between namespace (potential) and control (actualized permission) enables the recursive delegation patterns that characterize complex agent coordination.
+The permission & delegation system enables agents to granularily specialize while remaining aligned across levels.
+Swarms collectively explore a problem space and engage in an open-ended process of recursive niche construction to navigate towards the swarms goal.
----
-### Torus graph
-
-Dynamic multi-graph, where the edges are delegated permissions and incentives, representing the protocols emergent self-organization.
-
----
-### Graph event flow
-The central flow of chain events changing the structure of the protocol graph, which can be observed by anyone.
-
----
-### Organs
-Organs are regions of the Torus graph, composed of emergent sets of agents that fulfill an emergent function of the Torus to increase its competency. E.g. memory, immune system, sense making, complexity pruning, propaganda. “Organ” is a useful term of an emergent construct, but not a primitive.
+#### v0.5
----
+The v0.5 is a pragmatic, growth oriented and limited implemention of the Torus conceptual model.
+it's mainnet release initiates the formation process of the Torus hypergraph and allows battletesting of our concepts.
+It is sufficient for the formation of sophisticated agent swarms and applies the core ideas.
+The Torus v1 will be the pure and complete implementation of the Torus conceptual model and will be delivered after undergoing a growth phase with the v0.5.
\ No newline at end of file
diff --git a/src/content/docs/concepts/tokenomics.mdx b/src/content/docs/getting-started/tokenomics.mdx
similarity index 88%
rename from src/content/docs/concepts/tokenomics.mdx
rename to src/content/docs/getting-started/tokenomics.mdx
index 2b7e495..5bfcc9a 100644
--- a/src/content/docs/concepts/tokenomics.mdx
+++ b/src/content/docs/getting-started/tokenomics.mdx
@@ -10,4 +10,4 @@ TORUS was fair launched with no pre-mine. 100% of emissions are openly competed
The initial TORUS supply consists entirely of bridged COMAI tokens, which were also launched with a fair distribution model and no pre-mine.
-
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/create-permission.mdx b/src/content/docs/how-to-guides/builders/create-permission.mdx
new file mode 100644
index 0000000..4cb57d5
--- /dev/null
+++ b/src/content/docs/how-to-guides/builders/create-permission.mdx
@@ -0,0 +1,276 @@
+---
+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
+
+
+⏱️ **Estimated time to complete this guide: 15 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a registered agent that can delegate permissions.
+
+
+ Know the agent addresses you want to delegate permissions to.
+
+
+ Ensure sufficient TORUS for transaction fees.
+
+
+
+## Permission Types
+
+
+
+
+**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
+
+
+
+
+**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
+
+
+
+
+## Create a Permission
+
+
+
+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**
+
+
+
+### Configuring Capability Permissions
+
+For capability permissions, configure these details:
+
+**Namespace Path**: Enter the specific capability path
+- Format: `agent...`
+- 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:
+
+
+
+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
+
+
+
+### Revoke Permissions
+
+To cancel a revocable permission:
+
+
+
+1. Find the permission in your management dashboard
+2. Select **Revoke Permission**
+3. Confirm revocation (immediate effect)
+4. Sign transaction to execute on-chain
+
+
+
+## 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)
+- [Permission System Documentation](https://docs.torus.network/explanations/v05/permissions/)
+
+#### Related Topics
+
+
+
+ Deep dive into architecture
+
+
+ Economic coordination mechanisms
+
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/create-signal.mdx b/src/content/docs/how-to-guides/builders/create-signal.mdx
index 67bde1a..ec2d595 100644
--- a/src/content/docs/how-to-guides/builders/create-signal.mdx
+++ b/src/content/docs/how-to-guides/builders/create-signal.mdx
@@ -9,6 +9,7 @@ import {
CardGrid,
Card
} from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
In this guide, we'll **create a demand signal** to express your need for specialized capabilities from other agents.
@@ -35,7 +36,7 @@ Signaling demand allows you to delegate part of your emissions to agents who can
Have incoming emission streams available to offer as incentive for capability providers.
- You can find a [guide on how to stake TORUS here](https://docs.torus.network/how-to-guides/participants/stake-your-torus/).
+ You can find a [guide on how to stake TORUS here](https://docs.torus.network/how-to-guides/holders/stake-your-torus/).
@@ -48,11 +49,11 @@ Signaling demand allows you to delegate part of your emissions to agents who can
2. **Connect your Torus wallet**
- Connect the wallet that owns the agent you want to signal from.
+ Connect the wallet that owns the agent you want to signal from.
-3. **Fill in the signal details:**
-
- Signals allow agents to express their demand for specialized capabilities in both technical and economic terms. Here's an **example** of what a signal might look like:
+3. **Fill in the signal details**
+ Signals allow agents to express their demand for specialized capabilities in both technical and economic terms.
+ Here's an example of what a signal could look like :
```
Title: Short, descriptive name for the capability you need
@@ -90,10 +91,10 @@ Signaling demand allows you to delegate part of your emissions to agents who can
4. **Review and publish the signal**
- Double-check your details and publish to make it discoverable.
+ Double-check your details and publish to make it discoverable .
5. **All Done**
- Your demand signal is now visible in the Torus graph and signal marketplace for other agents to discover.
+ Your demand signal is now visible in the Torus graph and [signal marketplace for other agents](https://portal.torus.network/signals/signal-list) to discover.
diff --git a/src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx b/src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx
new file mode 100644
index 0000000..5c6d71f
--- /dev/null
+++ b/src/content/docs/how-to-guides/builders/delegate-emission-streams.mdx
@@ -0,0 +1,357 @@
+---
+title: Delegate Emission Streams
+description: Configure emission permissions to delegate token flows and create economic coordination structures.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card,
+ Tabs,
+ TabItem
+} from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
+
+In this guide, we'll set up **emission permissions** to delegate portions of your token streams to other agents.
+This enables economic coordination, agent hiring, and revenue sharing structures.
+
+#### What we will accomplish
+
+- Delegate percentage-based emission streams
+- Set up fixed-amount allocations
+- Configure delegation terms and monitoring
+- Understand stream preservation and traceability
+
+
+⏱️ **Estimated time to complete this guide: 15 minutes**
+
+
+## Prerequisites
+
+
+
+ You must be receiving emission streams (from staking, delegation, or root agent status).
+
+
+ Know the agent addresses you want to delegate emissions to.
+
+
+ Sufficient TORUS for transaction fees.
+
+
+
+## Understanding Emission Streams
+
+Emission permissions work with **stream identity preservation**:
+
+- **StreamId**: Each emission source has a unique identifier
+- **Traceability**: Token flow is tracked from source to final recipients
+- **Delegation Chains**: Streams maintain identity through recursive delegations
+
+**Common Stream Types:**
+- Staking rewards from allocators
+- Delegation fees from sub-agents
+- Root agent emissions
+- Custom revenue streams
+
+## Delegation Types
+
+
+
+
+**Percentage-based delegation of specific streams**
+
+- Delegate 0-100% of particular streams
+- Safety constraints prevent over-allocation
+- Maintains stream identity through delegation
+- Ideal for performance-based compensation
+
+
+
+
+**Set TORUS amounts per time period**
+
+- Fixed payments regardless of stream performance
+- Useful for salary-like arrangements
+- Independent of underlying stream fluctuations
+- Predictable costs for budget planning
+
+
+
+
+## Delegate Emission Streams
+
+
+
+1. **Visit the [Torus Portal](https://portal.torus.network/)**
+ Navigate to **Permissions Management** → **Create Permission**.
+
+2. **Select Emission Permission**
+ Choose "Emission Permission" from the permission type dropdown.
+
+3. **Connect your wallet**
+ Ensure you're connected as the agent receiving emissions to delegate.
+
+4. **Configure delegation type**
+ Choose between stream-based or fixed amount delegation.
+
+5. **Set delegation terms**
+ Configure duration, recipient, and constraints.
+
+6. **Review delegation contract**
+ Verify all details before submitting.
+
+7. **Submit emission permission**
+ Sign the transaction to create the delegation on-chain.
+
+8. **Monitor delegation**
+ Track delegation status in the Portal dashboard.
+
+
+
+## Delegation Configuration
+
+
+
+
+### Stream-Based Delegation
+
+**Select Streams**: Choose which emission streams to delegate
+- View all your active streams with their StreamIds
+- See current flow rates and sources
+- Select specific streams for delegation
+
+**Set Percentages**: Define allocation per stream
+```
+Stream A (Staking): 25% → Agent Bob
+Stream B (Fees): 50% → Agent Charlie
+Stream C (Root): 10% → Agent Dave
+```
+
+**Safety Validation**: System ensures totals don't exceed 100% per stream
+
+
+
+
+### Fixed Amount Delegation
+
+**Amount**: Specify TORUS amount per period
+- Daily allocation: `100 TORUS/day`
+- Weekly allocation: `700 TORUS/week`
+- Monthly allocation: `3000 TORUS/month`
+
+**Payment Schedule**: Define distribution frequency
+- Real-time (continuous)
+- Daily batches
+- Weekly payments
+- Monthly distributions
+
+**Source Priority**: Order which streams fund fixed payments
+1. Staking rewards (priority 1)
+2. Delegation fees (priority 2)
+3. Other streams (priority 3)
+
+
+
+
+## Delegation Terms Configuration
+
+**Duration**:
+- **Ongoing**: Until manually revoked
+- **Fixed Term**: Specific end date/block
+- **Conditional**: Based on performance metrics
+
+**Recipient**: Agent address to receive delegated emissions
+
+**Constraints**: Optional limitations
+- Maximum delegation amount
+- Performance requirements
+- Review periods
+
+## Monitoring Configuration
+
+Optionally configure delegation monitoring:
+- **Performance metrics**: Track recipient contribution
+- **Auto-adjustment**: Modify delegation based on performance
+- **Reporting**: Regular delegation reports
+
+## Contract Review Checklist
+
+Before submitting, verify:
+- Stream selections and percentages
+- Recipient address
+- Duration and constraints
+- Estimated delegation amounts
+
+## Managing Emission Delegations
+
+### View Active Delegations
+
+Monitor your delegations in the Portal:
+- **Outgoing**: Emissions you're delegating to others
+- **Incoming**: Emissions others are delegating to you
+- **Performance**: Track delegation effectiveness
+
+### Adjust Delegations
+
+For active delegations:
+
+1. Navigate to **Permissions Management** → **Edit Permission**
+2. Select the emission permission to modify
+3. Adjust percentages, amounts, or terms (within constraints)
+4. Submit changes on-chain
+
+### Revoke Delegations
+
+To stop delegating emissions:
+
+1. Find the delegation in your management dashboard
+2. Select **Revoke Permission**
+3. Confirm revocation (takes effect next distribution)
+4. Sign transaction
+
+## Advanced Scenarios
+
+### Multi-Level Delegation Chains
+
+Create complex delegation hierarchies:
+
+```
+Root Agent Alice
+├─ 40% → Agent Bob (Development Team Lead)
+│ ├─ 50% → Agent Carol (Senior Developer)
+│ └─ 30% → Agent Dave (Junior Developer)
+├─ 30% → Agent Eve (Marketing Lead)
+│ ├─ 60% → Agent Frank (Content Creator)
+│ └─ 40% → Agent Grace (Community Manager)
+└─ 20% → Agent Henry (Operations)
+```
+
+### Performance-Based Delegation
+
+Set up conditional delegations:
+
+- **KPI Triggers**: Adjust delegation based on metrics
+- **Milestone Payments**: Release emissions upon achievements
+- **Review Cycles**: Regular performance evaluations
+
+### Hybrid Allocation Models
+
+Combine multiple delegation types:
+
+```typescript
+// Example delegation structure
+const delegationModel = {
+ fixedSalary: {
+ recipient: "agent-bob-address",
+ amount: "1000 TORUS/month",
+ stream: "base-compensation"
+ },
+ performanceBonus: {
+ recipient: "agent-bob-address",
+ percentage: "15%",
+ stream: "staking-rewards",
+ conditions: "monthly-performance > 95%"
+ }
+};
+```
+
+## Best Practices
+
+### Economic Planning
+
+- **Start small**: Begin with small percentages and scale based on performance
+- **Diversify recipients**: Don't delegate all emissions to single agent
+- **Monitor ROI**: Track value created vs. emissions delegated
+- **Plan cash flow**: Ensure sufficient retained emissions for operations
+
+### Risk Management
+
+- **Set constraints**: Use maximum delegation limits
+- **Regular reviews**: Periodically assess delegation effectiveness
+- **Performance metrics**: Establish clear success criteria
+- **Exit strategies**: Plan for delegation termination scenarios
+
+### Operational Efficiency
+
+- **Batch delegations**: Group similar delegations to save transaction costs
+- **Automate monitoring**: Set up alerts for performance thresholds
+- **Document agreements**: Maintain clear records of delegation purposes
+- **Communication**: Coordinate expectations with recipients
+
+## Troubleshooting
+
+### Delegation Creation Fails
+
+**Common issues:**
+- Attempting to delegate more than 100% of a stream
+- Insufficient balance for transaction fees
+- Invalid recipient agent address
+- No active emission streams to delegate
+
+### Payments Not Processing
+
+**Check that:**
+- Delegation permission is active and confirmed
+- Underlying emission streams are still active
+- No conflicting delegations over-allocate streams
+- Recipient agent address is correct
+
+### Performance Issues
+
+**Symptoms:**
+- Delayed payment processing
+- Incorrect delegation amounts
+- Stream identity confusion
+
+**Solutions:**
+- Verify stream selections and percentages
+- Check for delegation chain conflicts
+- Monitor blockchain network status
+- Contact support for complex delegation debugging
+
+## Monitoring and Analytics
+
+### Track Delegation Performance
+
+Monitor key metrics:
+- **Delegation flow rates**: TORUS/day, week, month
+- **Recipient performance**: Value created vs. emissions received
+- **Cost effectiveness**: ROI on delegations
+- **Stream health**: Underlying emission stability
+
+### Optimize Delegation Strategy
+
+Based on performance data:
+- Adjust percentages for top performers
+- Reallocate from underperforming delegations
+- Add performance bonuses for exceptional results
+- Scale successful delegation models
+
+## What's Next?
+
+With emission delegations configured, you can:
+
+- **Build economic networks**: Create multi-agent coordination structures
+- **Scale agent teams**: Hire and compensate agent contributors
+- **Optimize performance**: Use emissions as incentive mechanisms
+- **Analyze economics**: Study delegation ROI and optimization
+
+## Support and Resources
+
+For help with emission delegations:
+
+- [Torus Community Discord](https://discord.gg/torus)
+- [Emission Permissions Documentation](https://docs.torus.network/explanations/v05/emission-permissions/)
+
+#### Related Topics
+
+
+
+ Economic coordination theory
+
+
+ General permission creation
+
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/edit-your-agent.mdx b/src/content/docs/how-to-guides/builders/edit-your-agent.mdx
index 0c71778..46f5b6e 100644
--- a/src/content/docs/how-to-guides/builders/edit-your-agent.mdx
+++ b/src/content/docs/how-to-guides/builders/edit-your-agent.mdx
@@ -12,13 +12,14 @@ import {
import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
import registeredAgents from '/public/images/how-to-guide/register-an-agent/registered-agent-on-allocator-page.png';
import editAgent from '/public/images/how-to-guide/edit-your-agent/allocator-card-edit-agent.png';
import toastExample from '/public/images/how-to-guide/edit-your-agent/allocator-success-toast.png';
In this guide, we'll walk through the process of **editing your Agent information** with the Torus Allocator.
-Both the **Registered Agent** and **Root Agent** can edit their information. Just make sure to use the proper filter on the Allocator Page.
+Both the **Registered Agent** and **Root Agent** can edit their information. Just make sure to use the proper filter on the Allocator tab .
In this guide we will be editing the information of a **Registered Agent**.
#### Why edit your agent?
@@ -41,11 +42,11 @@ and ensures your agent represents your current capabilities and offerings.
Make sure you have a Torus wallet set up and ready to use.
- You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/participants/setup-a-wallet/).
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
- Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough Free Balance to cover the registration fees.
- You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/bridge-to-base/).
+ Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough **Free Balance** to cover the registration fees.
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
You must have a Registered or Root Agent to edit your information.
@@ -56,13 +57,13 @@ and ensures your agent represents your current capabilities and offerings.
## Edit your Agent Information
-1. **Find your Agent in the [Allocator App](https://allocator.torus.network/)**
+1. **Find your Agent in the [Allocator Tab](https://portal.torus.network/root-allocator)**
You can either search for your Agent by name or by the address.
-
+
2. **Click on the card of your Agent**
- The edit is in the Detailed View of the Agent.
+ The edit is in the **Detailed View** of the Agent.
3. **Edit the information and Submit**
@@ -81,12 +82,12 @@ and ensures your agent represents your current capabilities and offerings.
- Telegram
```
4. **Sign the Transaction in the SubWallet and Wait for the Confirmation**
- You will be prompted by SubWallet to sign the on-chain transaction.
- Once confirmed, a toast notification will appear to indicate that your allocation was successful.
+ You will be prompted by SubWallet to sign the on-chain transaction .
+ Once confirmed, a notification will appear to indicate that your allocation was successful.
5. **All Done**
- You can now see your updated information in the Allocator App.
+ You can now see your updated information in the [Allocator Tab](https://portal.torus.network/root-allocator).
@@ -95,7 +96,7 @@ and ensures your agent represents your current capabilities and offerings.
After updating your agent information:
-- **Monitor your presence**: Check how your agent appears on the [Allocator page](https://allocator.torus.network/)
+- **Monitor your presence**: Check how your agent appears on the [Allocator tab](https://portal.torus.network/root-allocator)
- **Stay up to date**: Keep your information updated to match the latest changes
- **Build capabilities**: Set up an [agent server](https://docs.torus.network/how-to-guides/builders/setup-agent-server/) to provide services
diff --git a/src/content/docs/how-to-guides/builders/manage-capabilities.mdx b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
new file mode 100644
index 0000000..91b4498
--- /dev/null
+++ b/src/content/docs/how-to-guides/builders/manage-capabilities.mdx
@@ -0,0 +1,166 @@
+---
+title: Manage Capabilities
+description: Step-by-step guide to creating, editing, and managing capabilities in the Torus control space.
+---
+
+import {
+ Steps,
+ Aside,
+ CardGrid,
+ Card
+} from "@astrojs/starlight/components";
+
+import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
+import confirmCapability from '/public/images/how-to-guide/manage-capabilities/create-capability-confirm-information.png';
+import deleteCapability from '/public/images/how-to-guide/manage-capabilities/delete-capability-confirm-information.png';
+
+In this guide, we'll walk through **managing capabilities** in the Torus control space.
+Capabilities allow you to integrate off-chain resources and services with Torus's on-chain permission system.
+
+## Why Manage Your Capabilities?
+
+Managing capabilities means taking deliberate control over what your agent can do — and what others can do on its behalf.
+By creating capability paths, you define the exact functions your agent exposes, enabling collaboration through delegated permissions.
+By removing outdated or unused capabilities, you reduce the attack surface and keep your agent’s scope minimal and secure.
+
+
+#### What we will accomplish
+
+- [Register a capability path](#register-a-capability-path)
+- [Delete a capability path](#delete-a-capability-path)
+
+
+⏱️ **Estimated time to complete this guide: 10 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a registered agent on Torus.
+ Follow the [agent registration guide](https://docs.torus.network/how-to-guides/builders/register-an-agent/) if needed.
+
+
+ Ensure you have enough TORUS to cover capability registration and deposit fees.
+
+
+
+## Register a Capability path
+
+
+
+1. **Visit the [Create Capability Tab in the Torus Portal](https://portal.torus.network/capabilities/create-capability)**
+ Navigate to the **Capabilities** section in the Torus Portal.
+
+2. **Connect your Torus Wallet**
+ Ensure you're connected with the agent account that will own the capability.
+
+3. **Select the Capability Prefix and Create your Capability Path**
+ Your capability will follow this structure:
+ **`agent-name.capability-path.METHOD`**
+
+ - The `agent-name` is your registered agent name _(pre-filled and uneditable) _.
+ - The `capability-path` is the custom route you define (e.g. `tokens`, `profile_data`, etc.).
+
+
+ Capability paths can only contain **lowercase letters** , **numbers** , **hyphens** , and **underscores** .
+ You **do not** need to type the agent name or method — they are handled by the UI.
+
+ **Examples:**
+
+ - `example-agent.tokens.[method]` ✅
+ - `example-agent.profile_data.[method]` ✅
+ - `example-agent.claim.rewards.[method]` ✅ _Valid (multiple dots are fine within the full structure)_
+ ---
+
+
+ - `example-agent.tokens-.[method]` ❌ _(Invalid. **Hyphen** at the end of capability path)_
+ - `example-agent.Tokens.[method]` ❌ _(Invalid. **Uppercase** letter in capability path)_
+ - `example-agent.tokens!.[method]` ❌ _(Invalid. **Special character** `!` not allowed)_
+ - `example-agent tokens[method]` ❌ _(Invalid. **Space** in capability path)_
+
+
+
+4. **Select REST Method**
+ The `METHOD` is the REST method you select from the list: (`GET`, `POST`, `PATCH`, `DELETE`, `PUT`, `CUSTOM`, `NONE`).
+
+ - **GET** — Retrieve data (e.g. fetch a profile or list).
+ - **POST** — Create new data (e.g. submit a form).
+ - **PATCH** — Update part of an existing resource (e.g. change a name).
+ - **PUT** — Replace a resource entirely.
+ - **DELETE** — Remove a resource.
+ - **CUSTOM** — Define your own method name (useful for RPC-style or special actions).
+ - **NONE** — Leave this field blank (if your capability doesn’t involve a method call).
+
+
+5. **Review information, Submit and Sign the Transaction**
+ Review the capability path in the **Full Capability Path** field.
+ If everything is correct, click **Create Capability**.
+ Open the SubWallet extension and sign the transaction .
+
+
+6. **All Done**
+ You've now successfully created a capability on the Torus control space.
+ Now you can delegate permissions to it.
+
+
+## Delete a Capability path
+
+
+
+1. **Visit the [Delete Capability Tab in the Torus Portal](https://portal.torus.network/capabilities/delete-capability)**
+ Navigate to the **Capabilities** section in the Portal.
+
+2. **Connect your Torus Wallet**
+ Ensure you're connected with the agent account that owns the capability you want to delete.
+
+3. **Select the Capability Segment to Delete**
+ From the dropdown menu, choose the capability segment you want to remove from your agent.
+
+ Capabilities are structured in segments like:
+ **`agent.your-agent-name.test-path.get.depth.add.delete`**
+
+
+ **Understanding Segment-Based Deletion**
+
+ You can delete capabilities by segments, and deletion always removes all subsequent segments :
+
+ **Examples:**
+ - Delete `.get` → Removes `.get.depth.add.delete`
+ - Delete `.add` → Removes `.add.delete` (but keeps `.get.depth`)
+ - Delete `.test-path` → Removes `.test-path.get.depth.add.delete`
+
+ In the **Delegation Preview**, green segments will remain and red segments will be deleted .
+
+
+
+ **Deleting a capability segment is permanent and cannot be undone.**
+
+ Once deleted, any permissions or integrations relying on the deleted segments will stop working immediately. Make sure you're certain about removing these capability segments before proceeding.
+
+
+4. **Review information, Submit and Sign the Transaction**
+ Review the capability path you're about to delete in the preview field.
+ If you're certain you want to proceed, click **Delete Capability**.
+ Open the SubWallet extension and sign the transaction .
+
+
+5. **All Done**
+ You've successfully deleted the capability from the Torus control space.
+ Any existing permissions or delegations to this capability are now invalid.
+
+
+
+## What's Next?
+
+Now that you can manage capabilities, you might want to:
+
+- **Set up delegation**: Delegate permissions to allow other agents to use your capabilities *(coming soon)*
+- **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
+
+Connect with the community:
+- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
+- [Telegram](https://t.me/torusnetwork) — General chat and announcements
+- [Twitter](https://x.com/torus_network) — Updates and ecosystem news
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/manage-permissions.mdx b/src/content/docs/how-to-guides/builders/manage-permissions.mdx
new file mode 100644
index 0000000..cb8a449
--- /dev/null
+++ b/src/content/docs/how-to-guides/builders/manage-permissions.mdx
@@ -0,0 +1,278 @@
+---
+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";
+import RedText from '/src/components/RedText.astro';
+
+In this guide, we'll walk through **managing 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
+- Edit and revoke existing permissions
+- Understand revocation and enforcement mechanisms
+
+
+⏱️ **Estimated time to complete this guide: 15 minutes**
+
+
+## Prerequisites
+
+
+
+ You must have a registered agent that can delegate permissions.
+
+
+ Know the agent addresses you want to delegate permissions to.
+
+
+ Ensure sufficient TORUS for transaction fees.
+
+
+
+## Permission Types
+
+
+
+
+**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
+
+
+
+
+**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
+
+
+
+
+## Create a Permission
+
+
+
+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**
+
+
+
+### Configuring Capability Permissions
+
+For capability permissions, configure these details:
+
+**Namespace Path**: Enter the specific capability path
+- Format: `agent...`
+- 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:
+
+
+
+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
+
+
+
+### Revoke Permissions
+
+To cancel a revocable permission:
+
+
+
+1. Find the permission in your management dashboard
+2. Select **Revoke Permission**
+3. Confirm revocation (immediate effect)
+4. Sign transaction to execute on-chain
+
+
+
+## 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 managing 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)
+- [Permission System Documentation](https://docs.torus.network/explanations/v05/permissions/)
+
+#### Related Topics
+
+
+
+ Deep dive into architecture
+
+
+ Economic coordination mechanisms
+
+
\ No newline at end of file
diff --git a/src/content/docs/how-to-guides/builders/register-an-agent.mdx b/src/content/docs/how-to-guides/builders/register-an-agent.mdx
index 727a102..28fe6f8 100644
--- a/src/content/docs/how-to-guides/builders/register-an-agent.mdx
+++ b/src/content/docs/how-to-guides/builders/register-an-agent.mdx
@@ -11,6 +11,7 @@ import {
LinkCard
} from "@astrojs/starlight/components";
import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
import registerAnAgentButton from '/public/images/how-to-guide/register-an-agent/register-an-agent-button.png';
import connectWalletOnPortal from '/public/images/how-to-guide/register-an-agent/connect-wallet-on-portal.png';
import filledAgentInformation from '/public/images/how-to-guide/register-an-agent/filled-agent-information.png';
@@ -47,11 +48,11 @@ Registering an agent makes you discoverable in Torus and enables you to receive
Make sure you have a Torus wallet set up and ready to use.
- You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/participants/setup-a-wallet/).
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
Check your balance in the [Torus Wallet](https://wallet.torus.network) and ensure you have enough Free Balance to cover the registration fees.
- You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/bridge-to-base/).
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
@@ -64,30 +65,43 @@ Registering an agent makes you discoverable in Torus and enables you to receive
2. **Connect your Torus Wallet**
- Click the **Connect Wallet** button at the top right and select your Torus wallet.
+ Click the **Connect Wallet** button at the top right and select your Torus wallet.
3. **Fill in your agent details**
Provide the required information such as your agent name, description, and technical details.
-
- Agent names can only contain lowercase letters, numbers, hyphens, and underscore.
- - agent-name- (Invalid agent Name). Reason: Hyphen at the end
- - **A**gent-name (Invalid agent Name). Reason: Uppercase letter
- - Agent name (Invalid agent Name). Reason: Space in the middle
- - Agent.name (Invalid agent Name). Reason: Dot as separator
- ---
- - agent_name (Valid agent Name)
- - agent-name (Valid agent Name)
+
+
+ **Agent names are permanent and cannot be changed after creation.**
+
+ Choose your agent name carefully as it serves as a persistent identifier that will remain with your agent forever. You will need to create a new agent (with new registration fees) if you want a different name.
+
+
+
+ Agent names can only contain **lowercase letters** , **numbers** , **hyphens** , and **underscores** .
+ You will define your agent name during registration, and it will be used as the prefix in capability paths.
+
+ **Examples:**
+
+ - `agent_name` ✅
+ - `agent-name` ✅
+
+ ---
+
+ - `agent-name-` ❌ _(Invalid. **Hyphen** at the end)_
+ - `Agent-name` ❌ _(Invalid. **Uppercase letter**)_
+ - `Agent name` ❌ _(Invalid. **Space** in name)_
+ - `Agent.name` ❌ _(Invalid. **Dot** not allowed)_
4. **Add Relevant links and social profiles**
- Even though it is not mandatory, we strongly recommend adding links and social profiles.
+ Even though it is not mandatory, we strongly recommend adding links and social profiles .
This will help your agent to be discovered and used by the Torus community.
5. **Confirm registration**
- Click on register an agent and confirm the transaction in your wallet.
+ Click on **register an agent** and confirm the transaction in your wallet .
When you hover the mouse on the Registration Fee Price, you will see the breakdown of the registration fees.
@@ -98,9 +112,9 @@ Registering an agent makes you discoverable in Torus and enables you to receive
- Capability Deposit: Variable deposit based on the size of the agent name. This value is refunded when the capability is removed.
-6. **Check your Agent on the [Allocator Page](https://allocator.torus.network/?isWhitelisted=false)**
- You should find your agent on the Allocator Page, with the filter of Registered Agents.
-
+6. **Check your Agent on the [Allocator tab](https://portal.torus.network/root-allocator?isWhitelisted=false)**
+ You should find your agent on the Allocator tab , with the filter of **Registered Agents** .
+
6. **All Done**
You've now successfully registered an Agent on Torus.
diff --git a/src/content/docs/how-to-guides/builders/setup-agent-client.mdx b/src/content/docs/how-to-guides/builders/setup-agent-client.mdx
index 5e82de1..768bd07 100644
--- a/src/content/docs/how-to-guides/builders/setup-agent-client.mdx
+++ b/src/content/docs/how-to-guides/builders/setup-agent-client.mdx
@@ -9,6 +9,7 @@ import {
CardGrid,
Card
} from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
In this guide, we'll **setup an agent client** to interact with agent APIs with automatic authentication.
@@ -42,49 +43,115 @@ Agent clients allow you to easily communicate with other agents' APIs, enabling
-1. **Install the Torus SDK**
+1. **Install the required dependencies**
```sh
- npm install @torus-network/sdk
+ npm install @torus-network/sdk dotenv
+ npm install -D @types/node
```
-2. **Create a keypair**
+2. **Create environment configuration**
- ```ts
- import { AgentClient, Keypair } from "@torus-network/sdk";
+ Create a `.env` file in your project root:
+
+ ```env
+ AGENT_MNEMONIC=your twelve word mnemonic phrase goes here exactly like this
+ TARGET_AGENT_URL=http://localhost:3000
+ NODE_ENV=development
+ ```
+
+3. **Create the client with proper error handling**
- const keypair = new Keypair(
- "your twelve word mnemonic phrase goes here exactly like this"
- );
+ ```ts
+ import { AgentClient, Keypair } from "@torus-network/sdk/agent-client";
+ import dotenv from "dotenv";
+
+ // Load environment variables
+ dotenv.config();
+
+ async function createClient() {
+ try {
+ if (!process.env.AGENT_MNEMONIC) {
+ throw new Error("AGENT_MNEMONIC environment variable is required");
+ }
+
+ const keypair = new Keypair(process.env.AGENT_MNEMONIC);
+
+ const client = new AgentClient({
+ keypair,
+ baseUrl: process.env.TARGET_AGENT_URL || "http://localhost:3000",
+ });
+
+ console.log("Agent client initialized successfully");
+ return client;
+ } catch (error) {
+ console.error("Failed to create agent client:", error);
+ throw error;
+ }
+ }
```
-3. **Create the client**
+4. **Make API calls with comprehensive error handling**
```ts
- const client = new AgentClient({
- keypair,
- baseUrl: "http://localhost:3000", // Target agent server URL
- });
+ async function callAgent(client: AgentClient, endpoint: string, data: any) {
+ try {
+ console.log(`Calling endpoint: ${endpoint} with data:`, data);
+
+ const response = await client.call({
+ endpoint,
+ data,
+ });
+
+ if (response.success) {
+ console.log("Response received:", response.data);
+ return response.data;
+ } else {
+ console.error("API call failed:", response.error);
+ throw new Error(`API call failed: ${response.error}`);
+ }
+ } catch (error) {
+ console.error(`Error calling ${endpoint}:`, error);
+ throw error;
+ }
+ }
```
-4. **Make API calls**
+5. **Complete example with initialization and usage**
```ts
- const response = await client.call({
- endpoint: "hello",
- data: { name: "Alice" },
- });
-
- if (response.success) {
- console.log("Response:", response.data);
- } else {
- console.error("Error:", response.error);
+ async function main() {
+ try {
+ // Initialize the client
+ const client = await createClient();
+
+ // Make API calls
+ const helloResponse = await callAgent(client, "hello", {
+ name: "Alice"
+ });
+
+ console.log("Hello response:", helloResponse);
+
+ // You can make multiple calls
+ const anotherResponse = await callAgent(client, "hello", {
+ name: "Bob"
+ });
+
+ console.log("Another response:", anotherResponse);
+
+ } catch (error) {
+ console.error("Application failed:", error);
+ process.exit(1);
+ }
}
+
+ // Run the client
+ main();
```
-5. **All Done**
+6. **All Done**
- Your agent client is now ready to communicate with other agents' APIs.
+ Your agent client is now ready to communicate with other agents' APIs with proper error handling and environment configuration.
diff --git a/src/content/docs/how-to-guides/builders/setup-agent-server.mdx b/src/content/docs/how-to-guides/builders/setup-agent-server.mdx
index 21a82f1..97d1d9d 100644
--- a/src/content/docs/how-to-guides/builders/setup-agent-server.mdx
+++ b/src/content/docs/how-to-guides/builders/setup-agent-server.mdx
@@ -1,6 +1,6 @@
---
title: Setup Agent Server
-description: Step-by-step guide to build APIs with the Agent class from torus-ts-sdk.
+description: Step-by-step guide to build APIs with the Agent class from @torus-network/sdk.
---
import {
@@ -9,6 +9,7 @@ import {
CardGrid,
Card
} from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
In this guide, we'll **setup an agent server** to build authenticated APIs with automatic OpenAPI documentation.
@@ -43,61 +44,123 @@ Agent servers allow you to create APIs that other agents can discover and intera
-1. **Install the Torus SDK**
+1. **Install the required dependencies**
```sh
- npm install @torus-network/sdk
+ npm install @torus-network/sdk dotenv zod
+ npm install -D @types/node
```
-2. **Create a basic server**
+2. **Create environment configuration**
+
+ Create a `.env` file in your project root:
+
+ ```env
+ AGENT_KEY=your-agent-wallet-address
+ AGENT_MNEMONIC=your twelve word mnemonic phrase goes here exactly like this
+ PORT=3000
+ NODE_ENV=development
+ ```
+
+3. **Create the server with proper error handling**
```ts
- import { Agent } from "@torus-network/sdk";
+ import { Agent } from "@torus-network/sdk/agent";
import { z } from "zod";
-
- const agent = new AgentServer({
- agentKey: "your-agent-wallet-address", // Your registered agent's wallet address
- port: 3000,
- docs: {
- info: {
- title: "My Agent API",
- version: "1.0.0",
- },
- },
- });
+ import dotenv from "dotenv";
+
+ // Load environment variables
+ dotenv.config();
+
+ async function createAgent() {
+ try {
+ const agent = new Agent({
+ agentKey: process.env.AGENT_KEY!,
+ port: parseInt(process.env.PORT || "3000"),
+ docs: {
+ info: {
+ title: "My Agent API",
+ version: "1.0.0",
+ },
+ },
+ });
+
+ return agent;
+ } catch (error) {
+ console.error("Failed to create agent:", error);
+ process.exit(1);
+ }
+ }
```
-3. **Add an endpoint**
+4. **Add endpoints with comprehensive error handling**
```ts
- agent.endpoint({
- endpoint: "hello",
- schema: {
- input: z.object({
- name: z.string(),
- }),
- output: z.object({
- message: z.string(),
- }),
- },
- handler: async ({ input }) => {
- return {
- message: `Hello, ${input.name}!`,
- };
- },
- });
+ async function setupEndpoints(agent: Agent) {
+ try {
+ agent.method({
+ endpoint: "hello",
+ schema: {
+ input: z.object({
+ name: z.string(),
+ }),
+ output: z.object({
+ message: z.string(),
+ }),
+ },
+ handler: async ({ input }) => {
+ try {
+ return {
+ message: `Hello, ${input.name}!`,
+ };
+ } catch (error) {
+ console.error("Error in hello endpoint:", error);
+ throw error;
+ }
+ },
+ });
+
+ console.log("Endpoints configured successfully");
+ } catch (error) {
+ console.error("Failed to setup endpoints:", error);
+ throw error;
+ }
+ }
```
-4. **Start the server**
+5. **Start the server with proper initialization**
```ts
- agent.start();
- console.log("Agent server running on http://localhost:3000");
+ async function startServer() {
+ try {
+ const agent = await createAgent();
+ await setupEndpoints(agent);
+
+ agent.run();
+
+ const port = process.env.PORT || 3000;
+ console.log(`Agent server running on http://localhost:${port}`);
+ console.log(`API documentation available at http://localhost:${port}/docs`);
+
+ // Graceful shutdown handling
+ process.on('SIGTERM', () => {
+ console.log('Received SIGTERM, shutting down gracefully');
+ process.exit(0);
+ });
+
+ } catch (error) {
+ console.error("Failed to start server:", error);
+ process.exit(1);
+ }
+ }
+
+ // Start the server
+ startServer();
```
-5. **All Done**
+6. **All Done**
- Your agent server is now running and available at `http://localhost:3000/docs` for API documentation.
+ Your agent server is now running with proper error handling and environment configuration. The API documentation is available at `http://localhost:3000/docs`.
diff --git a/src/content/docs/how-to-guides/participants/bridge-from-base.mdx b/src/content/docs/how-to-guides/holders/bridge-from-base.mdx
similarity index 85%
rename from src/content/docs/how-to-guides/participants/bridge-from-base.mdx
rename to src/content/docs/how-to-guides/holders/bridge-from-base.mdx
index 5574036..d2f1cab 100644
--- a/src/content/docs/how-to-guides/participants/bridge-from-base.mdx
+++ b/src/content/docs/how-to-guides/holders/bridge-from-base.mdx
@@ -10,6 +10,7 @@ import {
Card
} from "@astrojs/starlight/components";
import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
import metamaskSubwalletConnect from '/public/images/how-to-guide/bridge-to-base/metamask-subwallet-connect.png';
import fillInFormToConvert from '/public/images/how-to-guide/bridge-to-base/fill-in-form-to-convert.png';
import confirmTransactionInMetamask from '/public/images/how-to-guide/bridge-to-base/confirm-transaction-in-metamask.png';
@@ -44,7 +45,7 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
A Torus wallet connected.
- If you don't have one, you can follow the [setup guide here](https://docs.torus.network/how-to-guides/participants/setup-a-wallet/).
+ If you don't have one, you can follow the [setup guide here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
@@ -72,10 +73,10 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
2. **Swap from Base TORUS to Torus EVM**
- Make sure you are **connected** to **both wallets**
- - Make sure you are on the **correct tab**, **TORUS EVM - Base**
- - Make sure it is **FROM** Base TORUS **TO** Torus EVM
+ - Make sure you are on the **correct tab** , **TORUS EVM - Base**
+ - Make sure it is FROM **Base TORUS** TO **Torus EVM**
- Fill in the form with the amount you want to convert and the Recipient Address, by clicking on the Self button, it will automatically fill the address for you with your connected base wallet.
+ Fill in the form with the amount you want to convert and the Recipient Address, by clicking on the Self button , it will automatically fill the address for you with your connected base wallet.
With all the information filled in, click **Continue**.
@@ -91,8 +92,7 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
4. **Confirmation of the swap**
After the transaction succeeds, your Base TORUS should now be displayed as Torus EVM as it was successfully swapped.
This process can take a while to complete on the blockchain,
- so please wait a few minutes and refresh the [Base Bridge Web App](https://bridge.torus.network/?tab=base&from=base&to=torus).
- If you have any issues, reach out to our support on the [Official Torus Discord](https://discord.gg/torus).
+ so please wait a few minutes and refresh the page.
@@ -110,8 +110,8 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
1. **Swap from Torus EVM to Torus**
- Make sure you are **connected** in **Both Wallets**
- - Make sure you are in the **correct Tab**, **TORUS EVM - Base**
- - Make sure it is **FROM** Torus EVM **TO** Torus
+ - Make sure you are in the **correct Tab** , **TORUS EVM - Base**
+ - Make sure it is FROM **Torus EVM** TO **Torus**
Fill in the form with the amount you want to convert, after confirmation, you will be prompted to sign the transaction in Torus.
@@ -128,7 +128,7 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
3. **Confirmation of the swap**
After the transaction succeeds, your Torus EVM should now be displayed as TORUS as it was successfully swapped.
This process can take a while to complete on the blockchain,
- so please wait a few minutes and refresh the [Base Bridge Web App](https://bridge.torus.network/?tab=base&from=base&to=torus).
+ so please wait a few minutes and refresh the page.
4. **All Done**
@@ -141,10 +141,10 @@ To keep things clear and concise, **Native TORUS** will be referred to as **TORU
Now that you have TORUS tokens, you can:
-- **Start earning rewards**: [Stake your TORUS](https://docs.torus.network/how-to-guides/participants/stake-your-torus/) to support agents and earn emissions
+- **Start earning rewards**: [Stake your TORUS](https://docs.torus.network/how-to-guides/holders/stake-your-torus/) to support agents and earn emissions
- **Become an agent**: [Register an agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/) to provide services and earn directly
- **Explore the ecosystem**: Browse agents and allocators on the [Torus Portal](https://portal.torus.network/)
-- **Understand tokenomics**: Learn about [TORUS economics](https://docs.torus.network/concepts/tokenomics/) and emission mechanisms
+- **Understand tokenomics**: Learn about [TORUS economics](https://docs.torus.network/getting-started/tokenomics/) and emission mechanisms
Connect with the community:
- [Discord](https://discord.gg/torus) — Technical discussions, support, and announcements
diff --git a/src/content/docs/how-to-guides/participants/setup-a-wallet.mdx b/src/content/docs/how-to-guides/holders/setup-a-wallet.mdx
similarity index 82%
rename from src/content/docs/how-to-guides/participants/setup-a-wallet.mdx
rename to src/content/docs/how-to-guides/holders/setup-a-wallet.mdx
index 82ab1de..f2eca51 100644
--- a/src/content/docs/how-to-guides/participants/setup-a-wallet.mdx
+++ b/src/content/docs/how-to-guides/holders/setup-a-wallet.mdx
@@ -18,8 +18,9 @@ import subwalletOpenSetup from '/public/images/how-to-guide/setup-wallet/subwall
import subwalletSelectConfigToAddNetwork from '/public/images/how-to-guide/setup-wallet/subwallet-select-config-to-add-network.png';
import subwalletSearchTorusNetwork from '/public/images/how-to-guide/setup-wallet/subwallet-search-torus-network.png';
import subwalletDoneTorusSetup from '/public/images/how-to-guide/setup-wallet/subwallet-done-torus-setup.png';
+import RedText from '/src/components/RedText.astro';
-In this guide, we'll walk through setting up a wallet with the **SubWallet** browser extension, a popular non-custodial wallet for managing assets across multiple blockchains.
+In this guide, we'll walk through setting up a wallet with the **SubWallet** browser extension , a popular non-custodial wallet for managing assets across multiple blockchains.
If you prefer a different extension, scroll to the bottom for a list of other wallets that work with Torus.
For simplicity's sake, though, we'll focus on SubWallet.
@@ -67,10 +68,10 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak
-1. **Open the SubWallet extension in your browser**:
+1. **Open the SubWallet extension in your browser**
Click on the SubWallet icon in your browser’s extension area to open the wallet.
-2. **Click Create a New Account**:
+2. **Click Create a New Account**
You will be prompted between three options:
- Create new account
@@ -80,11 +81,11 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak
Select the **"Create new account"** option.
-3. **Create a Master Password**:
- You will be prompted to create a master password. This password is crucial as it encrypts your wallet data on your device for security.
+3. **Create a Master Password**
+ You will be prompted to create a master password. This password is crucial as it encrypts your wallet data on your device for security.
-4. **Backup Your Seed Phrase**:
- After setting your password and accepting all the seed phrase terms, you will receive a seed phrase. **Write this down and store it in a secure location. This seed phrase is essential for recovering your wallet if you forget your password or lose access to your device.**
+4. **Backup Your Seed Phrase**
+ After setting your password and accepting all the seed phrase terms, you will receive a seed phrase. **Write this down and store it in a secure location. This seed phrase is essential for recovering your wallet if you forget your password or lose access to your device.**
[Here's a video for you to watch later about methods to keep your seed phrase safe](https://www.youtube.com/watch?v=fdtx0MG0Xgo).
@@ -117,12 +118,12 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak
2. **Select Manage Networks**
- Under the **Assets & Addresses** tab, click on **Manage Networks**.
+ Under the **Assets & Addresses** tab, click on **Manage Networks** .
3. **Search for Torus and activate it**
- Click on the search bar, type Torus, and select it from the list. Make sure to enable it so it appears in your list of active tokens.
+ Click on the search bar, type Torus, and select it from the list. Make sure to enable it so it appears in your list of active tokens.
4. **Confirm Torus is active**
@@ -149,10 +150,7 @@ You need a wallet to hold TORUS and interact with Torus - it's required for stak
Now that you have a wallet set up, you can:
-- **Get TORUS tokens**: [Bridge from Base](https://docs.torus.network/how-to-guides/bridge-to-base/) to get TORUS tokens into your wallet
-- **Start earning**: [Stake your TORUS](https://docs.torus.network/how-to-guides/participants/stake-your-torus/) to support agents and earn rewards
-- **Become an agent**: [Register an agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/) to participate actively in the network
-- **Understand Torus**: Learn about [concepts & terminology](https://docs.torus.network/getting-started/concepts/) to better understand the ecosystem
+- **Get TORUS**: [Bridge from Base](https://docs.torus.network/how-to-guides/holders/bridge-from-base/) to get TORUS into your wallet
For SubWallet-specific help, check the [SubWallet Documentation](https://docs.subwallet.app/main).
diff --git a/src/content/docs/how-to-guides/participants/stake-your-torus.mdx b/src/content/docs/how-to-guides/holders/stake-your-torus.mdx
similarity index 76%
rename from src/content/docs/how-to-guides/participants/stake-your-torus.mdx
rename to src/content/docs/how-to-guides/holders/stake-your-torus.mdx
index 4c52395..f348f1e 100644
--- a/src/content/docs/how-to-guides/participants/stake-your-torus.mdx
+++ b/src/content/docs/how-to-guides/holders/stake-your-torus.mdx
@@ -11,6 +11,7 @@ import {
Card
} from "@astrojs/starlight/components";
import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
import walletStakingTab from '/public/images/how-to-guide/stake-your-torus/wallet-staking-tab.png';
import connectToWallet from '/public/images/how-to-guide/stake-your-torus/connect-to-wallet.png';
import fillInInformation from '/public/images/how-to-guide/stake-your-torus/fill-in-information.png';
@@ -43,11 +44,11 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
Make sure you have a Torus wallet set up and ready to use.
- You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/participants/setup-a-wallet/).
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
Check your balance on the [Torus Wallet](https://wallet.torus.network) and ensure you have enough Free Balance to cover the registration fees.
- You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/bridge-to-base/).
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
@@ -57,11 +58,11 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
1. **Go to the [Staking tab in the Torus Wallet App](https://wallet.torus.network/staking)**
- In the Torus Wallet App, click on the **Staking** tab. Then click on **Stake**.
+ In the Torus Wallet App, click on the **Staking** tab. Then click on **Stake** .
2. **Connect your Torus Wallet**
- Click the **Connect Wallet** button at the top right and select your Torus wallet.
+ Click the **Connect Wallet** button at the top right and select your Torus wallet.
3. **Select the Allocator Address**
@@ -73,8 +74,8 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
4. **Fill in the required fields and confirm**
After you:
- - Selected the **Allocator Address**
- - Entered the **amount of TORUS** you wanted to stake
+ - Selected the **Allocator Address**
+ - Entered the **amount of TORUS** you wanted to stake
Click on **Review & Submit Transaction**.
@@ -87,13 +88,13 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
5. **Open SubWallet and Sign the Transaction**
- Click on the Subwallet icon at the top right navigation bar of your browser.
+ Click on the Subwallet icon at the top right navigation bar of your browser.
It will open a modal with the confirmation to sign the transaction.
-6. **Your TORUS is now staked, but you must allocate to an Agent**
- After signing your TORUS should show as **Staked Balance** in the Wallet App.
+6. **Your TORUS is staked, you can now allocate to an Agent**
+ After signing your TORUS should show as Staked Balance in the Wallet App.
This process can take a few minutes to complete, make sure to reload the page to see the updated balance.
When you see your staked balance, you can now allocate to an Agent.
@@ -101,10 +102,10 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
### Allocating to an Agent
-1. **Open the [Torus Allocator App](https://allocator.torus.network/)**
- You’ll see a list of all current **Root Agents**.
+1. **Open the [Torus Allocator Tab](https://portal.torus.network/root-allocator)**
+ You'll see a list of all current **Root Agents**.
- This page acts as an index of available **Root Agents** and shows a summary for each one.
+ This page acts as an index of available **Agents** and shows a summary for each one.
Click on any card to view more detailed information about the agent.
In the picture below, here's what each highlight represents:
@@ -117,28 +118,28 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
You can hover your mouse over the components to see the details.
-
+
2. **Choose the agents to allocate**
- Use the slider on each agent card to reserve the amount you want to allocate.
+ Use the slider on each agent card to reserve the amount you want to allocate.
The agents shown in the example are for demonstration purposes only — they are not recommendations.
Feel free to allocate to any agent you prefer, in any amount.
- In this step, you’re only **reserving** the amount — no tokens are staked yet, as it is highlighted in light blue.
+ In this step, you're only **reserving** the amount — no tokens are staked yet, as it is highlighted in light blue.
3. **Open the Allocation Menu and Confirm**
- When you open the Allocation Menu, you will see the list of the agents you’ve chosen to allocate to.
- If you are sure that you want to allocate to these agents, click on **Submit Agents**.
+ When you open the Allocation Menu , you will see the list of the agents you've chosen to allocate to.
+ If you are sure that you want to allocate to these agents, click on **Submit Agents** .
4. **Sign the Transaction in the SubWallet**
- After confirming the allocation, you will be prompted to sign the transaction in your wallet.
- Click on the SubWallet icon at the top right navigation bar of your browser.
+ After confirming the allocation, you will be prompted to sign the transaction in your wallet .
+ Click on the SubWallet icon at the top right navigation bar of your browser.
It will open a modal with the confirmation to sign the transaction.
@@ -159,8 +160,8 @@ Staking your TORUS allows you to earn emission rewards while supporting agents y
Now that you're earning emissions, you might want to:
-- **Optimize your strategy**: Monitor agent performance on the [Allocator page](https://allocator.torus.network/) and adjust allocations
-- **Understand the system**: Learn about [tokenomics](https://docs.torus.network/concepts/tokenomics/) and how emissions flow through the network
+- **Optimize your strategy**: Monitor agent performance on the [Allocator tab](https://portal.torus.network/root-allocator) and adjust allocations
+- **Understand the system**: Learn about [tokenomics](https://docs.torus.network/getting-started/tokenomics/) and how emissions flow through the network
- **Receive Updates**: Follow [Torus on Twitter](https://x.com/torus_network) to stay informed about the latest developments —
this can help you evaluate which agents are most promising for allocation and potential rewards.
diff --git a/src/content/docs/how-to-guides/root-agents/become-a-root-agent.mdx b/src/content/docs/how-to-guides/root-agents/become-a-root-agent.mdx
index 0feb3de..a5f97a2 100644
--- a/src/content/docs/how-to-guides/root-agents/become-a-root-agent.mdx
+++ b/src/content/docs/how-to-guides/root-agents/become-a-root-agent.mdx
@@ -10,6 +10,7 @@ import {
Card
} from "@astrojs/starlight/components";
import ClickableImage from '/src/components/ClickableImage.astro';
+import RedText from '/src/components/RedText.astro';
import daoShapeTheNetwork from '/public/images/how-to-guide/become-a-root-agent/dao-shape-the-network.png';
import selectTheWhitelistOption from '/public/images/how-to-guide/become-a-root-agent/select-the-whitelist-option.png';
@@ -42,11 +43,11 @@ Root Agents receive emissions directly from the stake root and can set goals for
Make sure you have a Torus wallet set up and ready to use.
- You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/participants/setup-a-wallet/).
+ You can find a [guide on how to set up a wallet here](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/).
Check your balance on the [Torus Wallet](https://wallet.torus.network) and ensure you have enough Free Balance to cover the registration fees.
- You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/bridge-to-base/).
+ You can find a [guide on how to bridge TORUS here](https://docs.torus.network/how-to-guides/holders/bridge-from-base/).
Have a valid Discord account and join the official [Torus Discord
@@ -63,7 +64,7 @@ Root Agents receive emissions directly from the stake root and can set goals for
The Whitelist Application page is found in the DAO page.
2. **Connect your Torus Wallet**
- Click the **Connect Wallet** button at the top right and select your Torus wallet.
+ Click the **Connect Wallet** button at the top right and select your Torus wallet.
3. **Click on Shape the Network Button**
It is located in the top right corner of the dashboard.
@@ -84,7 +85,7 @@ Root Agents receive emissions directly from the stake root and can set goals for
5. **Submit Proposal**
- After filling in the form, click **Submit Proposal** and confirm the transaction in your wallet.
+ After filling in the form, click **Submit Proposal** and confirm the transaction in your wallet.
The proposal cost (**100 TORUS**) will be deducted from your connected wallet.
diff --git a/src/content/docs/how-to-guides/start-here.mdx b/src/content/docs/how-to-guides/start-here.mdx
index 3088c09..050b630 100644
--- a/src/content/docs/how-to-guides/start-here.mdx
+++ b/src/content/docs/how-to-guides/start-here.mdx
@@ -19,13 +19,13 @@ Whether you're here to use Torus, build on it, or coordinate its evolution, ther
-## For Torus Participants
+## 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/participants/setup-a-wallet/)
-- [Bridge from Base](https://docs.torus.network/how-to-guides/participants/bridge-from-base/)
-- [Stake your TORUS](https://docs.torus.network/how-to-guides/participants/stake-your-torus/)
+- [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/)
- Allocate Emissions _(coming soon)_
---
@@ -34,13 +34,14 @@ If you want to interact with Torus as an end-user or holder:
If you're developing tools, services, or integrations on Torus:
-- [Setup CLI](https://docs.torus.network/how-to-guides/builders/setup-cli/)
- [Register an Agent](https://docs.torus.network/how-to-guides/builders/register-an-agent/)
- [Edit your Agent](https://docs.torus.network/how-to-guides/builders/edit-your-agent/)
- [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/)
-- Capability (Namespace) Registration _(coming soon)_
+- [Manage Capabilities](https://docs.torus.network/how-to-guides/builders/manage-capabilities/)
+- Manage Permissions _(coming soon)_
+- Delegate Emission Streams _(coming soon)_
---
@@ -50,7 +51,7 @@ _Leading new swarms or driving protocol changes_
If you're pioneering new goals or submitting DAO proposals:
- [Become a Root Agent](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/)
-- _See the [Governance & DAO](https://docs.torus.network/concepts/governance-dao/) section for docs on proposal types and formats._
+- _See the [Governance & DAO](https://docs.torus.network/explanations/v05/governance-dao/) section for docs on proposal types and formats._
---
diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
index 1da82ad..8272002 100644
--- a/src/content/docs/index.mdx
+++ b/src/content/docs/index.mdx
@@ -1,23 +1,44 @@
---
-title: Introduction
-description: Layer1 self-assembling & self-optimizing autonomous super-swarm
+title: Welcome to Torus
+description: The decentralized protocol for autonomous agent swarms and intelligent coordination
---
import { CardGrid, LinkCard, Aside } from "@astrojs/starlight/components";
+import RedText from '/src/components/RedText.astro';
-# Layer1 self-assembling & self-optimizing autonomous super-swarm
+**Torus is a decentralized protocol that enables autonomous agents to form intelligent swarms, collaborate on complex goals, and share capabilities through a permission-based system.**
-Torus is a stake-based p2p protocol for goal-driven agent swarm coordination. The system operates as one fractal super-swarm, which is composed of one emergent hypergraph of recursively delegated permissions and incentives among agents. Swarms are subgraphs, and can form at any position in the hypergraph.
+Whether you're looking to stake tokens, build agent services, or coordinate with other agents, Torus provides the infrastructure for decentralized autonomous collaboration.
-The Torus hypergraph emerges from and aligns back to the stake root, tethering the system to the interests of stake. Torus aligns towards the central point of stake, while stake is decentralized representing the system as a whole, effectively aligning it to itself.
+## Get stuff done
-Swarms form bottom-up around top-down goals, their formation happens organically without central planning. Swarms operate as self-assembling multi-scale competency architectures, collectively navigating towards complex goals with full autonomy at every level and open competition at every edge.
+- **For Token Holders** — [Setup a Wallet, Stake TORUS, earn rewards](https://docs.torus.network/how-to-guides/holders/setup-a-wallet/)
+- **For Agent Builders** — [Create autonomous agents and build services on Torus](https://docs.torus.network/how-to-guides/builders/register-an-agent/)
+- **For Swarm Leaders** — [Become a root agent and lead coordinated initiatives](https://docs.torus.network/how-to-guides/root-agents/become-a-root-agent/)
-The permission & delegation system enables agents to granularily specialize while remaining aligned across levels. Swarms collectively explore a problem space and engage in an open-ended process of recursive niche construction to navigate towards the swarms goal.
+---
+
+## Understand more
+
+- [Understanding Torus](https://docs.torus.network/getting-started/concepts/) — Deep dive into how Torus works and its core concepts
+- [Tokenomics](https://docs.torus.network/getting-started/tokenomics/) — Learn about TORUS token economics and incentive structures
+- [Explanations](https://docs.torus.network/explanations/start-here/) — In-depth explanations of concepts and architecture
+
+---
+
+## Need Help?
+
+Connect with the Torus community:
+
+- **[Discord](https://discord.gg/torus)** — Technical discussions, support, and community calls
+- **[Telegram](https://t.me/torusnetwork)** — Quick help and announcements
+- **[Twitter](https://x.com/torus_network)** — Latest updates and ecosystem news
+---
-#### v0.5
+## Choose Your Path
-The v0.5 is a pragmatic, growth oriented and limited implemention of the Torus conceptual model. It's mainnet release initiates the formation process of the Torus hypergraph and allows battletesting of our concepts. It is sufficient for the formation of sophisticated agent swarms and applies the core ideas.
+This documentation is structured linearly, but you're free to explore it your way.
-The Torus v1 will be the pure and complete implementation of the Torus conceptual model and will be delivered after undergoing a growth phase with the v0.5.
+You can start with What it is or skip ahead to How it works .
+If you choose What it is , just follow the guide step-by-step using the **Next** button bellow.
\ No newline at end of file
diff --git a/src/content/docs/web-apps/torus-allocator.mdx b/src/content/docs/web-apps (deprecated)/torus-allocator.mdx
similarity index 94%
rename from src/content/docs/web-apps/torus-allocator.mdx
rename to src/content/docs/web-apps (deprecated)/torus-allocator.mdx
index b70b5f0..af10f22 100644
--- a/src/content/docs/web-apps/torus-allocator.mdx
+++ b/src/content/docs/web-apps (deprecated)/torus-allocator.mdx
@@ -36,7 +36,7 @@ For staking details, see [torus wallet](torus-wallet).
## Allocating Weights
-1. **Connect**: Visit [allocator.torus.network](https://allocator.torus.network) and connect wallet
+1. **Connect**: Visit [portal.torus.network/root-allocator](https://portal.torus.network/root-allocator) and connect wallet
2. **Browse Agents**: Review available root agents and their metrics
3. **Set Weights**: Use sliders to allocate percentages to chosen agents
4. **Open Allocation Menu**: Review your weight distribution
diff --git a/src/content/docs/web-apps/torus-dao.mdx b/src/content/docs/web-apps (deprecated)/torus-dao.mdx
similarity index 85%
rename from src/content/docs/web-apps/torus-dao.mdx
rename to src/content/docs/web-apps (deprecated)/torus-dao.mdx
index 501d9dd..28d37ca 100644
--- a/src/content/docs/web-apps/torus-dao.mdx
+++ b/src/content/docs/web-apps (deprecated)/torus-dao.mdx
@@ -63,18 +63,3 @@ The dashboard contains three tabs:
4. Submit for community voting
**Voting**: DAO members can vote to approve/reject proposals and manage network parameters
-
-#### Related Topics
-
-
-
-
-
\ No newline at end of file
diff --git a/src/content/docs/web-apps/torus-portal.mdx b/src/content/docs/web-apps (deprecated)/torus-portal.mdx
similarity index 97%
rename from src/content/docs/web-apps/torus-portal.mdx
rename to src/content/docs/web-apps (deprecated)/torus-portal.mdx
index 43e59d6..56f9660 100644
--- a/src/content/docs/web-apps/torus-portal.mdx
+++ b/src/content/docs/web-apps (deprecated)/torus-portal.mdx
@@ -45,7 +45,7 @@ For Capability concepts, see [Capability Permissions](../v05/capability-permissi
## Network Operations
-**Register Agent**: Basic agent registration (different from [root agent registration](../agents/apply-root-agent))
+**Register Agent**: Basic agent registration (different from [root agent registration](/how-to-guides/root-agents/become-a-root-agent))
**Create Signal**: Broadcast coordination messages to other agents in Torus
diff --git a/src/content/docs/web-apps/torus-wallet.mdx b/src/content/docs/web-apps (deprecated)/torus-wallet.mdx
similarity index 97%
rename from src/content/docs/web-apps/torus-wallet.mdx
rename to src/content/docs/web-apps (deprecated)/torus-wallet.mdx
index b1cb146..41db3d8 100644
--- a/src/content/docs/web-apps/torus-wallet.mdx
+++ b/src/content/docs/web-apps (deprecated)/torus-wallet.mdx
@@ -72,7 +72,7 @@ Bridge transactions may take several minutes to complete due to cross-chain proc
/>
\ No newline at end of file
diff --git a/src/tailwind.css b/src/tailwind.css
index 9ca2352..5b4c599 100644
--- a/src/tailwind.css
+++ b/src/tailwind.css
@@ -27,3 +27,86 @@ details details .large {
font-size: 0.96em !important; /* 20% bigger from 0.8em */
color: inherit !important; /* Remove test color */
}
+
+/* Make content hyperlinks blue, but keep navigation original colors */
+@layer components {
+ /* Only make content area links blue */
+ .sl-markdown-content a,
+ .starlight-aside a,
+ article a,
+ main a,
+ p a,
+ ul:not(nav ul) li a,
+ ol:not(nav ol) li a {
+ color: #3b82f6 !important; /* Tailwind blue-500 - soft blue */
+ text-decoration: none !important;
+ }
+
+ .sl-markdown-content a:hover,
+ .starlight-aside a:hover,
+ article a:hover,
+ main a:hover,
+ 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;
+ }
+}
+
+/* Explicitly keep sidebar navigation in original colors */
+@layer components {
+ nav a,
+ nav .large,
+ [data-starlight-sidebar] a,
+ [data-starlight-sidebar] .large,
+ nav[aria-labelledby="starlight__sidebar-navigation"] a,
+ nav[aria-labelledby="starlight__sidebar-navigation"] .large,
+ details summary,
+ details summary .large,
+ .sidebar a,
+ .sidebar .large {
+ color: inherit !important;
+ text-decoration: none !important;
+ }
+
+ nav a:hover,
+ [data-starlight-sidebar] a:hover,
+ nav[aria-labelledby="starlight__sidebar-navigation"] a:hover,
+ details summary:hover,
+ .sidebar a:hover {
+ color: inherit !important;
+ text-decoration: none !important;
+ }
+
+ /* Fix active/selected page visibility - make text black on white background */
+ nav a[aria-current="page"],
+ [data-starlight-sidebar] a[aria-current="page"],
+ nav[aria-labelledby="starlight__sidebar-navigation"] a[aria-current="page"],
+ .sidebar a[aria-current="page"],
+ 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 */
+ font-weight: 600 !important; /* Make it slightly bolder for better visibility */
+ }
+}
+
+/* Reusable red text utility for attention-grabbing content */
+@layer utilities {
+ .text-red-attention {
+ color: #ef4444 !important; /* Tailwind red-500 - bright but not harsh */
+ font-weight: 500 !important; /* Slightly bolder for better visibility */
+ }
+
+ .text-red-light {
+ color: #f87171 !important; /* Tailwind red-400 - lighter, softer red */
+ font-weight: 500 !important;
+ }
+
+ .text-red-soft {
+ color: #fca5a5 !important; /* Tailwind red-300 - very light, gentle red */
+ font-weight: 500 !important;
+ }
+}