GOLD FUTURES INTELLIGENCE

Gold Futures Intelligence

AuraBot maintains one live, reconciled market state for Gold futures (GC and MGC) through the New York session: where gold sits relative to liquidity and session levels, which side of the auction is in control, and whether execution is currently permitted. One message, updated when evidence changes.

Gold trades around liquidity, but not the way NQ does

Gold respects the same categories of level as any liquid futures contract: the overnight high and low, the prior-day high, low and close, and the highs and lows of each session. Where it differs is in how it behaves once it gets there. NQ tends to sweep a level and resolve quickly. Gold often sweeps a level, sits on the other side of it, and makes you wait.

That waiting is the trap. A trader conditioned on NQ sees gold push through the overnight high, assumes the sweep is complete, and fades it. Gold grinds higher for another hour, accepts above the level, and the fade is stopped out before any rejection arrives. The problem is not the level. It is treating a touch as a verdict.

Why gold sweeps are slower to resolve

Two session mechanics matter most.

The London and New York overlap

Gold is already active during London, so by the time New York opens a directional move is frequently in progress. The period around 9:30 ET often extends or reverses what London started rather than beginning fresh. Location reads that ignore the London range miss the levels gold is actually reacting to.

Slower acceptance

When gold moves through a level, acceptance takes longer to confirm than on NQ. Price can hold beyond a level for a stretch without displacement either way. During that stretch the honest read is "not yet."

How the engines read gold

Anchor Rails — Location

Maps the London range, the overnight high and low, prior-day levels and session extremes, and tracks sweeps and destinations. On gold, Rails is usually telling you which of several stacked levels price is actually working against.

SKELETON — Direction

Reads structure and displacement to decide whether gold has accepted beyond a level or rejected it. SKELETON keeps the state from advancing on a hold that has not yet become acceptance, or on a pullback that has not shown displacement.

Black Book — Execution

Evaluates whether current conditions permit an entry. A level might be swept and rejected on the New York timeframe while the larger London move still argues against fading it. Black Book holds execution permission until the cues line up.

Doctrine

Knowing the destination is not the same as knowing the entry. Gold reaching the overnight high or sweeping the prior-day low is a location event. Aura does not change execution permission on location alone; it waits for the auction to show acceptance or rejection and displacement, and the trader remains responsible for execution.

A gold session, read through the state

  1. Before the New York open. Rails has the London high and low and the overnight extremes marked. The state is WAIT. #daily-market-brief has already set the morning context for gold and NQ.
  2. Gold pushes through the overnight high after 9:30 ET. Rails registers the sweep. The state moves to WATCH. SKELETON is now evaluating: is price displacing back below the level, or holding and building above it?
  3. Price holds above for a stretch without displacement. The state stays in WATCH. This is the window where an impatient fade would be entered. The message says the evidence is not in, and that is the useful information.
  4. Displacement appears. If it is back into the range with structure breaking, SKELETON reads rejection, Black Book evaluates execution context, and the state can move to ARMED and ACTIVE. If displacement continues higher, the fade scenario is INVALIDATED and the state reads acceptance, with the overnight high now a level behind price rather than ahead of it.

The #gold-intelligence message

Gold has its own persistent live message in Discord, separate from NQ, because the two instruments are rarely in the same state at once. The message is edited in place and carries the current state, the levels Rails has in play, the direction read from SKELETON, and whether Black Book permits execution. Notifications go out only for meaningful decision changes or execution-critical events. A long stretch of WATCH produces no pings.

Every session is retained in persistent storage. Reviewing how long acceptance took to confirm across many sessions is how a trader recalibrates the patience gold demands.

Limits, stated plainly

  • AuraBot does not place trades and is not a broker.
  • It does not predict where gold will go. Hologram Candle draws a structural scenario forward; that is projection, not prediction.
  • It does not alert on every touch of a level. On a slow-resolving instrument that kind of alerting is harmful.
  • Risk, sizing and funded-account rules stay with the trader. AuraBot is not affiliated with TradingView, Topstep or any funded-account provider.

Questions

Is MGC read the same way as GC?

Yes. MGC is the micro contract on the same market, so the location, direction and execution reads are identical. Contract size is the trader's choice.

Does the gold state consider the London session?

Rails tracks session highs and lows, and for gold the London range is part of the location picture at the New York open. The state itself is built for the New York session, but it is not blind to what happened before it.

Why did the state stay in WATCH while gold kept moving?

Because movement is not the same as evidence. Gold can hold beyond a level for a long time without displacement or a structural break. Until SKELETON reads acceptance or rejection, the scenario remains open and execution permission is withheld.