Strategy

The current codebase uses two related but different concepts under app/strategies/:

• Strategy: creates pending signals that can later become real trades
• Scanner: generates alerts and stores observations, but does not execute trades

Strategy vs Scanner

Registered components

MR Combined

Range/mean-reversion strategy with multi-timeframe context and explicit range management.

Flow:

1. Trigger scan via POST /api/mr-combined/scan-and-signal
2. Filter by HTF/MTF market context
3. Validate 4H range quality, then inspect 1H setup near support/resistance
4. Create a pending signal with tier, checklist, TP structure, and range levels
5. Boss YES -> COO calls /api/signal/{symbol}/confirm -> server checks EV/confidence -> bracket order

See: MR Combined

Pump Momentum Scanner

Alert-first momentum scanner. It does not open positions.

Flow:

1. Trigger scan via POST /api/pump-momentum/scan
2. Prefilter universe using 15m momentum + relative-strength conditions
3. Emit pump_watch or pump_signal
4. Persist signal data to SQLite
5. Send Telegram alert if present

See: Pump Momentum Scanner