Forward Performance Tracking

This page tracks live execution across three dimensions: corridor adherence against backtest envelopes, structural deviation monitoring using distribution-based metrics, and measured execution slippage from live order fills. Parameters remain frozen during forward tracking. No performance-based adjustments are permitted.

Deployment Protocol

  • Parameters frozen prior to launch.
  • No discretionary intervention.
  • No optimisation during forward tracking.
  • Deviations documented without modification of logic.

FPT Equity Curve

Observed execution vs. demo & live backtests

EN-1 B: Stop-Lock Timing Divergence — Execution Variance (26 Mar 2026)

Layer 1 — Execution Corridors

Demo Backtest

Upper bound

Optimistic execution assumptions. No spread variability, ideal fills.

Live Backtest

Lower bound

Conservative execution assumptions. Wider spreads, commission modeling.

Live Actual

Observed execution

Forward tracking. Performance is evaluated against the predefined execution corridor and structural monitoring thresholds.

Live observations are expected to fluctuate inside the execution envelope and through temporary sigma deviations, especially at low trade counts.

Forward tracking continues until a statistically meaningful sample size is reached.

Layer 2 — Structural Deviation Monitoring

After corridor validation, structural monitors test whether live behavior remains statistically consistent with OOS distributions.

σ: <1σ: 1–2σ: >2·Status: outside OOS 95% = Watch, outside OOS 99% = Alert·Confidence gates: A < 500, B < 250 trades are dimmed
MetricZenWave AZenWave B
Trades122109
Structural StatusALERTALERT
DD Percentile (best=high)100.0%99.6%
Runs Z Deviation (σ)+1.30σ+1.85σ
Ulcer Deviation (σ)+0.25σ-0.16σ
Rolling 12M Percentile——
Expectancy Drift (σ)-0.95σ-1.62σ
Time Underwater Drift (σ)+1.53σ+2.08σ

Layer 3 — Execution Slippage

Measured slippage on stop and stop-limit orders across all live public accounts. Positive values indicate slippage against the trader; negative values indicate price improvement.

Median slippage remains near zero across accounts, with occasional tail events during high-volatility conditions.

Execution remains consistent across engines, with no meaningful divergence between accounts.

MetricZenWave AZenWave BZenWave BookAll Accounts
Trades120107115342
Median Slippage+0.02 pips+0.01 pips+0.02 pips+0.02 pips
Mean Slippage+0.08 pips+0.04 pips+0.05 pips+0.06 pips
Std Dev0.37 pips0.15 pips0.18 pips0.26 pips
Max Adverse3.70 pips1.39 pips1.39 pips3.70 pips
Best Improvement-0.03 pips-0.13 pips-0.03 pips-0.13 pips
Adverse / Zero / Improved68.3% / 23.3% / 8.3%66.4% / 18.7% / 15%70.4% / 20% / 9.6%68.4% / 20.8% / 10.8%

Max adverse slippage reflects rare tail events and should not be interpreted as typical execution conditions.

By Session

Execution remains tight across sessions, with slightly wider slippage during London and overlap periods.

SessionZenWave AZenWave BZenWave BookAll Accounts
Sydney+3.70 pips(1)——+3.70 pips(1)
Tokyo+0.03 pips(49)+0.02 pips(48)+0.03 pips(53)+0.03 pips(150)
London+0.06 pips(43)+0.07 pips(34)+0.10 pips(38)+0.08 pips(115)
London/NY+0.07 pips(17)+0.06 pips(18)+0.02 pips(14)+0.05 pips(49)
New York+0.01 pips(10)+0.01 pips(7)+0.01 pips(10)+0.01 pips(27)

By Month

Higher-volatility periods produce wider slippage, consistent with breakout-driven execution.

MonthZenWave AZenWave BZenWave BookAll Accounts
2025-110.00 pips(4)+0.02 pips(6)—+0.01 pips(10)
2025-12+0.03 pips(26)+0.01 pips(28)—+0.02 pips(54)
2026-01+0.21 pips(20)+0.03 pips(11)—+0.15 pips(31)
2026-02+0.07 pips(30)+0.06 pips(26)+0.03 pips(39)+0.05 pips(95)
2026-03+0.03 pips(28)+0.03 pips(25)+0.03 pips(53)+0.03 pips(106)
2026-04+0.14 pips(12)+0.14 pips(11)+0.14 pips(23)+0.14 pips(46)

Small sample periods may show higher variance.

Percentile Distribution

Percentiles show how slippage is distributed beyond the average. P50 reflects typical execution, while upper percentiles capture rare tail events.

PercentileZenWave AZenWave BZenWave BookAll Accounts
P1-0.03 pips-0.04 pips-0.03 pips-0.03 pips
P5-0.01 pips-0.01 pips-0.01 pips-0.01 pips
P10+0.00 pips-0.01 pips+0.00 pips-0.01 pips
P25+0.00 pips+0.00 pips+0.00 pips+0.00 pips
P50+0.02 pips+0.01 pips+0.02 pips+0.02 pips
P75+0.04 pips+0.04 pips+0.05 pips+0.04 pips
P90+0.08 pips+0.09 pips+0.09 pips+0.09 pips
P95+0.11 pips+0.12 pips+0.10 pips+0.11 pips
P99+1.29 pips+0.73 pips+1.20 pips+1.37 pips

Most trades remain tightly clustered near zero slippage, with only a small fraction of events reaching the upper tail.

Slippage measured from trigger price to fill price on stop and stop-limit orders. Data sourced from cTrader order history via live API. Refreshed periodically.

Documentation Log

Each update is timestamped and documented. No parameter adjustments are made during forward tracking.

Execution Notes

EN-1

26 Mar 2026

Stop-Lock Timing Divergence (Execution Variance)

Cause: Minor entry-price differences (~0.001–0.003) produced variation in R-multiple calculations relative to the encoded initial stop, shifting threshold crossing.

Effect: Accounts with slightly more favorable entry reached the lock threshold and exited, while others remained below the threshold and stayed in position.

Conclusion: This reflects expected boundary sensitivity in a threshold-based system under live execution variance, not a logic inconsistency.

All environments executed identical rules with no parameter or logic differences.

Methodology →Validation →