Orchestration Flows

This document focuses on the current live flows around signals, scanners, manual trade management, and reporting.

A. MR Combined scan -> pending signal -> boss confirmation

scout
  -> POST /api/mr-combined/scan-and-signal?agent=scout
  -> server analyzes watchlist / universe
  -> server creates PendingSignal if setup is valid
  -> server sends Telegram signal to boss

boss
  -> replies YES / NO via COO flow

coo
  -> GET /api/signal/{symbol}
  -> POST /api/signal/{symbol}/confirm    # on YES
  -> POST /api/signal/{symbol}/reject     # on NO

server
  -> re-checks EV / confidence thresholds
  -> executes trade via app.opentrader subprocess
  -> sends final Telegram result

Notes:

• MR Combined is a trade-generating strategy.
• The signal is created first; trade execution only happens after explicit confirmation.

B. Pump Momentum scan -> alert only

scout
  -> POST /api/pump-momentum/scan?agent=scout

server
  -> scans configured universe
  -> emits pump_watch / pump_signal observations
  -> stores rows in SQLite
  -> sends Telegram alert if any signal exists

scout
  -> announces summary to COO if needed

Notes:

• Pump Momentum does not create trades.
• It is an alert-first scanner, not a strategy in the execution path.

C. Manual trade flow (LIMIT entry + delayed OCO)

boss
  -> gives explicit trade instruction

coo
  -> POST /api/trade/manual

server
  -> places LIMIT entry
  -> stores pending entry in SQLite

ops/finance loop
  -> GET /api/pending-entries/check
  -> if filled: place OCO / protection orders
  -> if expired: cancel pending entry

D. Market context flow

coo or finance or scout
  -> GET /api/market/{symbol}
  -> receive multi-timeframe MarketContext

optional warmup / cache refresh
  -> GET /api/market/scan
  -> GET /api/market/all
  -> GET /api/market/{symbol}/history

Notes:

• This flow is for analysis and decision support.
• It replaces the old /api/trend/* single-timeframe flow.

E. Trailing stop / status / reporting

ops automation
  -> GET /api/trailing
  -> GET /api/status
  -> POST /api/status/report
  -> POST /api/signal/cleanup

Main outcomes:

• trailing stop updates
• operational status snapshots
• daily PnL reporting
• cleanup of expired pending signals

F. Human routing model

boss -> COO

COO routes by intent:
- signal scan / market scan -> scout
- context / risk / PnL review -> finance
- manual trade / approve / reject -> COO
- infra / code / bugfix -> tech