Gold Catalyst Evolution V6.11 — How Risk Is Defined Across Both Engines

Hello traders,

UPDATE NOTE — 8 October 2026

This article has been rewritten for Gold Catalyst Evolution V6.11. V6.11 does not use one universal risk model: its two independent engines have separate lots, protective levels, exits, magic numbers, and participation controls.

👉 Gold Catalyst Evolution V6.11

V6.11 protection architecture — current product operating illustration; not a performance result. Manual static lots and capital principles — current product operating illustration; not a performance result.

Engine A — selective directional engine

• Default fixed lot: 0.02
• Own positions, protection, and exit logic

Engine B — independent market-participation engine

• Default fixed lot: 0.04

Input distances must be interpreted with the broker’s symbol digits, point value, contract size, and execution rules. Verify the actual price and monetary exposure in MT5 rather than assuming identical dollar risk across brokers.

Fixed lots—not fixed percentage risk

The default lots do not scale automatically with account balance or Stop Loss distance. Therefore, the same lots represent more relative risk on a smaller balance and less relative risk on a larger one. Changing either lot creates a custom configuration that requires new testing.

Engine A and Engine B can both contribute to account exposure. Separate magic numbers help attribution, but the balance and equity are shared. Always evaluate combined drawdown and margin—not only one engine at a time.

Protective orders and their limits

After the broker accepts a position and its protective levels, the Stop Loss/Take Profit is normally held by the broker. This can preserve protection if the terminal later disconnects. However, protection must not be assumed before acceptance, and users should verify the levels are visible.

A Stop Loss defines intended risk but cannot guarantee the exact exit price or monetary loss. Gaps, slippage, spread expansion, invalid stops, rejected modifications, and broker execution can produce a different result.

What V6.11 does not use

V6.11 is not presented as martingale, grid, arbitrage, uncontrolled recovery, or loss-based lot multiplication. A later trade does not intentionally inherit a larger lot because an earlier trade lost. This reduces one form of compounding risk, but it does not make losses automatically recoverable or drawdown bounded.

Development reference—never a guarantee

The current V6.11 specification promises no fixed drawdown level. Evaluate balance drawdown and equity drawdown separately for the exact tested version, engine selection, fixed lots, broker and period. A development screenshot or an earlier version’s observation cannot establish a V6.11 drawdown ceiling or future outcome.

Hedging is recommended. Netting is supported, with same-symbol entries serialized. Use an M5 chart on a gold symbol containing XAU or GOLD.

👉 V6.11 operating setup
👉 Account size and fixed-lot configuration
👉 Losing trades, expectancy, and streak controls

Capital and manual fixed lots in V6.11

• USD 400 minimum suggested entry configuration: Engine A enabled at 0.01 lot; Engine B disabled.
• USD 1,000 dual-engine reference: Engine A at 0.02 and Engine B at 0.04; both engines enabled for this reference.
• At USD 1,000 and above, Engine A only, Engine B only or both engines may be selected according to the reviewed capital and risk profile. Engine B may be reduced or disabled for a more conservative profile.
• Lots are set manually and remain static. There is no automatic balance/equity scaling or profit-based compounding.
• For non-USD accounts, convert account equity to its USD-equivalent value before applying USD-based guidance.

These are operating references, not safety guarantees. Increased lots increase potential gains and losses; each selected engine/lot combination needs evaluation under the operating broker’s conditions.

V6.11 protection and operating defaults

• Engine A Defense Mode: an additional protective state after a configured sequence of full-stop losses; internal recovery handling is automatic.
• Protection state persistence: retains protection state across terminal restarts where applicable.
• Weekend Protection: uses the broker’s session timing to block new entries near the weekly close, close protected EA positions before the weekend and resume after the market reopens.
• Engine B loss controls: daily-loss and consecutive-loss monitoring with cooldown behavior.
• Margin and execution checks: available margin and broker volume requirements are checked before orders are sent.

For normal customer operation, adjust engine selection and manual lots according to the evaluated capital and risk profile. Keep strategy, protection, sealed-profile, filter and diagnostic parameters at the supplied defaults. These controls do not guarantee recovery, exact Stop Loss fills, a maximum drawdown or any trading result.

⚠️ Risk disclaimer: Trading leveraged products such as Forex and CFDs involves substantial risk. Protective orders reduce intended risk but cannot eliminate it. Backtests, demo monitoring, and past performance do not guarantee future results.