GOLD TRADING SYSTEM

Gold Trading System

A gold trading system has to solve a problem NQ systems mostly do not: gold moves through levels and then makes you wait. AuraBot's engines and live state are built to hold execution permission until gold shows acceptance or rejection, so the system's core discipline is patience, not speed.

The mistake most gold systems are built to make

Gold futures (GC and MGC) attract level traders because gold respects session levels: the overnight high and low, the London range, the prior-day high, low and close. The trouble is what "respects" means. On gold, a reaction is often a slow hold beyond the level rather than a sharp rejection, and a system tuned to fire on the touch sells into a move that has not finished.

So the design question for a gold system is not "how fast can I get in at the level" but "how do I know when the auction has decided."

Four components, in order

The system is Direction → Location → Execution → one live decision state, with the trader's rules wrapped around it. Each component is owned by one engine.

SKELETON — Direction

Reads structure, displacement and acceptance versus rejection to state which side of the gold auction is in control. On gold this engine spends a lot of time saying "not yet."

Anchor Rails — Location

Maps liquidity, session highs and lows, prior-day levels, sweeps and destinations. For gold, Rails tracks London levels alongside New York ones, because the move often started before 9:30 ET.

Black Book — Execution

Evaluates execution context and decides whether conditions permit an entry. This is the engine that stands between a rejected level and a premature fade.

The Aura backend reconciles the three into one state, WAIT → WATCH → ARMED → ACTIVE → MANAGING → COMPLETE / INVALIDATED, published as a single persistent message in #gold-intelligence on Discord.

Patience on acceptance

Consider gold sweeping the prior-day high at 10:15 ET. Three outcomes are possible, and only one is a fade.

  1. Rejection with displacement. Price pushes through, fails, and displaces back below the level with structure breaking down. SKELETON reads rejection. Black Book evaluates whether execution is permitted. The state can move to ARMED.
  2. Hold without resolution. Price sits above the level, neither displacing higher nor falling back. This can last a long time on gold. The state stays in WATCH and no entry is permitted.
  3. Acceptance. Price builds above the level and displaces higher. The fade scenario is INVALIDATED. The prior-day high is now support behind price, and Rails is tracking the next destination above.

A trader who fades in outcome two is not wrong about the level. They are early about the evidence.

Doctrine

Knowing the destination is not the same as knowing the entry. Gold reaching a level is location. The entry needs auction evidence: acceptance or rejection, displacement, structure. Aura changes execution permission only when that evidence changes, and the trader remains responsible for execution.

Do not fade strong gold momentum

When gold is trending hard, especially when a London move carries through the New York open, each level it passes looks like a place to fade. The system handles this by keeping direction ahead of location. If SKELETON reads the auction as accepting higher, a sweep of a level above does not start a short scenario. Rails marks the sweep, the state may move to WATCH, but Black Book will not permit execution against a direction read that has not changed.

The Hologram Candle projection helps here by drawing a structural scenario path forward from live structure, session and volatility inputs. Projection, not prediction, but it makes "where would this go if acceptance continues" visible, a useful counterweight to the urge to call a top.

Session timing for gold

  • London into New York. Gold is active before New York. The context in #daily-market-brief and the London range on Rails matter more for gold than for NQ.
  • 8:20 to 9:30 ET. The futures open and the run into the equity open frequently extend or reverse the London move. This is where many gold sweeps of the overnight high or low occur.
  • 9:30 to roughly 11:00 ET. Where acceptance or rejection at those swept levels usually resolves, and where the state most often moves from WATCH to ARMED or INVALIDATED.
  • After the London close. Participation thins. Session filters in the TradingView tools exist for this reason, and the state spends more time in WAIT.

What the trader owns

Risk per trade, daily limits, contract size (GC versus MGC), and the constraints of any funded account are the trader's. AuraBot does not place trades, is not a broker, does not predict prices, and is not affiliated with TradingView, Topstep or any funded-account provider. The live state can read ARMED while your evaluation rules say stand down, and the rules win. Every session is retained in persistent storage, so reviewing how you handled the patience problem is part of the system.

Questions

How long should I wait for gold to confirm acceptance or rejection?

There is no fixed clock. The state advances when SKELETON reads displacement and a structural response, not after a number of minutes. If that takes an hour, the state stays in WATCH for an hour.

Is it ever right to fade gold at a level?

Yes, when the auction shows rejection with displacement and Black Book permits execution. The system is not against fading; it is against fading on location alone.

Do I need to watch London to trade gold in New York?

You do not need to trade it, but you need to know where its range is. Rails tracks session levels and the daily brief carries the morning context, so the London picture is in front of you at the open.