EVO-IILF institutional hybrid framework
Every trade has to earn its way to the market.
AutotradeX turns strategy signals into broker orders only after they clear an eight-stage validation pipeline, a seven-factor confluence score and your own risk limits. The stop is held at the broker, not in a browser tab.
- validation gates
- 8
- validation gates
- confluence factors
- 7
- confluence factors
- default target
- 3R
- default target
- 01SignatureHMAC-SHA256
- 02PayloadZod schema
- 03DuplicateSHA-256 hash
- 04Session09:30–15:30 IST
- 05Cooldown10 bars clear
- 06Daily tradesWithin cap
- 07Daily lossNot locked
- 08Open positionsSlot free
Target · 3R
- HMAC-SHA256 signed alerts◆
- Zod-validated payloads◆
- Seven-factor confluence◆
- Broker-held stop loss◆
- Native OCO on Binance Spot◆
- Durable execution ledger◆
- Daily-loss lock◆
- One-tap kill switch◆
- Paper · testnet · live separation◆
- Pine v5 strategy export◆
01 · The engine
Seven confirmations. One score.
Each closed candle is scored on seven independent confirmations. ADX strength, expanding volatility and your session window are hard gates on top, so a high score in a dead market still goes nowhere.
to qualify
- 01TrendClose and fast EMA 20 above EMA 200, confirmed by the 60-minute EMA 50. Mandatory for direction.
- 02VWAPPrice on the right side of the daily volume-weighted average price.
- 03DeltaSmoothed volume-delta proxy leaning with the trade.
- 04VolumeParticipation above 1.5× the 20-bar average.
- 05Liquidity sweepPrior 10-bar high or low taken, then rejected by the signal candle.
- 06Fair value gapImbalance left behind by a displacement candle larger than 0.8 ATR.
- 07Order blockOpposite candle reclaimed with displacement and high volume.
02 · Execution
From alert to order, without the guesswork.
- 01
Alert
A TradingView Pine alert or a native Binance scan produces a closed-candle setup.
- 02
Validate
Signature, schema, duplicate, session, cooldown, trade-cap, daily-loss and position checks run in order.
- 03
Size
Quantity comes from your risk percentage and the true stop distance, rechecked against lot and tick rules.
- 04
Protect
The entry is placed with protection held at the broker: native OCO on Binance, a broker stop on Angel One.
Connected where you trade.
Credentials are encrypted at rest and entered at runtime. Connecting a broker never starts trading on its own.
- India · NSE cash intradayAngel OneSmartAPI with broker-held stop, monitored target and a static IP egress.
- Crypto · testnet firstBinance SpotLong-only spot with native OCO protection and commission-aware accounting.
- SimulationPaperA separate switch and watchlist for forward testing that never touches a broker.
03 · Controls
You stay the circuit breaker.
Automation runs inside limits you set. Every limit is enforced on the server and survives a closed laptop.
Kill switch
Stop blocks new entries instantly. It needs no broker connection and leaves protection running.
Daily-loss lock
Hit your maximum daily loss and new entries lock until the next session.
Trade cap
A hard limit on entries per day, enforced on the server, not in the browser.
Cooldown
At least ten bars between setups, so one move cannot trigger a cascade of entries.
Session window
Entries only inside your trading hours, with a scheduled square-off before the broker cutoff.
Locked runs
Broker, symbol and timeframe stay locked while a run is live, across every tab and device.
Every intent, fill and fee goes on the record. Unknown outcomes are reconciled, never blindly retried.
A durable execution ledger feeds your journal, analytics, risk view and alerts, with paper, testnet and live results kept apart and every currency reported on its own.