1. EUR/USD M1 is the defined operating scope
The reference implementation is intentionally focused on EUR/USD on the one-minute timeframe. That keeps the intended symbol, timeframe, execution costs and historical test context clear. Running the EA on a different symbol or timeframe would be a different use case and should not be assumed to reproduce the published behavior.
2. The EA evaluates its coded entry conditions
When the configured trading window is active, the EA evaluates its internal EUR/USD rules and can place trades when those conditions are met. Automation makes execution consistent with the code; it does not mean a trade will occur every session and it does not remove losing trades.
3. Position size is calculated from the selected risk mode
The v1.07 tester configurations request 1.5% trade risk with a separate 1.00% hard planned-risk cap, uses a 10.0-pip protective stop and includes a 20-point sizing reserve for adverse execution. Prop-Safe references the original/fixed account balance for planned sizing. Compound references current balance, so planned size can rise or fall as the balance changes.
4. Account-level loss controls sit above individual trades
Prop-Safe includes an account-wide daily-loss guardrail. The published reference threshold is 0.80% of the original/reference balance, with floating P/L included in the accounting. Winning P/L does not create extra daily risk budget. The guardrail is intended to stop new trading when its configured threshold is reached; it cannot guarantee the exact realized loss during gaps, slippage or abnormal execution.
5. News and schedule controls reduce avoidable operating exposure
The production design checks relevant high-impact EUR/USD events before new entries, includes Friday-flat behavior, blocks weekend entries and supports MT5 push notifications. These are operational controls, not market-risk elimination. The published Strategy Tester runs had the live news filter disabled inside the tester, so those historical results should not be read as evidence of live news-filter performance.
6. Exits include a protective stop and normal strategy logic
The reference setup uses a defined protective stop and also includes normal time/strategy-based exit behavior. Requested stop prices are not guaranteed execution prices. Spread expansion, slippage, gaps, liquidity and broker conditions can change the actual fill.
7. The trader still controls the environment
A working deployment requires the correct MT5 terminal, broker EUR/USD symbol, Algo Trading permissions, required WebRequest access, a stable terminal or VPS and enough margin for the configured account. Broker costs and contract specifications should be checked before live use.
How to evaluate the workflow
Use the seven-day demo to verify installation and broker behavior, the risk-controls page to understand the reference limits, and the backtest page to review the dated historical evidence and its limitations. Treat installation success, execution quality and strategy robustness as three separate questions.