Dispersion and Relative Strength Backtests Need Proxy Discipline

Read this article with Options Backtesting API, Backtesting Framework, Backtesting Data Quality Checklist, Backtesting Execution Realism, Quote-Aware Options Backtests, and Backtest to Paper Trading Parity Checklist.

Abstract

Relative-value intraday strategies depend on aligned context. If a strategy compares QQQ against SPY, or one ETF against a sector proxy, the backtest has to align those series bar by bar and avoid letting the proxy introduce hidden lookahead.

For developers, dispersion research forces the system to handle multiple streams honestly.

What The Proxy Does

A proxy series can define beta-adjusted spread, relative strength, shock filters, or confirmation. The traded symbol is not evaluated in isolation. It is evaluated against what a related market was doing at the same time.

That can improve a signal, but it also adds failure modes. Missing proxy bars, mismatched timestamps, and unstable beta estimates can all create false precision.

Define The Alignment Contract

Proxy research should start with an alignment contract. The contract states which bar timestamps are eligible, how missing bars are handled, whether bars must be present for both series, and when rolling statistics are computed. Without this contract, the replay engine can accidentally compare a fresh primary bar with a stale proxy bar.

A strict default is to require both series to have completed bars for the same timestamp before scoring the signal. If one side is missing, the event rejects or carries a documented missing-data status. Forward filling can be useful for some macro features, but it is risky for intraday relative-strength signals because the stale side can make the spread look more extreme than it was.

The contract should also define session boundaries. A proxy based on regular-session bars should not mix premarket context unless the strategy explicitly uses it. These details sound small, but they determine whether the comparison is measuring relative behavior or timestamp mismatch.

Align Before You Score

Align primary and proxy bars before computing spread or z-score.

The replay engine should also define the rolling window used for beta or correlation. If the correlation filter uses future bars, the signal becomes contaminated.

The same next-bar discipline still applies. A relative-strength signal generated from completed bars should enter only after those bars were observable.

Estimate Beta Causally

Beta-adjusted spread signals are only as clean as the beta estimate. If the estimate uses future returns, the signal has already seen part of the answer. A causal beta estimate should use only data available before the signal timestamp, and the lookback window should be logged as part of the experiment.

Stress-test the estimate too. Short lookbacks are noisy; long lookbacks can lag regime changes.

Compare raw spread, beta-adjusted spread, and rank-based relative strength before promotion. If only one transformation works, the next step is to understand why.

Why Direction Matters

Dispersion signals are often not symmetric.

A branch that works when QQQ leads SPY may fail when the same idea is inverted or moved to another symbol. Developers should not assume a relative-value family is portable just because the math is reusable.

This is where no-go reports help. They show whether a failure came from signal logic, proxy mismatch, option expression, or portfolio overlap.

Use Null Tests For Proxy Contribution

A proxy should earn its place in the model.

One way to test that is to run null variants: primary-only signal, proxy-only filter, shuffled proxy timestamps, or a related but less appropriate proxy. The goal is to see whether the proxy adds information or only adds another parameter surface.

If the primary-only version performs similarly, the dispersion layer may be unnecessary. A shuffled-proxy win points to regime exposure, not aligned relative strength.

These tests are not punitive. They expose complexity that adds implementation risk without adding evidence.

Connect The Proxy Signal To The Option Expression

The relative-strength signal may live in the underlying pair, but the trade still has to be expressed through options. That creates a second layer of asymmetry. A proxy event that looks clean on the underlying can select contracts with different liquidity, DTE availability, and spread behavior depending on direction.

For example, a long-call expression after a relative-strength breakout can face a different quote surface than a long-put expression after a relative weakness event. The signal math may be symmetric while the option market is not. A serious report should therefore show rejects and fill quality by direction, beside combined PnL.

This also matters for portfolio construction. A dispersion branch can look useful alone but overlap heavily with broad index momentum or volatility sleeves. The proxy signal should be evaluated for independent contribution, beside standalone return.

When A Proxy Branch Should Stay A Research Note

A proxy-based strategy should stay in research when alignment is fragile, beta estimates are unstable, direction changes reverse the conclusion, or option rejects cluster around the exact events that generate the signal. These outcomes do not mean the idea is worthless. They mean the system has not yet converted the relative-value observation into a tradable rule.

That distinction is important for developers. Closing a branch is not the same as discarding the learning. A no-go report can preserve the alignment assumptions, proxy diagnostics, and option-expression failures so the next experiment starts from evidence rather than memory.

Takeaway

Proxy-based research is powerful only when the data alignment is boring and strict. Build the alignment first, then test the strategy. Otherwise the proxy can become a hidden source of hindsight.

Related workflow

For the Dispersion and Relative Strength Backtests Need Proxy Discipline workflow, continue through Options Backtesting API, Backtesting Framework, Backtesting Execution Realism, Backtesting Data Quality Checklist, Quote-Aware Options Backtests, and Backtest to Paper Trading Parity Checklist.

How the terminology applies

For Dispersion and Relative Strength Backtests Need Proxy Discipline, the backtesting workflow should treat Point-in-time contracts, Quote-aware fills, Reject reasons, Replay artifact, Cache key, and Signal timestamp as operational state rather than glossary decoration. That framing keeps the research claim causal: the strategy can only select instruments, prices, and labels that existed at the decision time.

A developer implementing this Strategy Research idea should persist Look-ahead leakage, Walk-forward test, Slippage model, Same-bar fill, Promotion gate, and Options data API beside the result, instead of leaving those words in a term card. It also turns attractive performance into an auditable record where fills, skips, thresholds, and replay inputs can be challenged independently.

The review artifact for Dispersion and Relative Strength Backtests Need Proxy Discipline becomes more useful when OPRA-originating data, OCC option symbol, Bid/ask spread, Midpoint, Quote/trade condition, and Quote vs trade semantics appear in the same body of evidence as the selected rows. When a result is promoted, these fields should appear in the run manifest, rather than a prose summary or final equity curve.

In production notes for this backtesting workflow, REST snapshot, WebSocket stream, Entitlement gate, Quote freshness, Timestamp semantics, and Pagination cursor define the checks that decide whether the workflow is reproducible. The result is a backtest that can be rerun, compared across threshold families, and rejected when the evidence is not strong enough.

For Dispersion and Relative Strength Backtests Need Proxy Discipline, the practical acceptance test is simple: another developer should be able to read the body, identify the exact inputs, reproduce the request sequence, and explain the accepted and rejected rows without relying on the bottom terminology grid. If a phrase appears in the page vocabulary, it should correspond to a stored field, a validation check, a replay step, or an implementation decision in the backtesting workflow.

This is also the reason the article should not measure success only by the final chart, table, or headline metric. The better standard is whether the data path, timing model, entitlement state, and evidence trail survive review. When those pieces are written directly into the body, the terminology becomes part of the workflow readers can implement.