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)EN-2 Apparent bot inactivity — logging ceased 12 Jun 2026; simultaneously affected all A/B live engines (individual & in‑book), missed trades (15–17 Jun 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.

σ: >2·Status: outside OOS 95% = Watch, outside OOS 99% = Alert·Confidence gates: A < 500, B < 250 trades are dimmed
MetricZenWave AZenWave B
Trades177161
Structural StatusALERTALERT
DD Percentile (best=high)100.0%76.2%
Runs Z Deviation (σ)+1.79σ+2.08σ
Ulcer Deviation (σ)+0.07σ+0.81σ
Rolling 12M Percentile——
Expectancy Drift (σ)-0.94σ-1.55σ
Time Underwater Drift (σ)+1.50σ+2.32σ

Layer 3 — Execution Slippage

Measured slippage across filled limit, stop, and stop-limit orders.

Positive values indicate execution worse than the requested price; negative values indicate price improvement.

Order counts may differ from headline trade totals because execution-level telemetry was introduced after launch.

MetricZenWave AZenWave BZenWave BookAll Accounts
Trades222201369792
Median Slippage+0.20 pips+0.10 pips+0.10 pips+0.10 pips
Mean Slippage+0.56 pips+0.55 pips+0.53 pips+0.55 pips
Std Dev1.79 pips1.66 pips1.72 pips1.73 pips
Max Adverse14.10 pips13.90 pips14.10 pips14.10 pips
Best Improvement-3.70 pips-3.20 pips-3.90 pips-3.90 pips
Adverse / Zero / Improved65.3% / 21.2% / 13.5%61.7% / 24.4% / 13.9%61.5% / 25.5% / 13%62.6% / 24% / 13.4%

Mean is the arithmetic average, median is the middle observation, std dev shows dispersion, max adverse is the largest positive slippage, and best improvement is the most negative slippage. Adverse / Zero / Improved shows the share of sampled orders in each bucket.

By Event Type

Each row shows mean slippage for that event type, with the sample count in parentheses. Entry covers opening fills and same-side adds; Exit covers opposite-side fills linked to the same execution chain.

EventZenWave AZenWave BZenWave BookAll Accounts
Entry+0.48 pips(141)+0.46 pips(128)+0.40 pips(235)+0.44 pips(504)
Exit+0.71 pips(81)+0.71 pips(73)+0.76 pips(134)+0.73 pips(288)

Entry and exit rows appear only where execution linkage is available in historical records.

By Session

Each cell shows mean slippage for orders filled in that session, with the sample count in parentheses.

SessionZenWave AZenWave BZenWave BookAll Accounts
Sydney+2.70 pips(4)+8.00 pips(1)+3.76 pips(5)+3.76 pips(10)
Tokyo+0.46 pips(84)+0.44 pips(75)+0.48 pips(140)+0.46 pips(299)
London+0.67 pips(75)+0.63 pips(69)+0.68 pips(129)+0.67 pips(273)
London/NY+0.52 pips(38)+0.65 pips(38)+0.30 pips(56)+0.46 pips(132)
New York+0.25 pips(21)+0.07 pips(18)+0.14 pips(39)+0.15 pips(78)

By Month

Each cell shows mean slippage for orders filled in that calendar month, with the sample count in parentheses.

MonthZenWave AZenWave BZenWave BookAll Accounts
2026-01+0.38 pips(12)+0.56 pips(8)—+0.45 pips(20)
2026-02+0.45 pips(49)+0.43 pips(46)+0.17 pips(61)+0.34 pips(156)
2026-03+0.36 pips(48)+0.35 pips(42)+0.36 pips(90)+0.36 pips(180)
2026-04+0.59 pips(44)+0.58 pips(41)+0.64 pips(85)+0.61 pips(170)
2026-05+0.93 pips(40)+0.80 pips(34)+0.87 pips(74)+0.87 pips(148)
2026-06+0.61 pips(29)+0.67 pips(30)+0.60 pips(59)+0.62 pips(118)

Smaller monthly samples can move more sharply because each individual order has more weight in the average.

Percentile Distribution

Percentiles show the slippage level at or below which that share of sampled orders fell. P50 is the median order, while P95 marks the level exceeded by about 5% of the sample.

PercentileZenWave AZenWave BZenWave BookAll Accounts
P1-1.06 pips-1.80 pips-1.89 pips-2.30 pips
P5-0.30 pips-0.10 pips-0.26 pips-0.30 pips
P10-0.10 pips-0.10 pips-0.10 pips-0.10 pips
P25+0.00 pips+0.00 pips+0.00 pips+0.00 pips
P50+0.20 pips+0.10 pips+0.10 pips+0.10 pips
P75+0.50 pips+0.50 pips+0.50 pips+0.50 pips
P90+1.00 pips+1.10 pips+1.10 pips+1.10 pips
P95+2.65 pips+2.60 pips+2.82 pips+2.90 pips
P99+9.22 pips+8.00 pips+8.19 pips+8.60 pips

Higher percentile rows place more weight on the tail of the distribution than the center.

Slippage is measured from the requested order price to the actual fill price. Data is sourced from cTrader order history via live API and 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.

EN-2

18 Jun 2026

Missed-Trades Divergence — Apparent Bot Inactivity (15–17 Jun 2026)

Cause: The precise cause of the inactivity could not be conclusively determined. Logging ceased on 12 Jun 2026 while cBot instances continued to appear active within the platform (Stop control remained visible). There is insufficient evidence to attribute the interval conclusively to a platform maintenance event.

Effect: Both ZenWave A and ZenWave B did not place expected trades during the interval; ZenWave A additionally lacked an expected open position. This produced a measurable live/backtest divergence driven by operational non‑participation rather than strategy logic or execution‑quality degradation.

Conclusion: Root cause remains undetermined. The affected interval resulted in operational non-participation and temporary divergence from expected backtest behavior despite cBot instances appearing active within the platform.

Preventative procedure: A restart and verification procedure will be performed following platform maintenance events and during routine operational checks. Verification includes confirming active log generation, expected position state, and ongoing strategy participation before trading activity is considered operational.

Log date: 18 Jun 2026 — Engines observed restarted and execution resumed.

Methodology →Validation →