# π Agent Orchestration Master Plan
> **Mission:** Build the complete x402 Facilitator infrastructure in parallel using 5 specialized agents.
## π Overview
This document coordinates 5 Opus 4.5 agents working in parallel on the **x402 Facilitator Server** - our first major revenue stream. Each agent has a specific domain and clear handoff points.
## π― Project Goal
Build a production-ready x402 Facilitator that:
1. Processes x402 payments across EVM and Solana chains
2. Takes 0.1% fee on each transaction
3. Provides analytics dashboard
4. Runs in Docker with full monitoring
5. Integrates with our existing marketplace
## π Agent Assignments
| Agent | Domain | Primary Files | Dependencies |
|-------|--------|---------------|--------------|
| **Agent 1** | Facilitator Core Engine | `packages/facilitator/src/core/` | None (starts first) |
| **Agent 2** | Settlement & Multi-Chain | `packages/facilitator/src/settlement/` | Agent 1 interfaces |
| **Agent 3** | REST API & WebSocket | `packages/facilitator/src/api/` | Agent 1 + 2 types |
| **Agent 4** | Monitoring & Analytics | `packages/facilitator/src/analytics/` | Agent 1-3 events |
| **Agent 5** | Deployment & Docs | `deploy/facilitator/`, docs | All agents |
## π Workflow
```
Phase 1 (Parallel): Agents 1-4 start simultaneously
Phase 2 (Integration): Agent 5 integrates, all agents test
Phase 3 (Polish): Bug fixes, optimization, documentation
Phase 4 (Launch): Deployment, monitoring, handoff to next project
```
## π Target Directory Structure
```
packages/facilitator/
βββ package.json
βββ tsconfig.json
βββ tsup.config.ts
βββ README.md
βββ src/
β βββ index.ts
β βββ core/
β β βββ FacilitatorServer.ts
β β βββ PaymentProcessor.ts
β β βββ PaymentVerifier.ts
β β βββ FeeCalculator.ts
β β βββ types.ts
β βββ settlement/
β β βββ SettlementEngine.ts
β β βββ chains/
β β β βββ EVMSettler.ts
β β β βββ SolanaSettler.ts
β β β βββ BaseSettler.ts
β β βββ BatchProcessor.ts
β β βββ types.ts
β βββ api/
β β βββ server.ts
β β βββ routes/
β β β βββ verify.ts
β β β βββ settle.ts
β β β βββ status.ts
β β β βββ analytics.ts
β β βββ middleware/
β β β βββ auth.ts
β β β βββ rateLimit.ts
β β β βββ logging.ts
β β βββ websocket/
β β βββ PaymentStream.ts
β βββ analytics/
β β βββ AnalyticsService.ts
β β βββ MetricsCollector.ts
β β βββ RevenueTracker.ts
β β βββ Dashboard.ts
β βββ storage/
β β βββ PaymentStore.ts
β β βββ SettlementStore.ts
β β βββ migrations/
β βββ utils/
β βββ logger.ts
β βββ config.ts
β βββ errors.ts
βββ tests/
βββ core.test.ts
βββ settlement.test.ts
βββ api.test.ts
βββ e2e/
deploy/facilitator/
βββ Dockerfile
βββ docker-compose.yml
βββ nginx.conf
βββ prometheus.yml
βββ grafana/
β βββ dashboards/
βββ scripts/
βββ start.sh
βββ health-check.sh
```
## π Integration Points
### With Existing Codebase
- `packages/payments/` - Share types and utilities
- `packages/marketplace/` - RevenueRouter integration
- `contracts/marketplace/RevenueRouter.sol` - On-chain fee routing
- `x402/typescript/` - Reference x402 implementation
### External Dependencies
- `@x402/core` - Base x402 types
- `viem` - EVM interactions
- `@solana/web3.js` - Solana interactions
- `hono` - Fast HTTP server
- `drizzle-orm` - Database
- `bullmq` - Job queue for settlements
## βοΈ After Facilitator Completion
Once all 5 agents complete the facilitator, they move to:
| Agent | Next Project |
|-------|-------------|
| Agent 1 | Featured Listings Contract |
| Agent 2 | Credit Purchase System |
| Agent 3 | Agent Wallet SDK |
| Agent 4 | Analytics Dashboard UI |
| Agent 5 | Documentation Site |
See individual agent prompt files for detailed instructions.
---
## π Agent Prompt Files
1. [AGENT_1_FACILITATOR_CORE.md](./AGENT_1_FACILITATOR_CORE.md)
2. [AGENT_2_FACILITATOR_SETTLEMENT.md](./AGENT_2_FACILITATOR_SETTLEMENT.md)
3. [AGENT_3_FACILITATOR_API.md](./AGENT_3_FACILITATOR_API.md)
4. [AGENT_4_FACILITATOR_MONITORING.md](./AGENT_4_FACILITATOR_MONITORING.md)
5. [AGENT_5_FACILITATOR_DEPLOYMENT.md](./AGENT_5_FACILITATOR_DEPLOYMENT.md)