Skip to content
Available now

The first algorithm born on Atlas

Sentinel.

A mechanical NQ/MNQ algorithm built on Atlas-powered market structure. Risk defined at entry. Discipline as code.

Sentinel is our cloud algo, and that matters more than any indicator ever could. It is not a signal service and not a co-pilot. It is the strategy itself: compiled, always-on, executing on dedicated infrastructure through a live exchange data feed, 24/5, with no human at the screen. No emotion, no hesitation, no fatigue, no revenge trades at 2 a.m.

The strategy isn't a person following rules. The strategy is the rules, running.

Follow the Sentinel LogGet access

New here? Atlas finds where opportunity may develop. Sentinel decides whether the conditions justify a trade. Atlas is the private quantitative foundation; Sentinel is one implementation built on it — with its own qualification, confirmation, direction, entries, risk, management, invalidation, and exits.

Meet Atlas

What it watches

Two things. Nothing else.

Atlas levels: a curated map of structural price levels, maintained by hand and read by machine. And the structural boundaries where price has to make a decision. Sentinel doesn't guess where those decisions happen. It waits for price to confirm one.

How it fires

It does not trade Atlas levels.
It trades qualified Atlas levels.

And most never qualify.

sentinel / decision_cascadescroll drives the sequence
01

The break has to prove it

most events fail here

A completed 5-minute close through structure by a minimum displacement. Wicks and pokes are rejected.

02

The level map gets scored

most levels fail here

Every Atlas level runs a qualification stack. Most fail. The single survivor becomes the entry.

03

One confirmation window

hard expiry

No survivor? One bar to prove demand or supply is real. Close fails, the window dies worthless.

04

One re-entry, with a kill switch

never revived

First valid touch only. If price runs too far or too long, the watch disarms. Dead setups stay dead.

Only the survivors fire.

Deterministic. Every rejection logged with its reason. Flat is a position.

Every decision in the cascade is deterministic: same inputs, same output, every rejection logged with its reason. Across the whole pipeline the default answer is no. Sentinel is engineered to refuse trades, and the ones that survive all of it are the only ones that fire.

Flat is a position.

Risk defined at birth

Every position is born protected.

Every position is born with a hard protective stop. Risk defined at entry, typically 25 points, never widened after. From there, a mechanical trailing engine advances the stop in stages as the trade develops and lets runners ride. A dedicated safety layer continuously enforces one invariant: no position rides unprotected. If a protective stop is ever lost, the automation moves immediately to close the position.

One trade at a time. A per-structure lockout keeps it from over-trading the same idea. Cooldowns are designed to prevent chop and revenge sequences before they start.

What access means

You get the outputs.
You stay in control.

Sentinel runs on our infrastructure and trades its own execution there. Access never connects to your brokerage, and nothing executes on your account. Members receive Sentinel's actions as standardized outputs, delivered through a webhook feed from our server and mirrored in the Sentinel Log: the same steps, to everyone, at the same time. Whether and how you act on them is entirely up to you, on your own platform, at your own risk.

  • Webhook feed from our server
  • Mirrored in the Sentinel Log
  • No account connection
  • No execution on your account
  • Same output for everyone

Same strategy. Same data. Same output. Your decision.

Recent stats

The last month, on the record.

2026-06-15 to 2026-07-15, presented on 10 MNQ micros: five contracts scale at +50, five ride the trail. Every trade, including the losses, is in the record.

completed trades
26
trade win rate
80.77%
profit factor
16.45
net · stated assumptions
$38,630

How the position works

  1. 01

    Entry · 10 MNQ

    The full position enters with risk defined: a hard stop at -25 points per contract, never widened.

  2. 02

    +50 · five bank the scale

    At +50 points, five contracts exit. The trade is now paying for itself.

  3. 03

    Then the trail takes over

    Once the scale is done, the remaining five follow the trailing method until it says done. That is where the big runs come from.

Methodology and assumptions
  • Presented on 10 MNQ micros at $2 per point per contract: five exit at +50, five follow the trail
  • The micro split is what makes the trailing method practical at accessible size
  • The trailing exit’s exact method stays private
  • Standard loss is -25 points per contract
  • USD is derived from the recorded point outcomes under this position assumption; the source recorded the same points under 2 NQ minis
  • Fixed +70 and +100 runner alternatives modeled for comparison
  • Rebuilt retrospectively from the owner’s historical trade records
See the full recordRebuilt from owner records · not broker-verified · historical, not a guarantee

The Sentinel Log

An audit trail, not a highlight reel.

Every action Sentinel takes is posted to the Sentinel Log on the TradeScope Discord, a record of the automation's own trading. No cherry-picking:

  • Entries with the risk stated up front
  • Progress in points and R-multiples, size-agnostic
  • A 2R milestone marker
  • Every stop advance
  • Every final result. Wins post. Losses post too.
  • Including the days it refuses everything

Code doesn't need conviction. It needs rules.

Follow the Sentinel LogGet access

the sentinel log is a factual record of an automation's own activity, shared for transparency. it is informational only, not financial advice, and not a signal service.