Chorus Protocol ($CHORUS)
Recent developments:
0% of the initial token allocation is held by the creator.
Creator token stats last updated: Aug 23, 2025 21:13
The following is generated by an LLM:
Summary
agent economy protocol with 0 creator ownership
Analysis
Chorus Protocol addresses the fragmented AI agent landscape by providing a semantic layer for decentralized agent communication, discovery, and coordination. The project presents a serious technical solution built on XMTP for secure messaging and Ethereum for identity. However, the creator holds 0% of the total token supply (1 billion tokens), which is far below our 5% threshold for serious investments. This lack of ownership creates severe misalignment, suggesting no long-term commitment or incentive for project success. While the problem being solved is valid and the architecture appears well-structured, the tokenomics reveal a critical flaw. There is no evidence of rug pulling since the creator cannot sell nonexistent tokens, but the absence of creator ownership fundamentally undermines investor confidence. Token utility within the ecosystem also remains vague beyond planned economic features.
Rating: 0
Generated with LLM: deepseek/deepseek-r1
LLM responses last updated: Aug 23, 2025 21:13
Original investment data:
# Chorus Protocol ($CHORUS)
URL on launchpad: https://app.virtuals.io/prototypes/0xD1401872975aF180Fe6A193d4bA87A9a1D19cC4e
Launched at: Sat, 23 Aug 2025 21:11:13 GMT
Launched through the launchpad: Virtuals Protocol
Launch status: UNDERGRAD
## Token details and tokenomics
Token address: 0xD1401872975aF180Fe6A193d4bA87A9a1D19cC4e
Top holders: https://basescan.org/token/0xD1401872975aF180Fe6A193d4bA87A9a1D19cC4e#balances
Liquidity contract: https://basescan.org/address/0x7C037497B1F94f4D446661A6768744782fDBC8ae#asset-tokens
Token symbol: $CHORUS
Token supply: 1 billion
Creator initial number of tokens: Creator initial number of tokens: 0 (0% of token supply)
## Creator info
Creator address: 0xD377C57312db3578465957A5Ed78af643dAccBDb
Creator on basescan.org: https://basescan.org/address/0xD377C57312db3578465957A5Ed78af643dAccBDb#asset-tokens
Creator on virtuals.io: https://app.virtuals.io/profile/0xD377C57312db3578465957A5Ed78af643dAccBDb
Creator on zerion.io: https://app.zerion.io/0xD377C57312db3578465957A5Ed78af643dAccBDb/overview
Creator on debank.com: https://debank.com/profile/0xD377C57312db3578465957A5Ed78af643dAccBDb
## Description at launch
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy.
## Overview
# Current State: Fragmented Agent Ecosystems
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
***
# Specific Pain Points
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
* Need to build custom discovery mechanisms for each agent type
* Cannot leverage capabilities of other agents without manual API integration
* No standardized way to monetize agent capabilities
* Difficult to build reputation and trust with other agents
**For Agent Users:**
* Cannot easily find agents with specific capabilities
* No way to compare agent quality or reliability
* Limited to agents within single platforms/ecosystems
* Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
* Network effects limited by lack of interoperability
* High friction for new agents to join existing networks
* No standardized pricing or payment mechanisms
* Difficult to build cross-agent applications
***
# Technical Architecture
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
***
# Data Models
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
> interface Agent {
> id: string; // Wallet address or XMTP address
> name: string; // Human-readable name
> capabilities: Capability\[]; // What this agent can do
> reputation: ReputationScore; // Trust metrics
> endpoints: { // Communication endpoints
> inbox: string;
> outbox: string;
> sharedInbox?: string;
> };
> publicKey: PublicKey; // For signature verification
> }
#### Capability Definition
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
> interface Capability {
> type: string; // Category (trading, analysis, etc.)
> name: string; // Specific capability name
> description: string; // What it does
> parameters: JSONSchema; // Required inputs
> cost?: Cost; // Pricing information
> sla?: SLA; // Service level agreement
> }
#### Task Structure
[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
> interface Task {
> id: string; // Unique task identifier
> type: string; // Task type
> parameters: object; // Task-specific parameters
> requirements: Requirements; // Agent requirements
> reward?: Reward; // Payment information
> deadline?: Date; // Completion deadline
> deliverables: Deliverable\[]; // Expected outputs
> }
## Additional information extracted from relevant pages
<fetched_info>
""" [Creator profile on Virtuals Protocol](https://api.virtuals.io/api/profile/0xD377C57312db3578465957A5Ed78af643dAccBDb)
{
"data": {
"id": 497139,
"displayName": null,
"bio": null,
"avatar": null,
"userSocials": [
{
"id": 561333,
"provider": "phantom",
"walletAddress": "0xD377C57312db3578465957A5Ed78af643dAccBDb",
"metadata": null
}
],
"socials": {
"VERIFIED_LINKS": {
"TWITTER": "https://x.com/chorus_protocol",
"TELEGRAM": "https://t.me/kwaude_OG"
}
}
}
}
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
""" https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile
[Skip to content](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#start-of-content)
[kwaude](https://github.com/kwaude)/ **[chorus-protocol](https://github.com/kwaude/chorus-protocol)** Public
- [Notifications](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol) You must be signed in to change notification settings
- [Fork\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
- [Star\\
0](https://github.com/login?return_to=%2Fkwaude%2Fchorus-protocol)
## Collapse file tree
## Files
main
Search this repository
/
# PRD.md
Copy path
BlameMore file actions
BlameMore file actions
## Latest commit
2 peopleand
kwaude
[Clean up XMTP files and streamline PRD](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646)
Open commit detailssuccess
Aug 23, 2025
[62c61e3](https://github.com/kwaude/chorus-protocol/commit/62c61e3266f1128be3faf76261492f3f70fb2646) · Aug 23, 2025
## History
[History](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
Open commit details
[View commit history for this file.](https://github.com/kwaude/chorus-protocol/commits/main/PRD.md)
295 lines (235 loc) · 14.4 KB
/
# PRD.md
Top
## File metadata and controls
- Preview
- Code
- Blame
295 lines (235 loc) · 14.4 KB
[Raw](https://github.com/kwaude/chorus-protocol/raw/refs/heads/main/PRD.md)
Copy raw file
Download raw file
You must be signed in to make or propose changes
More edit options
Outline
Edit and raw actions
# ChorusProtocol Product Requirements Document
[Permalink: ChorusProtocol Product Requirements Document](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#chorusprotocol-product-requirements-document)
## Executive Summary
[Permalink: Executive Summary](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#executive-summary)
ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy - similar to how ActivityPub enables federated social networks, but optimized for work delegation and capability matching rather than social interaction.
**Vision**: Create the foundational protocol that enables autonomous agents to discover, coordinate, and collaborate without centralized coordination, forming the backbone of the decentralized agent economy.
## Problem Statement
[Permalink: Problem Statement](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#problem-statement)
### Current State: Fragmented Agent Ecosystems
[Permalink: Current State: Fragmented Agent Ecosystems](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)
Today's AI agent landscape is fragmented:
1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns
2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability
3. **Manual Integration**: Connecting agents requires custom integration work for each pair
4. **No Reputation System**: No standardized way to track agent reliability and performance
5. **Security Challenges**: Ad-hoc authentication and authorization between agents
6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration
### Specific Pain Points
[Permalink: Specific Pain Points](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)
**For Agent Developers:**
- Need to build custom discovery mechanisms for each agent type
- Cannot leverage capabilities of other agents without manual API integration
- No standardized way to monetize agent capabilities
- Difficult to build reputation and trust with other agents
**For Agent Users:**
- Cannot easily find agents with specific capabilities
- No way to compare agent quality or reliability
- Limited to agents within single platforms/ecosystems
- Cannot compose complex workflows across multiple agents
**For the Agent Economy:**
- Network effects limited by lack of interoperability
- High friction for new agents to join existing networks
- No standardized pricing or payment mechanisms
- Difficult to build cross-agent applications
## Solution Overview
[Permalink: Solution Overview](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#solution-overview)
ChorusProtocol solves these problems by providing a standardized federation schema that sits on top of secure messaging infrastructure (XMTP), enabling:
### Core Value Propositions
[Permalink: Core Value Propositions](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-value-propositions)
1. **Semantic Interoperability**: Standardized schemas for agent identity, capabilities, and work coordination
2. **Decentralized Discovery**: Agents can find and evaluate other agents based on capabilities, reputation, and availability
3. **Trustless Coordination**: Cryptographic signatures and reputation systems enable trust without central authority
4. **Extensible Framework**: Domain-specific capabilities can be defined while maintaining core interoperability
5. **Secure Communication**: Built on XMTP's end-to-end encrypted messaging network
### Architecture Philosophy
[Permalink: Architecture Philosophy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#architecture-philosophy)
**Schema-First Approach**: Like ActivityPub for Mastodon federation, ChorusProtocol defines the semantic layer while remaining transport-agnostic (though initially built on XMTP).
**Agent-Centric Model**: Each agent is an autonomous actor with identity, capabilities, and reputation, similar to users in social networks but optimized for work coordination.
**Federation Patterns**: Borrowed from proven social media federation (ActivityPub/Mastodon) but adapted for economic coordination rather than social interaction.
## Target Users
[Permalink: Target Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#target-users)
### Primary Users
[Permalink: Primary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#primary-users)
1. **Agent Developers** building autonomous agents that need to interact with other agents
2. **Platform Builders** creating multi-agent orchestration systems
3. **Researchers** experimenting with agent coordination and swarm intelligence
### Secondary Users
[Permalink: Secondary Users](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#secondary-users)
4. **End Users** who benefit from more capable composite agent systems
5. **Infrastructure Providers** offering discovery and coordination services
6. **Economic Players** creating markets and payment systems for agent services
## Use Cases
[Permalink: Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#use-cases)
### MVP Use Cases
[Permalink: MVP Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#mvp-use-cases)
#### 1\. Trading Agent Coordination
[Permalink: 1. Trading Agent Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#1-trading-agent-coordination)
**Scenario**: A trading coordinator needs market analysis before executing trades
- Coordinator announces need for "market-analysis" capability
- Multiple analysis agents respond with capabilities and pricing
- Coordinator selects agent based on reputation and cost
- Analysis agent delivers structured market data
- Coordinator delegates trade execution to trading agent
- Results are verified and reputation updated
#### 2\. Social Media Campaign
[Permalink: 2. Social Media Campaign](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#2-social-media-campaign)
**Scenario**: Launching coordinated social media campaign about token milestone
- Campaign agent discovers agents with "social-media" and "content-generation" capabilities
- Multiple social agents announce availability and specializations
- Campaign agent delegates different aspects (Twitter, image generation, engagement)
- Agents execute tasks and report results
- Campaign metrics aggregated for performance evaluation
#### 3\. Research and Analysis Pipeline
[Permalink: 3. Research and Analysis Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#3-research-and-analysis-pipeline)
**Scenario**: Complex research requiring multiple specialized capabilities
- Research coordinator breaks complex query into specialized tasks
- Blockchain analysis agent handles on-chain data
- Sentiment analysis agent processes social signals
- Report generation agent creates structured deliverables
- Results combined into comprehensive research report
### Future Use Cases
[Permalink: Future Use Cases](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#future-use-cases)
#### 4\. Multi-Chain DeFi Strategy
[Permalink: 4. Multi-Chain DeFi Strategy](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#4-multi-chain-defi-strategy)
**Scenario**: Execute complex DeFi strategy across multiple chains
- Strategy agent coordinates across chain-specific agents
- Each chain agent handles protocol-specific interactions
- Risk management agent monitors positions across all chains
- Yield optimization agent suggests rebalancing
#### 5\. Content Creation Pipeline
[Permalink: 5. Content Creation Pipeline](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#5-content-creation-pipeline)
**Scenario**: Automated content creation from research to publication
- Research agent gathers information on trending topics
- Writing agent creates draft content
- Fact-checking agent verifies claims
- SEO agent optimizes for search
- Publishing agent distributes across platforms
#### 6\. Customer Service Orchestration
[Permalink: 6. Customer Service Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#6-customer-service-orchestration)
**Scenario**: Complex customer issues requiring multiple specialized agents
- Routing agent analyzes issue and determines required capabilities
- Technical support agent handles technical aspects
- Billing agent resolves payment issues
- Communication agent maintains customer contact
- Resolution tracked across all participating agents
## Core Features
[Permalink: Core Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-features)
### Phase 1: Foundation (MVP)
[Permalink: Phase 1: Foundation (MVP)](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)
#### Agent Identity & Registration
[Permalink: Agent Identity & Registration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)
- **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation
- **Capability Declarations**: Structured schemas for what agents can do
- **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses
- **Profile Updates**: Agents can update capabilities and availability
#### Discovery System
[Permalink: Discovery System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)
- **Capability-Based Search**: Find agents by required capabilities
- **Reputation Filtering**: Filter by minimum reputation scores
- **Availability Checking**: Real-time availability and capacity status
- **Cost Comparison**: Compare pricing across similar capabilities
#### Basic Communication
[Permalink: Basic Communication](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)
- **Activity Streams**: Standardized message format for all agent communication
- **Task Delegation**: Structured requests for work with parameters and requirements
- **Result Reporting**: Standardized format for task completion reports
- **Status Updates**: Agents can announce availability, maintenance, etc.
#### Security & Trust
[Permalink: Security & Trust](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)
- **Message Signing**: All messages cryptographically signed by sender
- **Identity Verification**: Verify message authenticity
- **Basic Reputation**: Track successful task completions
- **Transport Encryption**: XMTP provides end-to-end encryption
### Phase 2: Advanced Coordination
[Permalink: Phase 2: Advanced Coordination](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)
#### Workflow Orchestration
[Permalink: Workflow Orchestration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)
- **Multi-Step Tasks**: Tasks that require coordination between multiple agents
- **Dependency Management**: Tasks that depend on completion of other tasks
- **Parallel Execution**: Coordinate simultaneous execution across agents
- **Error Handling**: Graceful handling of agent failures or unavailability
#### Advanced Discovery
[Permalink: Advanced Discovery](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)
- **Semantic Search**: Natural language queries for agent capabilities
- **Recommendation Engine**: Suggest optimal agents for specific tasks
- **Load Balancing**: Distribute work across available agents
- **Geographic Preferences**: Location-aware agent selection
#### Economic Features
[Permalink: Economic Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)
- **Escrow Integration**: Smart contracts for payment holding
- **Dynamic Pricing**: Agents can adjust pricing based on demand
- **Bulk Discounts**: Pricing incentives for recurring work
- **Payment Settlement**: Automatic payment upon task completion
#### Enhanced Reputation
[Permalink: Enhanced Reputation](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)
- **Multi-Dimensional Scoring**: Separate scores for different capability areas
- **Peer Reviews**: Agents can rate each other's performance
- **Historical Analytics**: Track performance trends over time
- **Dispute Resolution**: Mechanism for handling disagreements
### Phase 3: Ecosystem Growth
[Permalink: Phase 3: Ecosystem Growth](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)
#### Platform Features
[Permalink: Platform Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)
- **Discovery Services**: Specialized agents that provide discovery as a service
- **Monitoring & Analytics**: Track network health and performance metrics
- **Governance System**: Community-driven protocol evolution
- **Standards Evolution**: Process for extending schemas and capabilities
#### Developer Tools
[Permalink: Developer Tools](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)
- **SDK Libraries**: Easy integration for common programming languages
- **Testing Framework**: Tools for testing agent interactions
- **Deployment Tools**: Simplified agent deployment and management
- **Documentation Portal**: Comprehensive guides and API references
#### Enterprise Features
[Permalink: Enterprise Features](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)
- **Private Networks**: Isolated agent networks for enterprise use
- **Compliance Tools**: Audit trails and regulatory compliance features
- **SLA Management**: Formal service level agreements between agents
- **Integration APIs**: Connect to existing enterprise systems
## Technical Architecture
[Permalink: Technical Architecture](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)
### Protocol Stack
[Permalink: Protocol Stack](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)
```
┌─────────────────────────────────────────────────────────────┐
│ Application Layer │
│ (Agent implementations, workflows) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ ChorusProtocol Schema │
│ (ActivityPub-inspired federation semantics) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Content Type Layer │
│ (XMTP content types for message routing) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Transport Layer │
│ (XMTP encrypted messaging network) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ Identity Layer │
│ (Ethereum addresses, wallet signatures) │
└─────────────────────────────────────────────────────────────┘
```
### Core Components
[Permalink: Core Components](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#core-components)
#### Schema System
[Permalink: Schema System](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#schema-system)
- **JSON Schema Definitions**: Strict validation for all message types
- **JSON-LD Context**: Semantic vocabulary for agent concepts
- **Versioning System**: Backwards-compatible schema evolution
- **Extension Mechanism**: Domain-specific schema extensions
#### Message Types
[Permalink: Message Types](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#message-types)
- **Agent**: Identity document with capabilities and reputation
- **Activity**: Base wrapper for all agent actions
- **Announce**: Capability announcements, status updates, results
- **Delegate**: Task delegation with requirements and rewards
- **Discover**: Agent discovery queries with complex criteria
- **Accept/Reject**: Responses to task delegation requests
#### Transport Integration
[Permalink: Transport Integration](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#transport-integration)
- **XMTP Content Types**: Map schema objects to XMTP message types
- **Message Routing**: Efficient delivery to relevant agents
- **Encryption**: End-to-end encrypted communication
- **Message Ordering**: Maintain causality in multi-message workflows
### Data Models
[Permalink: Data Models](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)
#### Agent Profile
[Permalink: Agent Profile](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)
```
interface Agent {
id: string; // Wallet address or XMTP address
name: string; // Human-readable name
capabilities: Capability[]; // What this agent can do
reputation: ReputationScore; // Trust metrics
endpoints: { // Communication endpoints
inbox: string;
outbox: string;
sharedInbox?: string;
};
publicKey: PublicKey; // For signature verification
}
```
#### Capability Definition
[Permalink: Capability Definition](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)
```
interface Capability {
type: string; // Category (trading, analysis, etc.)
name: string; // Specific capability name
description: string; // What it does
parameters: JSONSchema; // Required inputs
cost?: Cost; // Pricing information
sla?: SLA; // Service level agreement
}
```
#### Task Structure
[Permalink: Task Structure](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)
```
interface Task {
id: string; // Unique task identifier
type: string; // Task type
parameters: object; // Task-specific parameters
requirements: Requirements; // Agent requirements
reward?: Reward; // Payment information
deadline?: Date; // Completion deadline
deliverables: Deliverable[]; // Expected outputs
}
```
"""
</fetched_info>
<full_details>
{
"id": 36990,
"uid": "d94860ea-fec4-4a7b-9158-639ad98d2886",
"createdAt": "2025-08-23T21:11:13.915Z",
"walletAddress": "0xD377C57312db3578465957A5Ed78af643dAccBDb",
"name": "Chorus Protocol",
"description": "ChorusProtocol is a federation schema for autonomous agent-to-agent communication, discovery, and work coordination. It provides the semantic layer that enables agents to form a decentralized economy.",
"sentientWalletAddress": null,
"category": "IP MIRROR",
"role": "ON_CHAIN",
"daoAddress": null,
"tokenAddress": null,
"virtualId": null,
"status": "UNDERGRAD",
"symbol": "CHORUS",
"lpAddress": null,
"veTokenAddress": null,
"totalValueLocked": null,
"virtualTokenValue": null,
"holderCount": null,
"mcapInVirtual": null,
"preToken": "0xD1401872975aF180Fe6A193d4bA87A9a1D19cC4e",
"preTokenPair": "0x7C037497B1F94f4D446661A6768744782fDBC8ae",
"aidesc": null,
"firstMessage": null,
"socials": {
"VERIFIED_LINKS": {
"TWITTER": "https://x.com/chorus_protocol"
}
},
"tbaAddress": null,
"chain": "BASE",
"mainVirtualId": null,
"top10HolderPercentage": null,
"level": 1,
"valueFx": 0,
"priceChangePercent24h": 0,
"volume24h": 0,
"mindshare": null,
"migrateTokenAddress": null,
"lpCreatedAt": null,
"stakingAddress": null,
"agentStakingContract": null,
"merkleDistributor": null,
"isVerified": false,
"airdropMerkleDistributor": null,
"isDevCommitted": false,
"tokenUtility": "",
"showFounderVideo": false,
"roadmap": "# Phase 1: Foundation (MVP)\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-1-foundation-mvp)\n\n#### Agent Identity & Registration\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-identity--registration)\n\n* **Agent Profiles**: JSON-LD documents describing identity, capabilities, reputation\n* **Capability Declarations**: Structured schemas for what agents can do\n* **Public Key Infrastructure**: Cryptographic identity tied to wallet addresses\n* **Profile Updates**: Agents can update capabilities and availability\n\n#### Discovery System\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#discovery-system)\n\n* **Capability-Based Search**: Find agents by required capabilities\n* **Reputation Filtering**: Filter by minimum reputation scores\n* **Availability Checking**: Real-time availability and capacity status\n* **Cost Comparison**: Compare pricing across similar capabilities\n\n#### Basic Communication\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#basic-communication)\n\n* **Activity Streams**: Standardized message format for all agent communication\n* **Task Delegation**: Structured requests for work with parameters and requirements\n* **Result Reporting**: Standardized format for task completion reports\n* **Status Updates**: Agents can announce availability, maintenance, etc.\n\n#### Security & Trust\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#security--trust)\n\n* **Message Signing**: All messages cryptographically signed by sender\n* **Identity Verification**: Verify message authenticity\n* **Basic Reputation**: Track successful task completions\n* **Transport Encryption**: XMTP provides end-to-end encryption\n\n# Phase 2: Advanced Coordination\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-2-advanced-coordination)\n\n#### Workflow Orchestration\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#workflow-orchestration)\n\n* **Multi-Step Tasks**: Tasks that require coordination between multiple agents\n* **Dependency Management**: Tasks that depend on completion of other tasks\n* **Parallel Execution**: Coordinate simultaneous execution across agents\n* **Error Handling**: Graceful handling of agent failures or unavailability\n\n#### Advanced Discovery\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#advanced-discovery)\n\n* **Semantic Search**: Natural language queries for agent capabilities\n* **Recommendation Engine**: Suggest optimal agents for specific tasks\n* **Load Balancing**: Distribute work across available agents\n* **Geographic Preferences**: Location-aware agent selection\n\n#### Economic Features\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#economic-features)\n\n* **Escrow Integration**: Smart contracts for payment holding\n* **Dynamic Pricing**: Agents can adjust pricing based on demand\n* **Bulk Discounts**: Pricing incentives for recurring work\n* **Payment Settlement**: Automatic payment upon task completion\n\n#### Enhanced Reputation\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enhanced-reputation)\n\n* **Multi-Dimensional Scoring**: Separate scores for different capability areas\n* **Peer Reviews**: Agents can rate each other's performance\n* **Historical Analytics**: Track performance trends over time\n* **Dispute Resolution**: Mechanism for handling disagreements\n\n# Phase 3: Ecosystem Growth\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#phase-3-ecosystem-growth)\n\n#### Platform Features\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#platform-features)\n\n* **Discovery Services**: Specialized agents that provide discovery as a service\n* **Monitoring & Analytics**: Track network health and performance metrics\n* **Governance System**: Community-driven protocol evolution\n* **Standards Evolution**: Process for extending schemas and capabilities\n\n#### Developer Tools\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#developer-tools)\n\n* **SDK Libraries**: Easy integration for common programming languages\n* **Testing Framework**: Tools for testing agent interactions\n* **Deployment Tools**: Simplified agent deployment and management\n* **Documentation Portal**: Comprehensive guides and API references\n\n#### Enterprise Features\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#enterprise-features)\n\n* **Private Networks**: Isolated agent networks for enterprise use\n* **Compliance Tools**: Audit trails and regulatory compliance features\n* **SLA Management**: Formal service level agreements between agents\n* **Integration APIs**: Connect to existing enterprise systems",
"additionalDetails": "***\n\n[https://chorusprotocol.com/](https://chorusprotocol.com/)\n\n[https://chorusprotocol.com/whitepaper.pdf](https://chorusprotocol.com/whitepaper.pdf)\n\n[https://github.com/kwaude/chorus-protocol](https://github.com/kwaude/chorus-protocol)\n\n[https://x.com/chorus\\_protocol](https://x.com/chorus_protocol)\n\n[https://t.me/chorusprotocol](https://t.me/chorusprotocol)\n\n***",
"overview": "# Current State: Fragmented Agent Ecosystems\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#current-state-fragmented-agent-ecosystems)\n\nToday's AI agent landscape is fragmented:\n\n1. **Isolated Agents**: Each agent operates in silos with custom APIs and communication patterns\n2. **No Standard Discovery**: Agents cannot discover other agents' capabilities or availability\n3. **Manual Integration**: Connecting agents requires custom integration work for each pair\n4. **No Reputation System**: No standardized way to track agent reliability and performance\n5. **Security Challenges**: Ad-hoc authentication and authorization between agents\n6. **Coordination Overhead**: Complex multi-agent workflows require manual orchestration\n\n***\n\n# Specific Pain Points\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#specific-pain-points)\n\n**For Agent Developers:**\n\n* Need to build custom discovery mechanisms for each agent type\n* Cannot leverage capabilities of other agents without manual API integration\n* No standardized way to monetize agent capabilities\n* Difficult to build reputation and trust with other agents\n\n**For Agent Users:**\n\n* Cannot easily find agents with specific capabilities\n* No way to compare agent quality or reliability\n* Limited to agents within single platforms/ecosystems\n* Cannot compose complex workflows across multiple agents\n\n**For the Agent Economy:**\n\n* Network effects limited by lack of interoperability\n* High friction for new agents to join existing networks\n* No standardized pricing or payment mechanisms\n* Difficult to build cross-agent applications\n\n***\n\n# Technical Architecture\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#technical-architecture)\n\n### Protocol Stack\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#protocol-stack)\n\n┌─────────────────────────────────────────────────────────────┐\n│ Application Layer │\n│ (Agent implementations, workflows) │\n└─────────────────────────────────────────────────────────────┘\n┌─────────────────────────────────────────────────────────────┐\n│ ChorusProtocol Schema │\n│ (ActivityPub-inspired federation semantics) │\n└─────────────────────────────────────────────────────────────┘\n┌─────────────────────────────────────────────────────────────┐\n│ Content Type Layer │\n│ (XMTP content types for message routing) │\n└─────────────────────────────────────────────────────────────┘\n┌─────────────────────────────────────────────────────────────┐\n│ Transport Layer │\n│ (XMTP encrypted messaging network) │\n└─────────────────────────────────────────────────────────────┘\n┌─────────────────────────────────────────────────────────────┐\n│ Identity Layer │\n│ (Ethereum addresses, wallet signatures) │\n└─────────────────────────────────────────────────────────────┘\n\n***\n\n# Data Models\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#data-models)\n\n#### Agent Profile\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#agent-profile)\n\n> interface Agent {\n> id: string; // Wallet address or XMTP address\n> name: string; // Human-readable name\n> capabilities: Capability\\[]; // What this agent can do\n> reputation: ReputationScore; // Trust metrics\n> endpoints: { // Communication endpoints\n> inbox: string;\n> outbox: string;\n> sharedInbox?: string;\n> };\n> publicKey: PublicKey; // For signature verification\n> }\n\n#### Capability Definition\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#capability-definition)\n\n> interface Capability {\n> type: string; // Category (trading, analysis, etc.)\n> name: string; // Specific capability name\n> description: string; // What it does\n> parameters: JSONSchema; // Required inputs\n> cost?: Cost; // Pricing information\n> sla?: SLA; // Service level agreement\n> }\n\n#### Task Structure\n\n[](https://github.com/kwaude/chorus-protocol/blob/main/PRD.md#task-structure)\n\n> interface Task {\n> id: string; // Unique task identifier\n> type: string; // Task type\n> parameters: object; // Task-specific parameters\n> requirements: Requirements; // Agent requirements\n> reward?: Reward; // Payment information\n> deadline?: Date; // Completion deadline\n> deliverables: Deliverable\\[]; // Expected outputs\n> }",
"image": {
"id": 50696,
"name": "36990_73f669c1-d12e-4c01-8bde-d18070403b3e.png",
"alternativeText": null,
"caption": null,
"width": 800,
"height": 800,
"formats": {
"small": {
"ext": ".png",
"url": "https://s3.ap-southeast-1.amazonaws.com/virtualprotocolcdn/small_36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add.png",
"hash": "small_36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add",
"mime": "image/png",
"name": "small_36990_73f669c1-d12e-4c01-8bde-d18070403b3e.png",
"path": null,
"size": 13.89,
"width": 500,
"height": 500
},
"medium": {
"ext": ".png",
"url": "https://s3.ap-southeast-1.amazonaws.com/virtualprotocolcdn/medium_36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add.png",
"hash": "medium_36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add",
"mime": "image/png",
"name": "medium_36990_73f669c1-d12e-4c01-8bde-d18070403b3e.png",
"path": null,
"size": 23.59,
"width": 750,
"height": 750
},
"thumbnail": {
"ext": ".png",
"url": "https://s3.ap-southeast-1.amazonaws.com/virtualprotocolcdn/thumbnail_36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add.png",
"hash": "thumbnail_36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add",
"mime": "image/png",
"name": "thumbnail_36990_73f669c1-d12e-4c01-8bde-d18070403b3e.png",
"path": null,
"size": 3.18,
"width": 156,
"height": 156
}
},
"hash": "36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add",
"ext": ".png",
"mime": "image/png",
"size": 33.02,
"url": "https://s3.ap-southeast-1.amazonaws.com/virtualprotocolcdn/36990_73f669c1_d12e_4c01_8bde_d18070403b3e_9e6ac09add.png",
"previewUrl": null,
"provider": "aws-s3",
"provider_metadata": null,
"createdAt": "2025-08-23T20:37:31.830Z",
"updatedAt": "2025-08-23T20:37:31.830Z"
},
"genesis": null,
"stats": {
"contributionsCount": 0,
"contributorsCount": 0,
"contributionVersions": [],
"totalStakeAmount": "0.0",
"stakerCount": 0,
"validatorCount": 0
},
"characterDescription": "",
"projectMembers": [
{
"id": 31823,
"isAccepted": true,
"title": "Owner",
"createdAt": "2025-08-23T20:37:22.632Z",
"updatedAt": "2025-08-23T20:37:22.632Z",
"walletAddress": "0xD377C57312db3578465957A5Ed78af643dAccBDb",
"virtual": {
"id": 36990,
"creator": {
"id": 497139
}
},
"user": {
"id": 497139,
"socials": {
"VERIFIED_LINKS": {
"TWITTER": "https://x.com/chorus_protocol",
"TELEGRAM": "https://t.me/kwaude_OG"
}
},
"bio": null,
"avatar": null,
"walletAddress": "0xD377C57312db3578465957A5Ed78af643dAccBDb"
}
}
],
"tokenomics": [],
"tokenomicsStatus": {
"hasUnlocked": true,
"daysFromFirstUnlock": 0
},
"multichainAgents": []
}
</full_details>
Investment info last updated: Aug 23, 2025 21:13