The first algorithm born on Atlas
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.
New here? Atlas is TradeScope's proprietary quantitative level engine. It maps the price locations where market behaviour may become meaningful. Sentinel is one algorithm built on that map.
Meet AtlasWhat 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.
And most never qualify.
- 01
The break itself has to prove it
A boundary event only counts if a completed 5-minute bar closes through structure by a minimum displacement threshold, measured against the boundary itself, not the candle's body. Wicks, pokes, and marginal closes are rejected outright or placed under follow-through watch. No confirmation, no state change.
- 02
The level map gets scored
On a confirmed break, every Atlas level runs through a qualification stack: position inside the retest band defined by the break bar's range, side-of-structure validity, a minimum confidence floor, and proximity clustering against neighboring levels. This is a filter cascade, not a vibe. Most levels fail it, and every failure is discarded with the rejection reason logged. The single survivor becomes the entry, working as a resting limit at the retest, priced before the pullback happens. Sentinel does not chase.
- 03
No survivor? It escalates on evidence, once
Setup 2 arms a one-shot confirmation window on the candidate level: the next 5-minute close must land beyond it, proving the demand or supply is real. One bar, hard expiry. Close confirms, entry. Close fails, the window dies worthless. No trade.
- 04
One structural re-entry, with a kill switch
If stages one and two pass without filling, Sentinel watches for exactly one disciplined re-entry at the structure, inside strict approach and penetration tolerances. First valid touch only. The watch disarms itself if price runs too far or too long without offering the entry. An expired setup is a dead setup, never revived.
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.
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.
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