The Setups menu, explained

By the XAUUSDLiveChart Research Desk · 5 min read

The Setups menu holds detection engines: each one watches for a specific textbook sequence, session traps, failed breakouts, retracement confluences, reversal structures, and when its conditions complete, draws the setup with its zone, invalidation and targets. The word detection is doing honest work in that sentence: these tools find and label conditions; none of them knows the future, and their own backtests keep them humble.

What an engine gives you

Each detected setup carries a state machine, waiting, in-zone, confirmed, invalidated, plus concrete levels: where the idea activates, where it dies, where its targets sit. That converts a vague pattern into an auditable object: you can see what it saw, when it saw it, and what would prove it wrong. Nothing repaints; a state printed on a closed candle stays printed.

The scoring honesty

Setups show confluence scores that count how many independent conditions aligned, never probability of winning. Our own replay testing across years of data found that mechanical scores do not translate into win rates, and the interface says so rather than dressing counts up as confidence. A backtest-validated reward-to-risk filter tags which setups even clear the basic math, detailed in the risk-reward notes.

Context still governs

Every setup engine reads the bigger picture: higher-timeframe conflicts get flagged on the card, imminent high-impact news arms an entry-blocked warning, and setups fighting fresh weekly zones say so. A confirmed pattern inside hostile context is a labelled hazard, not an invitation.

The intended workflow

Enable the one or two engines matching your playbook, let alerts summon you, then judge the flagged setup with your own structure reading. The engines exist to make sure you never miss your pattern and never misremember what it looked like, which is preparation, not prophecy.

FAQ

← All guides