What Happens When Slippage Doubles? The Backtest Cost Cliff

Under adversarial review, fix the estimand as “executable net expectancy that remains after deterioration in the distribution of trading costs.” Do not substitute net profit, win rate, or a visually smooth curve for that target. Declare the horizon, account currency, included frictions, and operating-stop boundary before calculation. Any post-result change creates a new hypothesis and version, preventing the question from being selected after the answer is known.

Reconstruct the observation unit as “an order leg, costing entries, additions, partial exits, and final exits separately” before treating rows as independent evidence. Report raw rows, parent trades, decisions, event clusters, and the denominator used for each average or standard error. Recompute net expectancy, break-even cost, cost elasticity, opportunity loss after rejected fills, and lower quantiles under crisis costs under more than one defensible aggregation rule so that a larger export is not mistaken for a larger information set.

Preserve the hash of the TradingView export and the symbol, timeframe, session, timezone, order-processing settings, costs, account currency, and Pine version. For execution-cost cliff, state-dependent and size-dependent slippage and its positive correlation with losing conditions directly affects reproducibility. Keep immutable source, normalized, and analysis layers separate, with every join, deletion, imputation, and conversion recorded in a transformation ledger.

The export identifies only what can be rebuilt from recorded time, price, quantity, and P&L. order-book depth, queue position, market impact, and broker-specific rejection or requoting requires additional evidence. Mark each causal link as observed, bounded by assumption, or externally unverified. This prevents state-dependent and size-dependent slippage and its positive correlation with losing conditions from being presented as a confirmed fact when the available data support only an interval or conditional conclusion.

Do not adopt the platform summary as ground truth. Independently expand every entry, add-on, partial exit, and close into order legs and apply spread and slippage by time, size, and liquidity state. Reconcile total and row-level differences by sign, date, symbol, and order type. If discrepancies concentrate in the exact state associated with execution-cost cliff, treat that concentration as a primary finding rather than dismissing it as rounding.

Report net expectancy, break-even cost, cost elasticity, opportunity loss after rejected fills, and lower quantiles under crisis costs with intervals or resampling distributions, not point estimates alone. Match the uncertainty method to sample size, skewness, heavy tails, censoring, and selection history. If normal, quantile, and dependence-aware methods disagree on the sign, classify the edge as unidentified and show the minimum detectable effect and lower decision bound.

Do not narrow uncertainty with an IID shuffle alone. Resample time blocks that preserve liquidity and volatility states using several fixed block lengths and stationary bootstrap. Preserve random seed, repetition count, wrap rule, and missing-data treatment. For each block specification, report the distribution of net expectancy, break-even cost, cost elasticity, opportunity loss after rejected fills, and lower quantiles under crisis costs, the rejection-side tail mass, and the rate at which the verdict changes sign.

Interrogate the mechanism “state-dependent and size-dependent slippage and its positive correlation with losing conditions” with lower quantiles, expected shortfall, influence, cluster length, and boundary-hitting measures. Historical maximum loss is not a loss cap. Define several absorbing or operating boundaries—capital, margin, mandate drawdown, and recovery time—and record which boundary fails first under each stress.

A flat commission deduction is not an execution model for execution-cost cliff. Allocate spread, slippage, financing, borrow, roll, conversion, rounding, and rejected orders to the relevant unit. Recompute net expectancy, break-even cost, cost elasticity, opportunity loss after rejected fills, and lower quantiles under crisis costs under base, upper-quantile, and crisis states while preserving the possibility that costs and losses worsen together.

Count the complete population of periods, symbols, timeframes, parameters, exits, filters, and metrics that were tried. Do not detach the attractive result for execution-cost cliff from rejected candidates, interim changes, or repeated validation reviews. Where appropriate, use PBO, SPA, and a Deflated Sharpe Ratio, and treat an unrecorded trial count as a material audit limitation.

Test whether execution-cost cliff is concentrated in one trend, volatility, liquidity, rate, or session state. Define regimes prospectively or on training data only. Report statewise net expectancy, break-even cost, cost elasticity, opportunity loss after rejected fills, and lower quantiles under crisis costs, occupancy, transition probabilities, and costs, then reweight the mixture to adverse but realistic future compositions.

For the execution-cost cliff case, the same trade set can follow different capital paths under another inception date, order, initial balance, rounding rule, or stop condition. Separate fixed quantity, fixed R, and percentage sizing, then use circular shifts and block orderings to recompute drawdown, recovery, and boundary hits. Equal terminal P&L does not imply equal path risk.

Perturb “slippage multiplier, spread percentile, and fill-rejection rate” one axis at a time before creating a joint sensitivity surface. Add the negative control “permute slippage states within the same session to test whether the strategy timing is specifically exposed to costly execution.” Predefine the grid and crisis rule so that neither the most favorable nor the most damaging cell is selected after inspection. Save the slope, curvature, and exact point where the decision boundary is crossed.

Have a second implementation expand every entry, add-on, partial exit, and close into order legs and apply spread and slippage by time, size, and liquidity state, then compare critical row-level outputs. Regression fixtures should include empty files, duplicate timestamps, extreme costs, reverse ordering, missing values, and boundary cases. Agreement between implementations is insufficient if they share the same bad input, so separate data construction and review roles where feasible.

Predeclare the decision rule. This case passes only if “net expectancy clears the lower bound under base, doubled, and upper-quantile cost scenarios with material distance to break-even cost.” Near a boundary, disclose interval width and economic materiality rather than a binary badge. If only one favorable block length, cost state, or implementation passes, classify the result as assumption-sensitive rather than robust.

The evidence ledger must store the input hash, code version, settings, exclusions, “slippage multiplier, spread percentile, and fill-rejection rate,” block lengths, random seed, repetition count, and every scenario output. Keep exploratory and confirmatory results in separate namespaces and retain failed trials. When new TradingView data arrive, create a new version and track realized cost per leg, size-conditioned slippage, rejection rate, and deviation from the base cost model rather than overwriting the old result.

Translate statistical changes into capital consequences. A shift in expectancy, lower quantile, recovery time, or boundary risk caused by execution-cost cliff should be mapped to trade count, capital, margin, and continuation. A small per-trade difference can compound under high turnover, while a rare loss can be decisive near an absorbing boundary.

Separate hypothesis design, implementation, independent recalculation, and approval where practical. Stop automatically on material reconciliation error, unresolved missing data, non-reproducibility, or a predeclared threshold breach. Audit the chain “optimistic fills → overstated small wins → accumulation through turnover → negative net expectancy → live-trading divergence,” and monitor realized cost per leg, size-conditioned slippage, rejection rate, and deviation from the base cost model prospectively without turning a historical pass into a promise of future profit.

The estimand “executable net expectancy that remains after deterioration in the distribution of trading costs” is identified only within the columns present in the TradingView export and the stated assumptions. If order-book depth, queue position, market impact, and broker-specific rejection or requoting cannot be observed, report bounds rather than a false point estimate.

Past estimates of execution-cost cliff need not belong to the same population after changes in rules, participants, volatility, costs, or data specifications. Track realized cost per leg, size-conditioned slippage, rejection rate, and deviation from the base cost model in rolling and regime-specific windows.

For execution-cost sensitivity, repeatedly applying the same diagnostic battery and editing until it passes turns verification into another optimizer. Every post-audit change therefore creates a new model version and requires untouched evidence.

Even if net expectancy clears the lower bound under base, doubled, and upper-quantile cost scenarios with material distance to break-even cost, the analysis does not establish tax, regulatory, behavioral, liquidity, order-size, or systems suitability. Separate statistical diagnosis from live-operating approval.

Deleting observations related to state-dependent and size-dependent slippage and its positive correlation with losing conditions may improve the result. Compare no deletion, conservative imputation, and worst-case imputation, and display how net expectancy, break-even cost, cost elasticity, opportunity loss after rejected fills, and lower quantiles under crisis costs changes.

Run the control “permute slippage states within the same session to test whether the strategy timing is specifically exposed to costly execution.” If the control performs similarly, suspect processing rules or common market drift before attributing performance to the strategy.

After a provisional pass, log realized cost per leg, size-conditioned slippage, rejection rate, and deviation from the base cost model sequentially and stop on persistent departures from the predeclared predictive range. Diagnose implementation drift before reoptimizing history.

Multiple methods can agree because they share the same bad input or the same mechanism “state-dependent and size-dependent slippage and its positive correlation with losing conditions.” Give lower-tail outcomes, failed scenarios, and unresolved mismatches the same visual prominence as favorable results; test count is not proof of correctness.