FUTURES TRADING INTELLIGENCE
Futures Trading Intelligence
Futures trading intelligence is a continuously maintained read of an instrument's direction, location and execution conditions, reconciled into one decision state. It is distinct from indicators, signals and alerts, each of which hands you a fragment and leaves the reconciliation to you.
Four things that get called intelligence
The word gets used loosely, so it helps to separate what it is from what it is not.
Indicators
Transform price into a line or a label on the chart. An indicator shows you something; it does not decide anything. Ten indicators are ten opinions with no referee.
Signals
Compress a decision into a single instruction: buy, sell. The reasoning is hidden, so a signal cannot tell you when it has stopped being valid, and you cannot learn from it.
Alerts
Fire when a condition is met: a level touched, a crossover, a break. Alerts are events. They arrive in the order things happen, not in the order things matter, and each one asks you to re-evaluate everything.
Intelligence
Holds a single state that already reflects direction, location and execution together, and changes that state only when the evidence changes. You read the state, not the events.
Why one reconciled state beats many alerts
Picture the first half hour of the New York session on NQ. A level alert fires when the overnight high is touched. A structure tool fires on a break. A momentum tool fires on a displacement candle. Three alerts, and the actual question, whether conditions permit an entry, is still unanswered. Worse, the alerts can disagree, and nothing in the alert model resolves that.
A reconciled state answers the question directly. If location has changed (a sweep) but direction has not confirmed (no acceptance or rejection yet), the state reads WATCH. If direction confirms and execution context lines up, it reads ARMED. If direction goes the other way, it reads INVALIDATED. The trader is never assembling fragments in real time; the assembly has already happened.
This also fixes the noise problem. Alerts are noisy by construction, because every condition met is an event. A state is quiet by construction, because most events do not change it.
Doctrine
Knowing the destination is not the same as knowing the entry. A level being approached, touched or swept is a location fact, and location alone never changes execution permission. Intelligence waits for evidence from the auction, acceptance or rejection, displacement and structure, before changing state. The trader remains responsible for execution.
The order matters: direction, location, execution
Intelligence combines three reads in a fixed order. Direction first, because a level means something different depending on which side of the auction is in control. Location second, because it tells you where a scenario can begin and where it is wrong. Execution last, because it is the gate that decides whether all of that permits an entry right now. Reverse the order and you get the classic failure: entering at a level because it is a level.
Session memory and research
Alerts leave no history worth studying. An intelligence system does, because every state change records what the evidence looked like at the time. Persistent session storage means a trader can go back and see how long WATCH lasted before ARMED, which scenarios were invalidated and why, and where their own execution diverged from the state. Research on retained sessions separates intelligence from a tool that only exists in the present tense.
How AuraBot implements it for NQ and gold
AuraBot runs three invite-only TradingView engines that feed a shared Aura backend:
- Anchor Rails handles location: liquidity, session highs and lows, prior-day high, low and close, sweeps and destinations.
- SKELETON handles direction and auction state: structure, displacement, acceptance versus rejection, the current market story.
- Black Book handles execution: context, cues, and whether conditions permit an entry.
The backend reconciles these into one live state per instrument, WAIT → WATCH → ARMED → ACTIVE → MANAGING → COMPLETE / INVALIDATED, for NQ (including MNQ) and Gold (GC and MGC), built for the New York session. In Discord, each instrument has one persistent live message, in #nq-intelligence and #gold-intelligence, updated in place as conditions materially change. A combined morning context posts to #daily-market-brief. Separate notifications are reserved for meaningful decision changes or execution-critical events. Sessions are retained in persistent storage for review and research.
Alongside the engines sits the Hologram Candle projection system, which draws a structural scenario path forward from live structure, session and volatility inputs. It is projection, not prediction, and it is there to make scenarios visible, not to forecast price.
What intelligence is not
It does not place trades. It is not a broker. It does not predict price. It does not replace the trader's rules on risk, sizing or funded-account constraints. AuraBot is not affiliated with TradingView, Topstep or any funded-account provider. Intelligence narrows the decision to one state; the trader still makes it.
Questions
Is futures trading intelligence just a fancier alert system?
No. Alerts report events. Intelligence maintains a state and changes it only on evidence. The practical difference is that you read one current answer instead of reconciling a stream of events yourself.
Why only NQ and gold?
Because the engines are built around the session mechanics of those two instruments during the New York session: the overnight range, prior-day levels, the 9:30 ET open and how each instrument accepts or rejects a level. Depth on two instruments is the product, not breadth across many.
Can I still use my own indicators alongside it?
Yes. The engines run on TradingView and the state lives in Discord; keep whatever chart setup you like. The state resolves the question indicators leave open: whether an entry is currently permitted.