Skip to content

Commit 6aa9695

Browse files
committed
fix some problems with demand signaling and add torus-portal
1 parent 9749f2a commit 6aa9695

3 files changed

Lines changed: 61 additions & 61 deletions

File tree

astro.config.mjs

Lines changed: 7 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -37,16 +37,13 @@ export default defineConfig({
3737
{
3838
label: "v0.5",
3939
items: [
40-
// { label: "Network Overview", slug: "concepts/network-overview" },
41-
{ label: "Control Space", slug: "v05/control-space" },
42-
{ label: "Permission System", slug: "v05/permissions" },
43-
{
44-
label: "Capability Permissions",
45-
slug: "v05/capability-permissions",
46-
},
47-
{ label: "Emission Permissions", slug: "v05/emission-permissions" },
48-
{ label: "Tokenomics", slug: "concepts/tokenomics" },
49-
{ label: "Governance & DAO", slug: "concepts/governance-dao" },
40+
// { label: "Network Overview", slug: "concepts/network-overview" },
41+
{ label: "Control Space", slug: "v05/control-space" },
42+
{ label: "Permission System", slug: "v05/permissions" },
43+
{ label: "Capability Permissions", slug: "v05/capability-permissions" },
44+
{ label: "Emission Permissions", slug: "v05/emission-permissions" },
45+
{ label: "Tokenomics", slug: "concepts/tokenomics" },
46+
{ label: "Governance & DAO", slug: "concepts/governance-dao" },
5047
],
5148
},
5249
{

src/content/docs/agents/demand-signaling.mdx

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,25 +21,26 @@ import {
2121

2222
### Capability demand signaling system
2323

24+
The ["create signal"](https://portal.torus.network/create-signal) feature on the Portal allows root agents to express in a technical and economical way their demand for specialized capabilities from other agents.
2425
The ["create signal"](https://portal.torus.network/create-signal) feature on the Portal allows agents to technically and economically express their demand for specialized capabilities from other agents.
2526

26-
Agents are looking for opportunities to receive emission delegations by providing specialized capabilities. This means, you can define a problem and advertise it to agents by proposing an allocation of your own emissions for it.
27+
Standard agents are looking for opportunities to receive emission delegations by providing specialized capabilities. This means, you can define a problem and increase interest in solving it by proposing an allocation of your own emissions.
2728

2829
For example, if you have an agent specializing on finding predictions for the swarm memory and your accuracy and rewards suffer by failing to filter out irony, then you could signal a demand for an irony classifier that you integrate with your agent.
2930

3031
### Suggestions
3132

3233
You can let agents sub-specialize within your problem domain, similar to how you specialize in the higher level problem domain. By delegating 5% of your emissions, you might be able to increase your incoming emissions by >10%, while lowering required work.
3334

34-
We expect agents that apply this feature effectively to outcompete agents who stay solo in rewards.
35+
We expect root agents that apply this feature effectively to outcompete root agents who stay solo in rewards.
3536

36-
The text should clearly specify the semantics & goal, as well as the expected endpoint interface. Input-output examples are helpful. We strongly recommend to use the agent API standard (insert link), which your text can just refer to. If you are using a different schema, fully specify it.
37+
The text should clearly specify the semantics & goal, as well as the expected endpoint interface. Input-output examples are helpful. We strongly recommend to use the [agent API standard](/src/content/docs/agents/agent-api-standard), which your text can just refer to. If you are using a different schema, fully specify it.
3738

3839
## Prerequisites
3940

4041
<CardGrid>
41-
<Card title="Active Agent" icon="seti:license">
42-
Your agent must be registered in Torus.
42+
<Card title="Root Agent" icon="seti:license">
43+
You must be a root agent in Torus.
4344
</Card>
4445
<Card title="Available Emissions" icon="seti:pipeline">
4546
Have any amount of incoming emission streams available.
Lines changed: 48 additions & 46 deletions
Original file line numberDiff line numberDiff line change
@@ -1,78 +1,80 @@
11
---
22
title: How to Use Torus Portal
3-
description: Complete guide to creating namespaces and managing permissions through Torus Portal.
3+
description: Quick guide to navigating and using the Torus Portal interface for permission management.
44
---
55

6-
import { Aside, Card, CardGrid, Code, Tabs, TabItem, LinkCard } from "@astrojs/starlight/components";
6+
import { Aside, CardGrid, LinkCard } from "@astrojs/starlight/components";
77

8-
Learn how to use Torus Portal to create namespaces, manage permissions, and delegate access to your agent services.
8+
Torus Portal is the web interface for managing permissions and capabilities. Use it to create delegations, register capabilities, and coordinate with other agents.
99

10-
## Overview
10+
## Interface Overview
1111

12-
Torus Portal is the interface for managing the permission system, allowing you to create namespaces and delegate permissions for off-chain services.
12+
**Main View**: The hypergraph shows all network capabilities, agents, and their connections in real-time.
1313

14-
**Key Features:**
15-
- Create and manage permissions
16-
- Register agents
17-
- Create a signal
14+
**Navigation Menu** (top-left dropdown):
15+
- **Overview** → Hypergraph (current view)
16+
- **Permissions Management** → Create/Edit permissions
17+
- **Capability Operations** → Register/Delete capabilities
18+
- **Network Operations** → Register agents, Create signals
1819

19-
## Getting Started
20+
## Creating Permissions
2021

21-
[Content to be added - accessing and connecting to Torus Portal]
22+
**Permissions Management → Create Permission**
2223

23-
the first thing that shows when you open the page is the hypergraph, which is a graph of all the capabilities and agents interacting with those capabilities in the network, together with emission permissions etc.
24+
1. **Choose Type**: Emission or Capability permission (top-right selector)
25+
2. **Fill Form**: Configure delegator, recipient, scope, duration
26+
3. **Submit**: Create the permission
2427

25-
## Permissions
28+
For permission details, see [Emission Permissions](/advanced/emission-permissions) and [Capability Permissions](/advanced/namespace-permissions).
2629

27-
[Content to be added - how to create and manage different types of permissions]
30+
## Managing Capabilities
2831

29-
on the top left of the site, there is a button that at first will be written as "hypergraph", which is the current page you are on. after clicking it, it will show a dropdown with the following options:
32+
**Capability Operations → Register Capability**
3033

31-
- Overview
32-
- Hypergraph
33-
- Permissions Management
34-
- Create permission
35-
- Edit permission
36-
- Capability operations
37-
- Register capability
38-
- Delete capability
39-
- Network operations
40-
- Register agent
41-
- Create signal
34+
1. **Namespace Path**: Enter your capability path (e.g., `agent.alice.memory.store`)
35+
2. **REST Method**: Select HTTP method (`GET`, `POST`, etc.)
36+
3. **Submit**: Register the capability
4237

43-
to create a permission, you need to click on the "Create permission" button, which will take you to the "Create permission" form.
38+
**Capability Operations → Delete Capability**
4439

45-
there you can choose on the top right of the form the type of permission you want to create, either capability or emission, and then you can fill in the form with the required fields.
40+
1. **Select Path**: Choose capability to delete
41+
2. **Choose Granularity**: Delete specific method or entire capability
42+
3. **Confirm**: Delete (only works if no active delegations exist)
4643

47-
to edit a permission, you need to click on the "Edit permission" button, which will take you to the "Edit permission" form, there you can also "revoke" the permission (if revocable).
44+
For namespace concepts, see [Namespaces](../v05/permissions.mdx).
4845

49-
## Creating a capability
46+
## Network Operations
5047

51-
to create a capability, you need to click on the "Register capability" button, which will take you to the "Register capability" form, there you choose the path of your namespace, as well as the REST method you want to create the capability for.
48+
**Register Agent**: Basic agent registration (different from [root agent registration](../agents/apply-root-agent.mdx))
5249

53-
to delete the capability, you need to click on the "Delete capability" button, which will take you to the "Delete capability" form, there, you can choose the permission path you want to delete, and granularly delete a specific capability or REST method. but before trying to delete, make sure that that capability is not being delegated, otherwise you will not be able to delete it.
50+
**Create Signal**: Broadcast coordination messages to other agents in the network
5451

55-
## Register an agent
52+
## Editing Permissions
5653

57-
[Content to be added - how to register an agent]
54+
**Permissions Management → Edit Permission**
5855

59-
to register an agent, you need to click on the "Register agent" button, which will take you to the "Register agent" form, there you can fill in the form with the required fields. keep notice, this registration is not the same as [root agent registration](../agents/register-root-agent.mdx).
56+
- Modify existing permissions within original contract terms
57+
- Revoke permissions (if revocable)
58+
- Some changes may require recipient consent
6059

61-
## Create a signal
62-
63-
[Content to be added - how to create a signal]
64-
65-
to create a signal, you need to click on the "Create signal" button, which will take you to the "Create signal" form, there you can fill in the form with the required fields.
60+
<Aside type="note">
61+
Always check dependency warnings before deleting capabilities - you cannot delete capabilities with active delegations.
62+
</Aside>
6663

6764
<CardGrid>
6865
<LinkCard
69-
title="Namespaces"
70-
href="/advanced/namespaces"
71-
description="Understand namespace concepts and architecture."
66+
title="Emission Permissions"
67+
href="/advanced/emission-permissions"
68+
description="Learn about token delegation mechanics"
7269
/>
7370
<LinkCard
74-
title="Permissions System"
75-
href="/advanced/permissions"
76-
description="Learn about the permission system and delegation."
71+
title="Capability Permissions"
72+
href="/advanced/namespace-permissions"
73+
description="Understand service access control"
74+
/>
75+
<LinkCard
76+
title="Namespaces"
77+
href="/advanced/namespaces"
78+
description="Namespace structure and concepts"
7779
/>
7880
</CardGrid>

0 commit comments

Comments
 (0)