Modules
Eight modules. One state machine.
ATLAS is not a bundle of separate indicators — every module feeds the same setup sequence: context defines direction, location defines where, confirmation defines when, and risk defines when to stop. This page is the technical detail.
Context / 01
HTF Bias Engine
Reads 4H and 1H market structure and maintains a live directional bias. Every downstream signal is gated by it: if the higher timeframe says long, ATLAS will not print a short.
Most losing intraday trades are structurally fine on the entry timeframe and wrong on the one above it. The bias engine makes that filter automatic instead of a discipline test.
| Bias timeframes | 4H and 1H structure read, independent of your chart timeframe |
| Structure lookback | Swing depth used to define higher-timeframe highs and lows |
| Bias display | Optional on-chart bias markers |
Context / 02
Liquidity & Sweeps
Tracks equal highs and equal lows plus multi-timeframe swing points — the levels where resting liquidity accumulates — and flags the moment one is swept.
A sweep is the event that starts an ATLAS setup: the framework treats the run on liquidity as the trigger to start looking for an entry, not as the entry itself.
| Equal high/low tolerance | How close two highs or lows must be to count as a liquidity pool |
| Swing timeframes | Which timeframes contribute swing points to the liquidity map |
| Sweep display | Level lines and sweep markers on chart |
Location / 03
Order Blocks / FVG
Locates order blocks and fair value gaps and tracks them live — fresh, tapped, or mitigated. These zones are the only places ATLAS permits an entry sequence to begin.
Location discipline is what separates a framework from a signal generator. By constraining entries to mapped zones, every signal has a structural reason to exist at that price.
| Zone timeframes | Which timeframes produce order blocks and FVGs |
| Mitigation tracking | How a zone is retired once price has traded through it |
| Zone display | Zone boxes, labels, and maximum zones kept on chart |
Confirmation / 04
MicroBOS Confirmation
The entry sequence. After a sweep and a tap into a valid zone, ATLAS waits for a micro break of structure in the bias direction. Only when that sequence completes does a signal print.
Touching a zone is not evidence — plenty of zones fail. The MicroBOS requirement means the market has already turned on the micro timeframe before you're shown an entry, trading later fills for materially fewer fakeouts.
| Sequence strictness | How complete the sweep → tap → break sequence must be |
| Micro structure depth | Swing size that defines the structure being broken |
| Signal output | On-chart signal markers and TradingView alerts |
Flow / 05
CVD Volume Delta
Cumulative volume delta running alongside the structure read — a live measure of whether aggressive buyers or sellers are actually in control while your setup forms.
Structure says where; flow says who. A long signal into rising CVD and a long signal into heavy selling are different trades, and CVD makes that difference visible on the chart before entry.
| Delta source | Timeframe and reset basis for the cumulative delta |
| Divergence display | Optional flagging of price/CVD disagreement |
Value / 06
Value Area Context
Positions the session against its value area — above value, below value, or inside it — and displays that context on chart alongside every setup.
The same entry means different things in premium and in discount. Value area context tells you whether you're buying a discount or chasing an extension, without leaving the chart.
| Value basis | Session used to build the value area |
| Display | Value area levels rendered on chart |
Filter / 07
Session Bias Confidence
Session windows restrict when ATLAS is allowed to signal, and a composite confidence readout reports how strongly the framework's layers currently agree.
Not all hours are tradable and not all signals are equal. The confidence readout turns "how good is this setup?" from a feeling into a number you can set a personal floor on.
| Session windows | Which sessions (e.g. London, New York) can produce signals |
| Confidence weighting | How bias, flow, and value context combine into the readout |
Risk / 08
Risk & Kill-Switch
Per-day trade limits and a daily kill-switch. When the limit is hit or the kill-switch condition triggers, ATLAS stops offering signals until the next session.
The most expensive trades of a losing day are the ones after the day was already lost. The kill-switch makes stopping a property of the instrument instead of a promise to yourself — and if you trade prop-firm evals, these are the same daily rules your funder enforces, applied before the funder has to.
| Trade limit | Maximum signals per day |
| Kill-switch | Daily shutdown condition and reset time |
| On-chart status | Trades-used counter and kill-switch indicator |