Monitoring Rules
| Metric | Threshold |
|---|---|
| Rolling expectancy | < 0 over the latest 50 trades |
| Rolling hit rate | Below the backtest range for 3 consecutive months |
| Drawdown | Worse than 1.5x historical max drawdown |
| Metric | Threshold |
|---|---|
| Rolling expectancy | < 0 over the latest 50 trades |
| Rolling hit rate | Below the backtest range for 3 consecutive months |
| Drawdown | Worse than 1.5x historical max drawdown |
Going forward, the strategy should be monitored through rolling behavior rather than single wins and losses. We would compare live or forward results against the out-of-sample backtest using:
Successful, Stop-loss triggered, Timed out, and Breakout failureThe key idea is that we do not expect each month to match the backtest exactly. We expect live behavior to stay inside a reasonable range around the validated backtest distribution.
The strategy will be treated as impaired when one or more of the following conditions persist long enough to suggest regime failure rather than normal noise:
Rolling expectancy < 0
50 tradesRolling hit rate falls materially below the backtest range
Drawdown exceeds a historical stress threshold
1.5x the historical max drawdownML overlay no longer improves the baseline
Payoff shape breaks
The project should monitor both layers separately:
This matters because the ML extension is intentionally small. If the overlay stops helping, the baseline may still remain tradable.
| Metric | Value |
|---|---|
| Average winner | 1.41% |
| Average loser | -1.17% |
| Payoff ratio | 1.21 |
| Largest winner | 4.40% |
| Largest loser | -2.97% |
| Top 3 trade PnL share | 47.57% |
The practical decision rule is:
That gives the project a concrete answer to the two most important forward-looking questions: