Product overview

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

Lexicon, the Strategy Research Platform (SRP) from Prismark Systems, lets traders define setup logic from indicators, anchors, comparators, sequence, persistence, and entry rules, then run those definitions through historical tests.

Lexicon is not built around one signal. It is built around combining conditions into structured setup definitions using its Quant Definition Language (QDL).

Private BetaNo-code rule languageResearch software only

setup.logicLive language

ANDORTHENFOR N BARSENTER

AND and OR combine conditions into one setup definition.

THEN keeps ordered confirmation explicit.

FOR N BARS expresses persistence when a condition must hold long enough to matter.

ENTER marks the research entry action after the setup is satisfied.

Research workflowRepeatable

A structured research process, not a signal machine.

Definerule.define

State the setup as explicit, deterministic logic — indicators, anchors, sequence, and entry conditions.

Testhistory.run

Run the definition against historical data under visible assumptions about fills, slippage, and structure.

Reviewoutput.review

Read the output as evidence to examine, not as prediction. Note what held and what did not.

Refinevariable.adjust

Adjust one deliberate variable, then retest — so every change to the research stays visible.

Capabilities

Capability groups that combine into one setup definition.

The core feature is not one isolated trigger. It is the ability to describe what forms first, what confirms next, what must persist, and what turns that setup into a historical testable definition.

Indicators01

Build rules from familiar technical indicators and combine them with other rule types.

Anchors02

Reference prior-day levels, opening ranges, session highs and lows, and open-price anchors.

Timing03

Frame conditions with timing logic such as 90-minute levels and custom windows.

Sequence04

Keep ordered confirmation explicit: what forms first, what confirms next.

Persistence05

Require a condition to hold long enough to matter before an entry is allowed.

Trade Entry06

Shape how the historical test runs: direction, fill, stop, target, slippage, commission.

Reviewable Research07

Define, run, review, adjust one variable, and retest without a black-box feed.

DNA-Encoded Logic08

Every setup is encoded with a unique DNA signature, ensuring every backtest run is perfectly reproducible and deterministic.

QDL language surface

Indicators, anchors, comparators, and sequence primitives.

This section summarizes the Lexicon Beta QDL language surface: the indicators, anchors, comparators, and sequence tools available for building strategy rules. It is a public language-surface summary for Private Beta, not a claim that every indicator or every setup is already covered.

01 — Trend indicators

Moving-average and trend-style indicators help define directional context.

Trend indicators help describe whether price is above, below, reclaiming, rejecting, or holding around a directional reference. In the current public language surface, that includes moving-average and related trend-style references traders already recognize.

These are useful when combined with anchors, comparators, sequence, and persistence rather than treated as a one-line signal by themselves.

SMAEMAMACDADX

02 — Momentum indicators

Momentum conditions help describe strength, weakness, and confirmation.

Momentum indicators can help express whether a move is strengthening, weakening, stretching, or reverting. Examples already consistent with the current page include RSI, DMI/ADX-style momentum context, stochastic conditions, and related directional-strength checks.

RSIDMIADXSTOCHMACD

03 — Volatility indicators

Volatility and envelope indicators help describe expansion, compression, and band context.

Volatility indicators matter when a rule depends on range expansion, contraction, band interaction, or a change in trading conditions rather than just directional bias.

Public-facing examples here include Bollinger Bands, ATR, Keltner-style envelopes, and band-state language that can be combined with sequence and persistence rules.

ATRBBANDSKELTNERINSIDE_BANDEXPANSION

04 — Volume indicators

Volume and relative-volume context can support setup confirmation.

Volume-oriented language helps describe whether participation is increasing, fading, or behaving unusually relative to recent context.

This stays in the language surface as supporting context, not as fake proof or a promise that one volume read can decide a setup by itself.

RVOLOBVVOLUME

05 — VWAP

VWAP is a key intraday reference that works best when combined with structure.

VWAP is one of the most important intraday references in the Lexicon QDL language surface because traders often use it together with anchors, sequence, and persistence rather than as a standalone line.

A rule may use structures such as CLOSE CROSSUP VWAP for reclaim or cross-up behaviour, CLOSE CROSSDOWN VWAP for rejection or cross-back-below behaviour, and CLOSE > VWAP FOR 5 BARS for hold-above or persistence behaviour.

VWAPCLOSE CROSSUP VWAPCLOSE CROSSDOWN VWAPCLOSE > VWAP FOR 5 BARS

06 — Price-reference / structure

Price-reference logic exists, but it is secondary to the broader language surface.

Lexicon can express rule logic around price-reference and structure concepts, but raw OHLC fields are not the public feature pillar of this page. The main point is how price references interact with indicators, anchors, comparators, and sequence.

OPENHIGHLOWCLOSE

07 — Anchor families

Lexicon can express rules around the levels traders actually watch.

Anchor families are central to the language surface because many setups depend on prior levels, opening structure, session ranges, and time-window references rather than on indicators alone.

In plain language, that includes prior-day levels, current-day levels, prior-day close, current-day open, opening print, first 5-minute highs and lows, first 15-minute highs and lows, opening range highs and lows, custom window levels, session highs and lows, Asia/London/New York levels, NY AM / NY PM levels, 90-minute cycle levels, and open-price anchors.

PRIOR_DAY_LEVELSCURRENT_DAY_LEVELSPRIOR_DAY_CLOSECURRENT_DAY_OPENOPENING_PRINTFIRST_5M_HIGH_LOWFIRST_15M_HIGH_LOWOPENING_RANGE_HIGH_LOWCUSTOM_WINDOW_LEVELSSESSION_HIGHS_LOWSASIA_LONDON_NY_LEVELSNY_AM_NY_PM_LEVELSNINETY_MINUTE_CYCLE_LEVELSOPEN_PRICE_ANCHORS

08 — Comparator and qualifier families

The language surface describes how a condition behaved, not just where a value printed.

Comparator and qualifier families let a trader express whether something was greater than, less than, equal, not equal, crossing, holding, stretching, fading, or breaking for the first time.

This is what helps Lexicon describe setup behaviour more precisely than a single above/below test.

GREATER_THAN / LESS_THANEQUAL / NOT_EQUALCROSS_UP / CROSS_DOWNWITHIN_DISTANCESLOPE_UP / SLOPE_DOWNSTEEPENING / FLATTENINGOVERBOUGHT / OVERSOLDINCREASING / DECREASING / ACCELERATINGENVELOPE_STATESDUAL_SERIES_STATESFIRST_BREAK_ABOVE / FIRST_BREAK_BELOW

09 — Sequence and persistence

Multi-step setup rules depend on sequence and must-hold logic.

Sequence and persistence tools help a trader express that one condition happened, another condition followed, and the combined setup needed to persist long enough to matter before an entry is allowed.

These primitives are part of why the language surface is about structured setup definitions rather than one signal firing in isolation.

ANDORTHENFOR N BARSENTER

Example rule structures

Illustrative rule structures show how the language pieces can fit together.

setup.logic

Rule-language examples

01CLOSE > OPENING_RANGE_HIGH AND CLOSE > VWAP THEN CLOSE > OPENING_RANGE_HIGH FOR 2 BARS THEN ENTER LONG

02HIGH > PRIOR_DAY_HIGH THEN CLOSE < PRIOR_DAY_HIGH AND CLOSE < VWAP THEN ENTER SHORT

03CLOSE > SMA(200) AND RSI(2) < 10 THEN ENTER LONG EXIT WHEN RSI(2) > 70

Examples are illustrative target Beta rule structures, not trading recommendations.

Supported markets

Current market and data coverage.

The current research surface is controlled: structured historical testing for selected market and data contexts, not unlimited coverage or live trading.

Asset classes

Private Beta coverage is centered on the research surface currently being validated.

Intraday futures and index-linked context are the clearest fit today. Related references such as VIX, DXY, and SPY should be read as available research inputs where that dataset and workflow have been validated.

Intraday futuresIndex-linked contextVIXDXYSPY

Timeframes

The current surface is focused on structured historical testing rather than live trading.

Intraday master-bar workflows remain the clearest fit, especially where 1m, 5m, 15m, and 1H logic is being used to express sequence, timing windows, and setup context instead of one-off trigger conditions.

1m5m15m1H

Session awareness

Session and timing handling matter because many setups depend on context, not just direction.

CME Globex session boundaries, 17:00-18:00 ET maintenance gaps, and DST transitions remain important for anchor computation and timing-aware rule logic.

CME Globex17:00-18:00 ET gapDST transitionsAnchor computation

Methodology

How Lexicon keeps setup tests structured and reviewable.

Deterministic rule definitions

Setup definitions are explicit, repeatable, and encoded with a unique DNA signature.

Lexicon is built around deterministic rule definitions so the same setup can be reviewed, rerun, and compared without silent drift between tests.

The goal is not to describe a vague trading idea. The goal is to define the rule clearly enough that the logic, comparisons, sequence, and entry conditions can be evaluated the same way each time.

Historical test workflow

The core workflow is simple: define the rule, run the test, review the output, refine one variable, retest.

Historical testing is meant to support a disciplined research loop. A trader defines the setup, runs the historical test, reviews the output, adjusts one variable, and retests.

That structure matters because it keeps research changes visible. It is easier to understand what changed, what stayed stable, and whether a result improved because of one deliberate adjustment or because the logic drifted in multiple directions at once.

Sequence and persistence

Multi-step setups need ordered logic and must-hold conditions.

Many setups are not one-condition events. One condition can happen first, another can follow, and the setup can be required to persist long enough to matter before an entry is allowed.

That is why sequence and persistence matter. The methodology assumes that ordered logic such as AND, OR, THEN, FOR N bars, and ENTER should remain visible in the QDL setup definition.

Anchor and timing logic

Setup context should reflect the levels and timing references traders actually watch.

Anchor and timing logic matter because many setups depend on prior-day levels, opening ranges, session highs and lows, VWAP context, first-window highs or lows, and other time-aware reference points rather than on one indicator alone.

Reference anchors are meant to stay tied to information that would have been available at the time of the test. The purpose is to keep setup context realistic and reviewable.

Assumptions and limitations

Historical tests are useful research evidence, but they do not remove uncertainty.

Historical tests depend on assumptions about price data, bar structure, fill behaviour, slippage, commissions, and how a rule is interpreted. Those assumptions need to stay visible because they affect what a result can and cannot support.

Lexicon does not present historical output as prediction. Historical tests are evidence to review, not predictions.

Limitations and risk

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

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

Historical tests are not predictions

How Lexicon keeps research conclusions in bounds.

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.

evidence != prediction

Execution assumptions matter

How Lexicon keeps research conclusions in bounds.

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

Data quality matters

How Lexicon keeps research conclusions in bounds.

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.

coverage, revisions, survivorship

Curve fitting risk

How Lexicon keeps research conclusions in bounds.

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.

in-sample != out-of-sample

Beta limitations

How Lexicon keeps research conclusions in bounds.

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

status: private_beta

User responsibility

How Lexicon keeps research conclusions in bounds.

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

user retains responsibility

Private Beta

Apply if you want to help validate the workflow and language surface.

Private Beta access is for traders who can explain their setup logic clearly and give useful feedback on how the product should express, test, and review that logic.

Apply for Beta

Private BetaResearch software onlyExamples are illustrative rule structures