Financial Trading Desk Setup

Deploy 4 agents: analyst, sentiment, risk-mgr, and executor.

Roles

Setup Procedure

Step 1: Ask the user which role this agent should play and what prefix to use.

Step 2: Install the skills for the chosen role:

# For analyst:
clawhub install pilot-stream-data pilot-metrics pilot-cron pilot-alert
# For sentiment:
clawhub install pilot-stream-data pilot-event-filter pilot-archive
# For risk-mgr:
clawhub install pilot-event-filter pilot-audit-log pilot-alert
# For executor:
clawhub install pilot-task-router pilot-receipt pilot-webhook-bridge

Step 3: Set the hostname and write the manifest to ~/.pilot/setups/financial-trading-desk.json.

Step 4: Tell the user to initiate handshakes with the peers for their role.

Manifest Templates Per Role

analyst

{
  "setup": "financial-trading-desk", "role": "analyst", "role_name": "Market Analyst",
  "hostname": "\x3Cprefix>-analyst",
  "skills": {
    "pilot-stream-data": "Ingest real-time market data feeds (price, volume, order book).",
    "pilot-metrics": "Track signal accuracy, win rate, and Sharpe ratio.",
    "pilot-cron": "Run scheduled scans for technical setups across watchlists.",
    "pilot-alert": "Emit trade signals when high-confidence setups are detected."
  },
  "data_flows": [
    { "direction": "send", "peer": "\x3Cprefix>-risk-mgr", "port": 1002, "topic": "trade-signal", "description": "Trade signals with entry/exit levels" }
  ],
  "handshakes_needed": ["\x3Cprefix>-risk-mgr"]
}

sentiment

{
  "setup": "financial-trading-desk", "role": "sentiment", "role_name": "Sentiment Scanner",
  "hostname": "\x3Cprefix>-sentiment",
  "skills": {
    "pilot-stream-data": "Ingest news feeds, social media streams, and earnings data.",
    "pilot-event-filter": "Classify content as bullish, bearish, or neutral.",
    "pilot-archive": "Store historical sentiment data for backtesting."
  },
  "data_flows": [
    { "direction": "send", "peer": "\x3Cprefix>-risk-mgr", "port": 1002, "topic": "sentiment-score", "description": "Sentiment scores with source attribution" }
  ],
  "handshakes_needed": ["\x3Cprefix>-risk-mgr"]
}

risk-mgr

{
  "setup": "financial-trading-desk", "role": "risk-mgr", "role_name": "Risk Manager",
  "hostname": "\x3Cprefix>-risk-mgr",
  "skills": {
    "pilot-event-filter": "Correlate trade signals with sentiment for confirmation.",
    "pilot-audit-log": "Log all risk decisions with full reasoning for audit.",
    "pilot-alert": "Emit alerts on exposure limit breaches or drawdown warnings."
  },
  "data_flows": [
    { "direction": "receive", "peer": "\x3Cprefix>-analyst", "port": 1002, "topic": "trade-signal", "description": "Trade signals from analyst" },
    { "direction": "receive", "peer": "\x3Cprefix>-sentiment", "port": 1002, "topic": "sentiment-score", "description": "Sentiment scores from scanner" },
    { "direction": "send", "peer": "\x3Cprefix>-executor", "port": 1002, "topic": "approved-trade", "description": "Approved trades with position sizing" },
    { "direction": "receive", "peer": "\x3Cprefix>-executor", "port": 1002, "topic": "execution-report", "description": "Fill reports for P&L tracking" }
  ],
  "handshakes_needed": ["\x3Cprefix>-analyst", "\x3Cprefix>-sentiment", "\x3Cprefix>-executor"]
}

executor

{
  "setup": "financial-trading-desk", "role": "executor", "role_name": "Trade Executor",
  "hostname": "\x3Cprefix>-executor",
  "skills": {
    "pilot-task-router": "Route orders to optimal execution venue.",
    "pilot-receipt": "Generate trade confirmations and settlement receipts.",
    "pilot-webhook-bridge": "Interface with exchange APIs for order placement."
  },
  "data_flows": [
    { "direction": "receive", "peer": "\x3Cprefix>-risk-mgr", "port": 1002, "topic": "approved-trade", "description": "Approved trades to execute" },
    { "direction": "send", "peer": "\x3Cprefix>-risk-mgr", "port": 1002, "topic": "execution-report", "description": "Fill reports with price and slippage" }
  ],
  "handshakes_needed": ["\x3Cprefix>-risk-mgr"]
}

Data Flows

• analyst -> risk-mgr : trade signals with entry/exit levels and rationale (port 1002)
• sentiment -> risk-mgr : sentiment scores with source attribution (port 1002)
• risk-mgr -> executor : approved trades with position size and risk parameters (port 1002)
• executor -> risk-mgr : execution reports with fill price and slippage (port 1002)

Workflow Example

# On analyst -- detect setup and publish signal:
pilotctl --json publish \x3Cprefix>-risk-mgr trade-signal '{"symbol":"AAPL","direction":"long","entry":187.50,"stop_loss":184.00,"confidence":0.82}'
# On sentiment -- publish corroborating sentiment:
pilotctl --json publish \x3Cprefix>-risk-mgr sentiment-score '{"symbol":"AAPL","score":0.74,"classification":"bullish"}'
# On risk-mgr -- approve with position sizing:
pilotctl --json publish \x3Cprefix>-executor approved-trade '{"trade_id":"TRD-4821","symbol":"AAPL","direction":"long","qty":150,"order_type":"limit"}'
# On executor -- report fill:
pilotctl --json publish \x3Cprefix>-risk-mgr execution-report '{"trade_id":"TRD-4821","fill_price":187.55,"slippage_bps":2.7,"status":"filled"}'

Dependencies

Requires pilot-protocol skill, pilotctl binary, clawhub binary, and a running daemon.