Backtesting limitations

A backtest is evidence to review, not a prediction to trust blindly.

This page is intentionally direct. Lexicon is in Private Beta, and backtest output remains research material shaped by assumptions, data quality, execution modelling, and user judgment.

Private BetaResearch software onlyUser responsibility remains
Risk document6 sections
01
Historical tests are not predictions

A historical result can be useful evidence without becoming future certainty.

A backtest can help show how a setup definition behaved under prior conditions, but it does not tell a trader what must happen next. Historical tests are evidence to review, not predictions to trust blindly.

That is why Lexicon is framed as research software only. Examples and outputs are research material, not trading recommendations.

evidence != prediction
02
Execution assumptions matter

A backtest cannot fully recreate real execution friction.

Historical tests still depend on assumptions about fills, slippage, spread, latency, commissions, and how a rule is evaluated inside bar-based data. Those assumptions can materially change what a result means.

Practical implication

A clean historical result should not be mistaken for a live execution guarantee. Execution drag, liquidity, queue position, and other market frictions can reduce real-world performance.

fills · slippage · spread · latency
03
Data quality matters

Historical datasets can still carry blind spots, omissions, and simplifications.

Backtests depend on the quality and completeness of the underlying data. Missing instruments, revised data, survivorship effects, session-boundary assumptions, and other dataset limitations can distort what appears to be a stable historical result.

For that reason, a clean output should be read as a research artifact built on available data, not as proof that every relevant historical path has been captured perfectly.

coverage · revisions · survivorship
04
Curve fitting risk

A more structured rule definition does not remove overfitting risk.

Even a well-defined strategy can be tuned too closely to prior data. A setup can look persuasive in-sample, then weaken when conditions change or when the same idea is reviewed out of sample.

Lexicon can support a more disciplined workflow, but it cannot stop a user from over-optimizing a rule or mistaking historical fit for durable edge.

in-sample != out-of-sample
05
Beta limitations

Private Beta software should be read with additional caution.

Lexicon is in Private Beta. That means the research workflow, supported language surface, and reporting experience are still being reviewed and refined.

Beta status is another reason not to over-read outputs. The product is not a profit system, does not offer guaranteed results, and should not be treated as a finished authority on every setup or market condition.

status: private_beta
06
User responsibility

Structured research still requires skepticism, judgment, and responsibility.

Lexicon is research software only. It is not signals, not financial advice, not a profit system, and offers no guaranteed results.

Users remain responsible for reviewing assumptions, questioning results, and avoiding the mistake of treating research material as a recommendation. Examples and outputs are research material, not trading recommendations.

user retains responsibility
Trust note

Serious research starts with clear limitations, not hidden certainty.

Private Beta is for traders who want a more structured research workflow and who are comfortable reviewing outputs critically instead of treating them as promises.

Private BetaResearch software onlyResearch material, not trading recommendations