NQ FUTURES INTELLIGENCE

NQ Futures Intelligence

AuraBot maintains one live, reconciled market state for Nasdaq-100 futures (NQ and MNQ) through the New York session, so you know where NQ is relative to liquidity, which side the auction is on, and whether conditions currently permit an entry. It is context and execution permission, not a stream of alerts.

What "intelligence" means here

Most NQ tools produce events: a line is crossed, an alert fires, a label prints. Each event is a fragment the trader has to assemble into a decision while price is moving. Intelligence is one state, held continuously, that already reflects everything the engines have read.

For NQ, that state runs through a fixed sequence: WAIT → WATCH → ARMED → ACTIVE → MANAGING → COMPLETE / INVALIDATED. It moves only when the evidence moves. If nothing material has changed, nothing is sent. A quiet message is information too.

How the three engines read NQ

Three invite-only TradingView engines feed a shared Aura backend. Each answers a different question, and NQ session mechanics give each one specific work to do.

Anchor Rails — Location

Tracks the overnight high and low, the prior-day high, low and close, session extremes, and the destinations price is drawn toward. On NQ the overnight range is the first thing that matters at 9:30 ET, because the open so often runs one side of it before doing anything else.

SKELETON — Direction

Reads structure, displacement, and acceptance versus rejection to determine which side of the auction is in control. A sweep of the overnight low that is followed by displacement back into the range tells a different story than a sweep that is accepted and built on. SKELETON is the engine that distinguishes the two.

Black Book — Execution

Evaluates execution context and cues, and decides whether current conditions actually permit an entry. Location and direction can both line up while execution permission is still withheld.

The 9:30 open and the 10:00 ET decision

NQ's first thirty minutes are where the session's first real evidence shows up. A typical read looks like this:

  1. Pre-9:30. Rails has the overnight high and low and the prior-day levels marked. The state is WAIT. There is context, but no auction evidence yet.
  2. 9:30 to roughly 10:00. Price runs the overnight high. Rails registers the sweep and moves the state to WATCH. SKELETON is now looking for one of two things: acceptance above the level (price holds, builds, continues) or rejection (displacement back inside the range).
  3. Around 10:00 ET. This is the decision window. If SKELETON reads rejection and Black Book confirms execution context, the state can move to ARMED and then ACTIVE. If SKELETON reads acceptance instead, the earlier scenario is INVALIDATED and the state resets rather than forcing a trade.

Note what did not happen in that sequence: the sweep itself never triggered an entry. The sweep changed location. Only auction evidence changed execution permission.

Doctrine

Knowing the destination is not the same as knowing the entry. NQ touching or sweeping the overnight high is a location fact. It does not mean reverse. Aura waits for acceptance or rejection, displacement, and structure before changing execution permission, and the trader remains responsible for execution.

What the #nq-intelligence message looks like

In Discord there is one persistent live message for NQ in #nq-intelligence. It is edited in place as conditions materially change, so you are always reading the current state rather than scrolling through a history of stale calls. In practice it carries:

  • The current state (WAIT, WATCH, ARMED, ACTIVE, MANAGING, COMPLETE or INVALIDATED).
  • Location context from Rails: which levels are in play, what has been swept, what the current destination is.
  • Direction context from SKELETON: the market story and whether price is showing acceptance or rejection at the relevant area.
  • Execution context from Black Book: whether entry is currently permitted and what would change that.

Separate notifications go out only for meaningful decision changes or execution-critical events. A move from WATCH to ARMED is meaningful; a tick through a level is not. Morning context for both instruments lands earlier in #daily-market-brief, and every session is retained in persistent storage for review.

What it does not do

Being specific about limits keeps the tool useful.

  • It does not place trades. AuraBot is not a broker and does not connect to your account.
  • It does not predict price. The Hologram Candle system projects a structural scenario forward; projection is not prediction.
  • It does not fire an alert on every level touch. If you want a dozen pings before 10:00 ET, this is the wrong product.
  • It does not size your position, manage your risk, or know your funded-account rules. Those remain yours.
  • It is not affiliated with TradingView, Topstep or any funded-account provider.

Questions

Does the NQ state also cover MNQ?

Yes. MNQ is the micro contract on the same underlying, so the location, direction and execution read is identical. The only difference is the contract size you choose to trade.

Why does the state sometimes sit in WATCH for a long time?

Because location has changed but the auction has not yet shown acceptance or rejection. WATCH means a scenario is on the table and the evidence is not in. Forcing the state forward without evidence is exactly what the system is built to avoid.

What happens after the 10:00 ET window if nothing sets up?

The state stays in WAIT or WATCH and the message says so. Rails keeps tracking levels through the session, and a later sweep of the prior-day high or low can start a new scenario.