A backtest-passing bot is not a money-making bot — yet. This runbook is the bridge. Six stages, ~3 weeks, ~$50-150 in eval costs, and a real shot at a funded account at the end. Read this once. Bookmark it. Re-read at each stage transition.
The fleet backtester runs all 31 strategies × 14 symbols × 4 timeframes against multiple years of CME historical OHLCV data. Each (strategy, symbol, variant) combo gets classified into one of four buckets per the dual-track gate logic.
From Backtest in the sidebar, kick off a fleet backtest on a 5-minute timeframe with Micro mode enabled. Micro mode uses micro-contract point values (MNQ $2/pt vs NQ $20/pt) so drawdowns scale to micro-account-friendly sizes. The run produces one report per bot plus a SUMMARY view that classifies each candidate into the four buckets above.
The moment SUMMARY.md drops, the post-v6 validation pipeline auto-runs. It chains three independent gates and produces the actionable survivor list:
The output surfaces in two places:
The SURVIVORS section at the top is the actionable list. These bots passed all 3 backtest-side gates. They're safe to paper-trade — but not yet safe to risk real eval money on. Paper trading is the next gate.
Paper trading is where backtest assumptions meet real Tradovate market data + slippage + execution latency. This is the gate that catches overfit + unrealistic-fill cases that look great on paper but die in production.
Drop any bot showing any of these symptoms:
You're about to spend $50-150 on a Topstep 50K combine. Run this checklist before clicking buy. Print it out if that helps. Every box must be .
Eval passed → Topstep gives you a funded account. Time to scale safely.
Concentration risk. Don't deploy 5 M2K bots to 5 accounts — when M2K has a bad day all 5 accounts blow at once. Either retune to broaden the symbol set, or accept you're running 1 effective bot and only buy 1 eval.
Severe overfitting. The strategy was tuned to in-sample noise. Don't paper-trade this bot — retune with looser parameters and re-run the full backtest pipeline.
Slippage is eating your edge. Tighten the TP target by 1-2 ticks, or widen the SL by 1 tick, and re-test. If both adjustments still show negative P&L, the strategy doesn't have enough edge to survive realistic execution costs.
Almost always due to oversized initial position or news event. Audit log shows the death trade. Check: was it a session-filter bypass (bot fired during news window)? Was it a contract-size mismatch (deployed at 5ct instead of 1ct)? Fix the specific cause, not the strategy.
Trailing DD bit you. You hit a peak then gave it back. Standing rule: when up $1,500+ on a 50K combine, close all positions for the day. Trailing DD is highest at peak. Going flat preserves the lead.
Aborting means: shut down all live deployments, pause development for 1-2 weeks, reassess. Maybe the market regime has shifted. Maybe the strategies need a complete rewrite. Either way, throwing more money at a broken pipeline doesn't fix the pipeline.
Many of our funded traders use NinjaTrader as their order-entry surface for the eval & funded stages above. Lucid Terminal continues to handle indicator tracking, journal-to-vault, bot automation, and combined-DD monitoring; NinjaTrader handles the discretionary order placement with its DOM, advanced order types, and chart trader. The two coexist cleanly because both read the same broker account state through each firm’s official API.
If you don’t already use NinjaTrader, you can pair it with a free Kinetick data account for futures-only feeds during your eval stage. See the Platforms page for the partner links.
Every step in this runbook is wired into the Lucid Terminal app. Open the Bots tab, find the Eval Pre-Flight Checklist, and let the gate badges guide you stage by stage.
Open Lucid Terminal Back to Getting Started