A no-code rule language for multi-step trading setups.

Build from familiar indicator ingredients, then combine them into setup logic.

Lexicon's Quant Definition Language (QDL) is meant to start from familiar technical indicators rather than from custom code. Traders can combine indicator conditions with timing logic, anchor references, and ordered confirmations so the definition reflects the setup they are actually trying to test.

The point is not to elevate one indicator into a public-facing promise. The point is to let a trader combine indicators with other rule types inside a broader setup definition.

Use the reference levels traders already organize their decisions around.

Lexicon is shaped to test rules against anchor levels traders already watch on the chart, including prior-day highs and lows, opening ranges, session highs and lows, 90-minute levels, custom windows, and open-price anchors.

That keeps the rule closer to the real setup context instead of collapsing everything into one generic threshold detached from the chart structure.

Describe how a condition behaved, not just whether a number was above or below.

The QDL rule surface is intended to cover comparator language traders actually use when describing setups. A condition may cross, hold, expand, compress, move within a distance band, slope, accelerate, or break a level for the first time.

That vocabulary matters because many setups depend on how a level or indicator is approached, held, or rejected, not just on a static comparison snapshot.

Multi-step setup logic is the point of the QDL language surface.

Lexicon is being built for setups where one condition happens, another condition follows, and the setup may need to persist long enough to matter before an entry rule is allowed.

After the setup is defined, entry settings can frame the backtest.

Once the setup logic is defined, trade-entry settings can shape how the historical test is run: direction, fill method, stop, target, slippage, commission, and an optional trailing stop.

This is presented as research and backtesting workflow configuration, not as live execution or automated trading. The point is to define how the test should be evaluated once the setup criteria are satisfied.

Define the setup, run the test, review the result, adjust one variable, retest.

The workflow is meant to be iterative and reviewable: define the setup, run the historical test, inspect the result, change one variable, and retest.

Lexicon is being built around research review rather than around hype, signals, or a claim that one pass through history should settle the question permanently.