NQ TRADING SYSTEM

NQ Trading System

A complete NQ trading system answers four questions in order: which way is the auction leaning, where is price relative to liquidity, do current conditions permit an entry, and what rules govern the trade once it is on. AuraBot's TradingView engines and live state cover the first three. The fourth stays with the trader.

A signal is not a system

Searches for an "NQ trading system" mostly return signal services. A signal is one output: buy here, sell there. It hides every judgment that produced it, so when it fails you learn nothing. A system is a set of components that each do one job, combined in a fixed order, so the decision is visible and repeatable.

For NQ, that order is Direction → Location → Execution → one live decision state. Execute on a level touch before direction is known and the same components produce worse results.

The four parts

Direction

Which side of the auction is in control, read from structure, displacement and acceptance or rejection at the levels that matter. Direction is not a morning bias you defend all day; it changes when the evidence changes.

Location

Where price is relative to the overnight high and low, prior-day levels and session extremes. Location tells you where a scenario can begin and where it would be wrong. It never tells you to enter.

Execution

Whether current conditions permit an entry at all. Direction and location can agree while execution is still withheld because displacement or structure has not confirmed. This is the gate most NQ traders skip.

Rules

Position size, risk per trade, daily loss limits, when to stop, and the constraints of any funded account. These are not derived from the chart and no engine can supply them.

How AuraBot supplies the first three

Three invite-only TradingView engines each own one part.

  • SKELETON owns direction. It reads structure, displacement and acceptance versus rejection to describe the current market story on NQ.
  • Anchor Rails owns location. It tracks liquidity, session levels, sweeps and destinations and shows where price is relative to areas that matter.
  • Black Book owns execution. It evaluates execution context and cues and decides whether conditions permit an entry.

The backend combines the three into one live state per instrument: WAIT → WATCH → ARMED → ACTIVE → MANAGING → COMPLETE / INVALIDATED, published as a single persistent message in #nq-intelligence on Discord and updated as conditions materially change. That state is the decision layer that turns three reads into one answer.

A worked NQ sequence

NQ opens at 9:30 ET inside the overnight range and runs the overnight low in the first fifteen minutes.

  1. Rails marks the sweep. Location has changed. The state moves from WAIT to WATCH. No entry.
  2. SKELETON evaluates the response. Price displaces back up through the low and reclaims the range. That is rejection with displacement, and direction now favors the upside for this scenario.
  3. Black Book evaluates execution context. If cues line up, the state moves to ARMED and then ACTIVE. If not, it holds at WATCH and the message says why.
  4. The trader decides whether to take the trade, sizes it under their own rules, and executes. Once in, the state moves to MANAGING with the prior-day high as the destination Rails tracks.
  5. Either the destination is reached (COMPLETE) or structure breaks against the scenario (INVALIDATED). Both are recorded in persistent storage.

If instead price had accepted below the overnight low with continued displacement, the long scenario would have been invalidated before it was ever armed. Keeping the trader out is the system doing its job.

Doctrine

Knowing the destination is not the same as knowing the entry. A system that enters because a level was reached is a signal wearing a system's clothes. Aura waits for acceptance or rejection, displacement and structure before changing execution permission, and the trader remains responsible for execution.

What the trader still owns

This is the fourth component of the system and the one no software can provide.

  • Risk. How much is at stake per trade and per day is a decision about your account, not about NQ.
  • Execution. AuraBot does not place trades and is not a broker. Order type, fill, and management are yours.
  • Funded-account rules. Loss limits, drawdown and consistency requirements vary by provider. AuraBot is not affiliated with Topstep or any funded-account provider, and the live state does not know your rules. A valid ACTIVE state can still be a trade your evaluation does not allow.
  • The decision to pass. ARMED is permission, not obligation.

Supporting tools

Membership also includes the Hologram Candle projection system (a structural scenario path drawn forward from live inputs; projection, not prediction), TrendGlow for multi-timeframe bias, Smart Zones, CyberStructure, Order Blocks, session filters, SL/TP plotting and Battle Loadouts preset configs, plus AuraSzn Academy, Mindset Lab and the Momentum OS planner for the rules layer. They support the system; the three engines and the live state are the system.

Questions

Is this a mechanical system I can follow blindly?

No. The engines and the live state make direction, location and execution permission explicit, but the trader decides whether to take a trade and how to size it. Following any state blindly ignores the rules component only you can supply.

What timeframe does the NQ system work on?

It is built around the New York session and the levels that define it: the overnight range, prior-day levels and session extremes. The state is about session-level scenarios rather than a single fixed chart interval.

How is this different from just using the TradingView tools?

The tools show what each engine sees on the chart. The live state reconciles all three into one decision state in Discord. The system is the combination, not any single script.