Walk-Forward Validation
An out-of-sample testing protocol in which a strategy is fitted on one window of historical data and evaluated on the subsequent, unseen window, with the process rolled forward through time.
Walk-forward validation exists because a single in-sample/out-of-sample split answers the wrong question. A strategy tuned on 2015–2020 and tested once on 2021 has been validated against exactly one market regime. Rolling the boundary forward — fit on window one, test on window two, refit on windows one and two, test on window three — produces a sequence of genuinely out-of-sample verdicts that better approximates how the strategy would actually have been deployed: always trading on parameters chosen without knowledge of the future.
Two variants dominate. Anchored walk-forward grows the training window from a fixed start date, so later fits see more history. Rolling walk-forward keeps the training window a fixed length, so the model adapts to recent regimes and forgets old ones. Neither is universally correct; the choice is itself a modelling decision about how fast the market forgets.
The honest caveat is that walk-forward validation is consumable. The first pass over the out-of-sample windows is a real test. Every subsequent pass — after the researcher has seen the results and adjusted the strategy — quietly converts out-of-sample data into in-sample data. A strategy that survives its fifth walk-forward, having been reshaped after each of the previous four, has not passed five tests; it has been fitted to one long dataset in an expensive way. This is why walk-forward results are only interpretable alongside an honest count of how many configurations were tried, which is the problem the probability of backtest overfitting and the deflated Sharpe ratio exist to address, and why a kill ledger matters more than any single validation protocol. The Overfit Auditor we are building is intended to make that trial accounting explicit rather than optional.