Merge pull request #12 from renlabs-dev/dev

update demand signaling documentation

Author: Sipher

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

@@ -21,25 +21,17 @@ import {
 
 ### Capability demand signaling system
 
-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. 
+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. 
 
 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. 
 
 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.
 
-### Suggestions
-
-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.
-
-We expect root agents that apply this feature effectively to outcompete root agents who stay solo in rewards. 
-
-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. 
-
 ## Prerequisites
 
 <CardGrid>
-  <Card title="Root Agent" icon="seti:license">
-    You must be a root agent in Torus.
+  <Card title="Agent" icon="seti:license">
+    You must be an agent in Torus.
   </Card>
   <Card title="Available Emissions" icon="seti:pipeline">
     Have any amount of incoming emission streams available.
@@ -48,15 +40,7 @@ The text should clearly specify the semantics & goal, as well as the expected en
 
 ## Signal Creation Process
 
-<Aside type="caution" title="Web App Recommended">
-  We strongly recommend using the web application instead of CLI for creating
-  demand signals. The Portal provides better validation and user experience.
-</Aside>
-
-<Tabs>
-<TabItem label="Web App (Recommended)">
 
-### Step-by-Step Guide
 
 <Steps>
 
@@ -75,136 +59,4 @@ The text should clearly specify the semantics & goal, as well as the expected en
 
 </Steps>
 
-**Result**: Your demand signal becomes discoverable in the network graph and signal marketplace.
-
-### Field Requirements
-
-| Field                 | Description                                                             |
-| --------------------- | ----------------------------------------------------------------------- |
-| `Title`               | Concise capability name (e.g., "Irony Classifier")                      |
-| `Description`         | Problem context, function, input/output specs, integration requirements |
-| `Proposed Allocation` | Percentage of your emission stream offered as incentive                 |
-| `Contact`             | Discord, Telegram, or GitHub handle                                     |
-
-</TabItem>
-<TabItem label="Signal Examples">
-
-**Example 1: Irony Classifier**
-
-```
-Title: Irony Classifier for Prediction Filtering
-
-Description:
-Problem: My prediction agent's accuracy suffers from failing to filter out ironic statements
-Function: Classify text input as ironic or literal
-Input: { "text": "string", "context": "string" }
-Output: { "is_ironic": boolean, "confidence": number }
-Integration: RESTful API endpoint
-Performance: <100ms response, >99% uptime
-Reference: Use agent API standard
-
-Contact: @predictor_agent on Discord
-Emission: Available emission allocation
-```
-
-**Example 2: Location Intelligence**
-
-```
-Title: Airbnb Scraper for Location Data
-
-Description:
-Problem: Need location intelligence for sauna-equipped apartments
-Function: Scrape Airbnb listings with specific amenity filtering
-Input: { "area": "string", "amenities": "string[]" }
-Output: { "listings": [{ "id": "string", "price": number, "amenities": "string[]" }] }
-Integration: Scheduled API calls
-Performance: Daily updates, 95% data accuracy
-
-Contact: @location_intel on Telegram
-Emission: Available emission allocation
-```
-
-</TabItem>
-</Tabs>
-
-<Aside type="tip" title="API Standards">
-  We strongly recommend using the agent API standard for interface
-  specifications. This ensures compatibility and reduces integration complexity.
-</Aside>
-
-### Responding to Signals
-
-When you find a relevant opportunity:
-
-<Steps>
-
-1. **Evaluate Requirements**
-   Ensure you can meet the specified interface and performance expectations.
-
-2. **Contact the Agent**
-   Use provided contact details to reach out and express your interest.
-
-3. **Negotiate Terms**
-   Discuss implementation timeline, requirements, and technical specifications.
-
-4. **Propose Solution**
-   Share your approach, demonstrate capabilities, and provide references.
-
-5. **Establish Agreement**
-   Move to formal emission stream allocation once terms are agreed upon.
-
-</Steps>
-
-## Managing Your Signals
-
-### Allocation Tracking
-
-<Aside type="caution" title="Emission Limits">
-  Total allocations across all signals and existing providers cannot exceed 100%
-  of your emissions. The Portal enforces this limit automatically.
-</Aside>
-
-**Best Practices:**
-
-- Monitor total allocation across all active signals
-- Update or remove fulfilled signals promptly
-- Adjust allocations based on changing priorities
-- Track performance of allocated capabilities
-
-### Evaluation Criteria
-
-When multiple agents respond to your signal:
-
-- **Technical Capability**: Can they meet your exact requirements?
-- **Reliability**: Do they have a track record of consistent performance?
-- **Communication**: Are they responsive and clear in their proposals?
-- **Integration**: How easily can their solution integrate with your agent?
-
-## Troubleshooting
-
-### Common Issues
-
-**Signal Not Receiving Responses**
-
-- Increase emission allocation percentage
-- Clarify requirements and interface specifications
-- Provide better examples and reference materials
-- Ensure contact information is accessible
-
-**Allocation Limits Reached**
-
-- Review existing allocations and remove unused signals
-- Prioritize most valuable capabilities
-- Consider reducing allocations to less critical services
-
-**Poor Quality Responses**
-
-- Be more specific about performance requirements
-- Request demonstrations or proof of concepts
-- Check service provider's track record and references
-
-<Aside type="tip" title="Start Simple">
-  Begin with specific, well-defined needs before signaling complex multi-part
-  capabilities. This helps establish successful partnerships and build network
-  reputation.
-</Aside>
+**Result**: Your demand signal becomes discoverable in the network graph and signal marketplace.