← Back to HomeRisk Controls

9 Risk Gates.
No Trade Skips Any.

Every trade signal generated by the AI engine must clear all nine risk validation gates before it reaches MetaTrader 5. Hard limits, not suggestions.

Execution Flow
AI Analysis
→
Decision Engine
→
Risk Manager
→
Trade Approval
→
MT5 Execution
→
Telegram Notification

The 9 Risk Gates

🎯
Confidence Validation
Signal must exceed the minimum confidence threshold. Low-confidence signals are automatically rejected.
📡
Spread Validation
Live spread must be within acceptable limits. High-spread conditions block execution to protect against slippage.
📉
Daily Loss Check
Cumulative daily loss is tracked continuously. When the daily limit is reached, trading halts for the rest of the day.
📊
Drawdown Check
Account drawdown from peak equity is monitored. A drawdown breach triggers an automatic trading pause.
💰
Margin Check
Available free margin is verified before each order. Insufficient margin blocks execution entirely.
🔄
Duplicate Signal Protection
The same signal cannot be executed twice in the same window. Prevents over-trading on repeated conditions.
📋
Max Open Trades
Total open trade count is compared against the configured maximum. New signals are rejected if the limit is reached.
🚨
Emergency Stop State
A manual or automatic emergency stop can be activated at any time. All execution is blocked while active.
⚙️
Account-Specific Risk Rules
Each managed account carries its own risk parameters. Rules are enforced independently per account.

Risk Philosophy

Capital preservation comes before profit. Every configuration decision in N1God AI is designed around this principle.

✓
Hard Limits Only
Risk parameters are enforced in code. There is no manual override that bypasses the risk engine.
✓
Per-Trade Risk Control
Every trade is sized to risk a fixed percentage of account balance, not a fixed lot size.
✓
Emergency Stop
A single command halts all trading instantly. No open positions can be opened while the stop is active.
✓
Full Audit Trail
Every decision — approved or rejected — is logged with timestamp, reason, and parameters.

See the Risk Engine in Action

Sign in to view live risk parameters, active limits, and emergency controls.

Sign InOpen Dashboard