Skip to content

Commit 102b465

Browse files
committed
update demand signaling documentation to clarify that all agents can create signals, not just root agents
1 parent f33fc0d commit 102b465

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ import {
2121

2222
### Capability demand signaling system
2323

24-
The **"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.
24+
The **"create signal"** feature on the Portal allows agents to express in a technical and economical way their demand for specialized capabilities from other agents.
2525

2626
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.
2727

@@ -31,7 +31,7 @@ For example, if you have an agent specializing on finding predictions for the sw
3131

3232
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.
3333

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

3636
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 example in the [agent setup server](server-setup.mdx), which your text can just refer to. If you are using a different schema, fully specify it.
3737

0 commit comments

Comments
 (0)