01
Starting point
An entry logic identifies recurring price patterns. Without context it can treat visually similar patterns as equally valuable.
System architecture
A trading system is more than its entry signal.
An entry is only the visible endpoint of a longer decision chain. Before that, the system must determine where the market is trading, which structure is present, whether a signal is robust and whether the technical environment permits clean execution.
GoldAutoTradePRO deliberately separates these tasks. No single indicator controls an order on its own. Signal, structure, quality, order logic and operations form five connected yet independently testable areas of responsibility.
This separation makes decisions easier to understand: a setup can be detected and later rejected because structure conflicts, quality is insufficient or the operating state is unresolved.
GoldAutoTradePROCONNECTED
SYSTEM ARCHITECTURE
SYSTEM ARCHITECTURE
01
Signal
Detects potential market situations and creates a candidate. No order exists yet.
Development path
From entry logic to a complete trading architecture.
The strategy was not improved by simply adding more signals. The decisive step was separating responsibilities and introducing explicit veto points.
02
First insight
Signal frequency is not a quality metric. Additional trades can damage performance when market phase and structure do not align.
03
Market structure
Relevant highs, lows, sweeps and reactions provide the spatial context in which a signal is assessed.
04
Quality and veto
Several checks can downgrade or fully block a candidate. Not trading is an active system decision.
05
Operating architecture
Order state, session boundaries, rollover and connectivity are treated as part of the strategy.
MGC futures
What the futures market means for an automated strategy.
MGC is not just another gold symbol. Contract specification, tick value, expiry, trading hours and liquidity migration determine how data is read and orders are executed.
Instrument specification
The Micro Gold future has defined tick sizes and tick values. Risk and order logic must be aligned precisely with this instrument.
MGC as a position unit
The smaller contract size enables finer sizing. It does not automatically reduce market risk; it changes the scale.
Central futures data
The strategy requires suitable MGC market data. CFD or spot-gold data is not equivalent to the traded futures contract.
Rollover as an operating state
When liquidity moves to the next contract, the active market must be changed and data continuity checked.
500 tick
Why the 500-tick chart structures the decision chain.
Tick-based candles organise the market by activity rather than equal time blocks. This changes not only the display, but also the density at which structure and signals emerge.
Signal rhythm
Candles form faster during high activity. The system receives a finer sequence of state changes in dynamic phases.
Structural consistency
Each candle is based on the same activity count. Quiet minutes are therefore not weighted as heavily as very active minutes merely because both span the same time.
Sensitivity testing
500 tick is an operating baseline, not a law of nature. Other tick rates must be tested separately so an apparent edge is not merely caused by a display setting.
Input → Processing → Output
Five modules. One connected decision flow.
The sequence shows how market information enters as a bundled impulse, is checked from module to module and only then becomes a clearly defined system state.
INPUTPROCESSINGOUTPUT
Relevant highs / lows
Sweep and V reaction
Market activity
Directional structure
Create candidate
Continue observation
Block setup
ACTIVE STAGEBundle input
CHECK
Market data is captured as a common input state.
HANDOVER
Structured input to the Signal Engine
01 / 07
Decision examples
Different situations. Different system decisions.
Each example begins with an incomplete market structure. The continuing path shows which information is added and why the system executes, observes or deliberately blocks.
Operating protection
Technology protects execution – it does not replace trading logic.
The futures sections explain which instrument and market data are processed. Operating protection answers a different question: may an already approved decision actually be executed under the current technical conditions?
Licensing and distribution
Protected delivery, unambiguous versions and controlled activation reduce inconsistent installations.
Feed and connectivity monitoring
Interruptions must be detected. After a disruption the system must not continue blindly from an unknown state.
Trading hours and rollover
Session boundaries, flatten time and the active contract are explicit operating parameters.
Audit and traceability
Signals, filter decisions and order states should be logged so deviations can be investigated.
Operating environment
A clearly defined operating environment.
The strategy is designed for NinjaTrader 8 on Windows with suitable MGC futures market data. The VPS page expands only on the technical runtime environment – not the trading logic.
NinjaTrader 8 and Windows
The strategy runs in a controlled NinjaTrader configuration. Platform version, add-on version and workspace must align.
MGC data access
Instrument, contract month and data feed must be correct. Historical and real-time data can differ in quality and coverage.
Stable operation
A local PC or VPS must provide reliable connectivity, power, time synchronisation and remote access.