LEARN · METHOD

How AuraBot Uses Direction → Location → Execution

AuraBot reads NQ and Gold in three layers — which way the auction is leaning, where price sits relative to the levels that matter, and whether conditions permit an entry — then reconciles them into one live state per instrument. This is what each layer does, how they combine, and what is still your job.

Why three questions instead of one signal

Most losing trades are built on one good answer and two assumptions. A trader sees a level, assumes the direction, assumes the entry is fine, and clicks. AuraBot separates the three questions on purpose, because each is read from different evidence and each can be wrong on its own.

The questions are: Direction (which side is the auction on?), Location (where is price relative to liquidity and session levels?) and Execution (do current conditions actually permit an entry?). Each has its own TradingView engine. All three feed a shared backend.

Direction — SKELETON

SKELETON reads the auction state. It tracks structure (the sequence of swing highs and lows), displacement (fast, one-sided movement that leaves the prior area behind), and acceptance versus rejection (whether price holds a new area or gets pushed back out). From those it maintains the current market story: buyers in control, sellers in control, or unresolved.

Example: NQ opens at 9:30 ET, displaces above the overnight high and builds higher lows above it. SKELETON reads that as acceptance and the story shifts toward the buy side. If the same push had been rejected back below the overnight high within minutes, the story would not have changed.

Location — Anchor Rails

Anchor Rails handles where price is. It maps session highs and lows (Asia, London, New York), the prior-day high, low and close, and other areas where resting orders sit. It tracks destinations — the levels price appears to be travelling toward — and it records sweeps, when a level gets taken and price either holds beyond it or snaps back.

Location on its own is not a trade. Gold drifting up into the London high is a location fact. What happens at the London high is a direction fact. Keeping them separate is the point.

Execution — Black Book

Black Book handles execution context and cues. Its job is the last question: given the direction story and the location, do current conditions permit an entry right now? That is what execution permission means. Permission can be withheld even when direction and location line up — when price has already displaced far from the level and an entry would be chasing, or when the auction has not yet shown a clear response at the destination.

How the backend reconciles the three

The engines publish into a shared Aura backend, which holds one live market state per instrument:

• WAIT — no scenario in play.
• WATCH — price is approaching a mapped location and a scenario is being evaluated.
• ARMED — direction and location have lined up; execution context is being checked.
• ACTIVE — execution permission is on; the scenario is live.
• MANAGING — the scenario is being tracked toward its destination.
• COMPLETE / INVALIDATED — the destination was reached, or the auction produced evidence against the scenario and it was dropped.

The state only moves when evidence changes. Price touching a level does not move it. Acceptance, rejection, displacement or a structure change does. Session history is stored, so a state sequence can be reviewed afterwards.

What a state change looks like in Discord

Each instrument has one persistent live message — #nq-intelligence for NQ, #gold-intelligence for Gold. The message is edited in place as conditions materially change, so you read the current state rather than scrolling a feed. A separate notification goes out only for a meaningful decision change or an execution-critical event.

A morning might read like this: the NQ message sits in WATCH as price works toward the prior-day high. Price sweeps it and holds above; SKELETON reads acceptance; the message updates to ARMED. Black Book confirms execution context and the message moves to ACTIVE, with a notification. If instead price had swept the level and rejected sharply, the message would have shown the scenario invalidated and returned to WAIT — with no entry ever permitted.

What stays the trader's job

AuraBot does not place trades and is not a broker. It provides context and one live decision state; you decide whether to act on it. Position size, order type, stop placement, whether the scenario fits your plan, and whether you take the trade at all remain yours. The system is built to make those decisions better informed, not to make them for you.