Skip to content
Available now

Systematic intraday execution on NQ

Meridian.

One instrument. One session. The same process every day, without discretion.

A fully automated intraday strategy for Nasdaq-100 futures. Where Sentinel resolves trade by trade, Meridian measures the session — and most days it decides there is nothing to do.

39 recorded trading days, wins and losses both. Built from Meridian’s own logged sessions and reviewed before publication.

See the record

The process

It doesn’t forecast.
It measures.

  1. 01

    It measures, it does not forecast

    Each session Meridian derives a structural reference from the market’s own price action. No prediction, no opinion about where price should go.

  2. 02

    It holds fire until structure resolves

    Nothing happens until price resolves that structure decisively. Most of the strategy’s day is spent not trading.

  3. 03

    It waits for the retracement

    On resolution it projects a defined objective zone from the measured structure and works a limit order back into it — entering on the retracement rather than chasing the extension. If price never returns to the level, there is no trade that day.

  4. 04

    Risk exists before the position does

    Every entry carries a predetermined stop and a target at a fixed 2:1 reward-to-risk, with identical size on every trade.

  5. 05

    It stands down when it is done

    Position count per session is strictly capped, and the strategy stops for the day once its objective is met. No re-entry past the daily limit, no averaging down, no discretionary override.

where atlas comes in

Meridian measures its own structure — that part is its own engine, not Atlas. Atlas enters at the objective: when a qualifying Atlas level sits within range of the projected zone, Meridian anchors to it instead. So Atlas does not tell Meridian whether to trade. It sharpens where Meridian is aiming when the map has something to say.

This is a narrower relationship than Sentinel’s, and it is stated narrowly on purpose. Meet Atlas →

The engineering

Built like infrastructure,
not a script.

Deterministic state machine

Identical inputs produce identical decisions, every session.

121/121 automated test coverage

Across the full state and execution surface.

Shadow mode

Every change is validated against live market data in simulation before it touches capital.

Complete audit trail

Every state transition, order, and fill recorded.

Fail-open isolation

Reporting or connectivity faults cannot reach the execution path.

Restart reconciliation

Position and session state recover cleanly after any interruption.

Every claim in this section is verified against the code. None of it is a performance claim — engineering discipline is not an edge, and a well-built strategy can still lose money.

How it differs from Sentinel

Two strategies, one foundation underneath. This is what changes when the objective changes — and it is the same room a creator’s own system would be designed in.

meridian

  • One session, one instrument, capped position count
  • Enters on the retracement, never the extension
  • Fixed 2:1 reward-to-risk, identical size every trade
  • Atlas anchors the objective when it is in range
  • 39 days of logged sessions, summarized by day outcome

sentinel

  • Autonomous execution on dedicated infrastructure
  • Three-stage qualification cascade per trade
  • Trades qualified Atlas locations directly
  • Row-level record, trade by trade
  • Full Sentinel page →

standardized outputs · no account connections · you place your own trades · not personalized advice