OPEN-SOURCE SCRIPT
BK AK-Iron Dome
📡🛡️ BK AK–Iron Dome (Zenith Edition) 🛡️📡
🙏 All glory to G-d
Respect to AK — discipline, patience, and clean execution.
what this indicator is
Iron Dome is a reversal probability framework built around a single, interpretable oscillator called the Reversal Score (range -100 to +100). The goal is not to “predict” tops or bottoms. The goal is to identify when price is stretched, then confirm whether a turn is forming using multiple independent factors (momentum, volume behavior, VWAP location, divergences, and context filters).
This script is designed for traders who want:
a clear overextended / mean-reversion map
confirmation-based reversal triggers (not just “overbought/oversold”)
optional filters that reduce low-quality signals (time-of-day, higher timeframe alignment, rejection candles, volume confirmation)
What the Reversal Score measures (core logic)
The Reversal Score is a weighted composite that blends several components into one number:
Momentum + oscillator pressure
RSI and Money Flow Index (MFI) are used to measure directional pressure and exhaustion risk.
A momentum component (rate-of-change/acceleration behavior) is used to detect loss of thrust into extremes.
Anchored VWAP position
Iron Dome includes a multi-anchor VWAP engine that can be anchored to:
Session (daily reset)
Weekly (Monday anchor)
Monthly
Quarterly (auto-roll style anchor)
Custom date/time anchor
Or disabled (fallback VWMA)
The script then measures where price sits inside VWAP bands using a true deviation model (standard deviation of price minus VWAP), and converts that into a VWAP Position score (0–100). This prevents “band width illusions” that happen when volatility changes.
Adaptive thresholds (optional)
Default reversal zones are:
Peak zone around +90
Valley zone around -90
When Adaptive Thresholds are enabled, the script adjusts thresholds depending on whether volatility is unusually high or low (ATR regime). This helps reduce the “always in a zone” problem in high volatility and the “never reaches a zone” problem in quiet markets.
Confirmation layers (what makes this different)
Iron Dome’s signals are not based on a single trigger. They are filtered through optional confirmation systems you can enable/disable depending on your style.
A) Divergence engine (two independent systems)
Iron Dome can detect divergence in two different ways:
RSI divergence (price vs RSI or Momentum-RSI)
Score-line divergence (price vs the Reversal Score itself)
Both use pivot confirmation logic (left/right lookbacks). That means divergence markers appear only after the pivot is confirmed — this is intentional to reduce false early calls. Once printed, the divergence condition is based on confirmed pivots, not future bars.
You can also require divergence for trade signals (Require Divergence for Buy/Sell Signals) if you want fewer but stricter triggers.
B) Liquidity sweep detection (stop-hunt behavior)
Optional sweep detection flags candles that:
break a prior swing high/low by a meaningful wick (ATR-scaled)
then close back through the level (reclaim)
This is used as a context boost because sweep behavior often appears near reversals.
C) Exhaustion volume pattern
Optional exhaustion logic looks for:
a volume spike relative to average,
followed by volume decay,
while price stalls (ATR-scaled)
This attempts to detect “effort vs result” behavior: large activity but no follow-through.
D) Delta proxy (candle-structure pressure)
It’s a proxy derived from candle structure (how price closes relative to the candle range). It’s used as confirmation, not as a standalone signal.
E) MTF score alignment
You can compute a version of the score on a higher timeframe and require alignment before signals print. This is useful when you want reversals only in the direction of a bigger context (or only when HTF is also extreme).
F) Time-of-day filter (explicit timezone)
This module lets you avoid historically lower-quality windows (like lunch / transition periods) and optionally boost score weight during open/close drive windows. Time windows are interpreted in a user-selected timezone so there’s no ambiguity between exchange time and local time.
“Zenith Killer Gate” (final signal filter)
The Zenith Gate is an optional “final checkpoint” that can require:
higher timeframe trend/RSI context,
a rejection candle (wick/body ratio),
volume confirmation (surge or climax),
time filter pass,
and a one-shot arming mechanism that prevents repeated triggers until the score cools down.
If you want fewer, more selective signals, enable the Zenith Gate and use it as the final decision layer.
How signals are generated (simple and explicit)
A signal is not “Score touched a zone.”
A signal is “Score entered a zone and then turned.”
Zenith Sell: score was in peak zone, then momentum/score behavior indicates a turn down, and the selected confirmation gates pass.
Zenith Buy: score was in valley zone, then momentum/score behavior indicates a turn up, and the selected confirmation gates pass.
This reduces the common trap of selling “overbought” too early or buying “oversold” too early.
Risk tools: targets and stops (optional)
Iron Dome can project:
an ATR-based stop distance
and multiple R:R targets (T1/T2/T3)
These are planning guides, not guarantees. Targets auto-clean after a configurable number of bars to keep the chart clean.
Alerts
Alerts are included for:
Zenith Buy / Zenith Sell
extreme zone warnings
RSI divergence and Score divergence
liquidity sweeps
exhaustion patterns
high confluence states
For best consistency, use alerts on bar close and avoid firing multiple intrabar alerts unless your execution requires it.
Suggested usage (practical workflow)
Pick your anchor style
Intraday: Session anchor + RTH/ETH filter if you trade sessions
Swing: Weekly/Monthly anchor + MTF alignment
Use zones as “risk areas,” not entries
Peak/Valley zones mean “reversal risk rising,” not “enter now.”
Let confirmation decide
Divergence + sweep/exhaustion + rejection candle is the classic “stack.”
If you want strictness: enable Zenith Gate + require MTF alignment.
Execute with structure
Use your own market structure (levels, pivots, trendlines) for execution and stops. Iron Dome is the timing + confirmation layer, not a full trade plan by itself.
Limitations (important)
The delta component is a proxy, not true order-flow delta.
Divergences based on pivots confirm after a right-lookback delay (expected behavior).
The “quarterly auto-roll” anchor is an approximation intended for practical anchoring; it is not a full contract roll engine.
Suitable markets and timeframes
Works best on liquid markets where volume and volatility behavior are meaningful (futures, major forex pairs, large-cap equities, crypto majors).
Common use cases:
Intraday reversal filtering (5–30m)
Swing reversal context (1H–1D with MTF alignment)
Disclaimer
This tool is for charting/analysis only and does not constitute financial advice. Always use independent risk management and confirm with price action and market context.
📡🛡️ BK AK–Iron Dome (Zenith Edition) 🛡️📡
🙏 All glory to G-d
Respect to AK — discipline, patience, and clean execution.
what this indicator is
Iron Dome is a reversal probability framework built around a single, interpretable oscillator called the Reversal Score (range -100 to +100). The goal is not to “predict” tops or bottoms. The goal is to identify when price is stretched, then confirm whether a turn is forming using multiple independent factors (momentum, volume behavior, VWAP location, divergences, and context filters).
This script is designed for traders who want:
a clear overextended / mean-reversion map
confirmation-based reversal triggers (not just “overbought/oversold”)
optional filters that reduce low-quality signals (time-of-day, higher timeframe alignment, rejection candles, volume confirmation)
What the Reversal Score measures (core logic)
The Reversal Score is a weighted composite that blends several components into one number:
Momentum + oscillator pressure
RSI and Money Flow Index (MFI) are used to measure directional pressure and exhaustion risk.
A momentum component (rate-of-change/acceleration behavior) is used to detect loss of thrust into extremes.
Anchored VWAP position
Iron Dome includes a multi-anchor VWAP engine that can be anchored to:
Session (daily reset)
Weekly (Monday anchor)
Monthly
Quarterly (auto-roll style anchor)
Custom date/time anchor
Or disabled (fallback VWMA)
The script then measures where price sits inside VWAP bands using a true deviation model (standard deviation of price minus VWAP), and converts that into a VWAP Position score (0–100). This prevents “band width illusions” that happen when volatility changes.
Adaptive thresholds (optional)
Default reversal zones are:
Peak zone around +90
Valley zone around -90
When Adaptive Thresholds are enabled, the script adjusts thresholds depending on whether volatility is unusually high or low (ATR regime). This helps reduce the “always in a zone” problem in high volatility and the “never reaches a zone” problem in quiet markets.
Confirmation layers (what makes this different)
Iron Dome’s signals are not based on a single trigger. They are filtered through optional confirmation systems you can enable/disable depending on your style.
A) Divergence engine (two independent systems)
Iron Dome can detect divergence in two different ways:
RSI divergence (price vs RSI or Momentum-RSI)
Score-line divergence (price vs the Reversal Score itself)
Both use pivot confirmation logic (left/right lookbacks). That means divergence markers appear only after the pivot is confirmed — this is intentional to reduce false early calls. Once printed, the divergence condition is based on confirmed pivots, not future bars.
You can also require divergence for trade signals (Require Divergence for Buy/Sell Signals) if you want fewer but stricter triggers.
B) Liquidity sweep detection (stop-hunt behavior)
Optional sweep detection flags candles that:
break a prior swing high/low by a meaningful wick (ATR-scaled)
then close back through the level (reclaim)
This is used as a context boost because sweep behavior often appears near reversals.
C) Exhaustion volume pattern
Optional exhaustion logic looks for:
a volume spike relative to average,
followed by volume decay,
while price stalls (ATR-scaled)
This attempts to detect “effort vs result” behavior: large activity but no follow-through.
D) Delta proxy (candle-structure pressure)
It’s a proxy derived from candle structure (how price closes relative to the candle range). It’s used as confirmation, not as a standalone signal.
E) MTF score alignment
You can compute a version of the score on a higher timeframe and require alignment before signals print. This is useful when you want reversals only in the direction of a bigger context (or only when HTF is also extreme).
F) Time-of-day filter (explicit timezone)
This module lets you avoid historically lower-quality windows (like lunch / transition periods) and optionally boost score weight during open/close drive windows. Time windows are interpreted in a user-selected timezone so there’s no ambiguity between exchange time and local time.
“Zenith Killer Gate” (final signal filter)
The Zenith Gate is an optional “final checkpoint” that can require:
higher timeframe trend/RSI context,
a rejection candle (wick/body ratio),
volume confirmation (surge or climax),
time filter pass,
and a one-shot arming mechanism that prevents repeated triggers until the score cools down.
If you want fewer, more selective signals, enable the Zenith Gate and use it as the final decision layer.
How signals are generated (simple and explicit)
A signal is not “Score touched a zone.”
A signal is “Score entered a zone and then turned.”
Zenith Sell: score was in peak zone, then momentum/score behavior indicates a turn down, and the selected confirmation gates pass.
Zenith Buy: score was in valley zone, then momentum/score behavior indicates a turn up, and the selected confirmation gates pass.
This reduces the common trap of selling “overbought” too early or buying “oversold” too early.
Risk tools: targets and stops (optional)
Iron Dome can project:
an ATR-based stop distance
and multiple R:R targets (T1/T2/T3)
These are planning guides, not guarantees. Targets auto-clean after a configurable number of bars to keep the chart clean.
Alerts
Alerts are included for:
Zenith Buy / Zenith Sell
extreme zone warnings
RSI divergence and Score divergence
liquidity sweeps
exhaustion patterns
high confluence states
For best consistency, use alerts on bar close and avoid firing multiple intrabar alerts unless your execution requires it.
Suggested usage (practical workflow)
Pick your anchor style
Intraday: Session anchor + RTH/ETH filter if you trade sessions
Swing: Weekly/Monthly anchor + MTF alignment
Use zones as “risk areas,” not entries
Peak/Valley zones mean “reversal risk rising,” not “enter now.”
Let confirmation decide
Divergence + sweep/exhaustion + rejection candle is the classic “stack.”
If you want strictness: enable Zenith Gate + require MTF alignment.
Execute with structure
Use your own market structure (levels, pivots, trendlines) for execution and stops. Iron Dome is the timing + confirmation layer, not a full trade plan by itself.
Limitations (important)
The delta component is a proxy, not true order-flow delta.
Divergences based on pivots confirm after a right-lookback delay (expected behavior).
The “quarterly auto-roll” anchor is an approximation intended for practical anchoring; it is not a full contract roll engine.
Suitable markets and timeframes
Works best on liquid markets where volume and volatility behavior are meaningful (futures, major forex pairs, large-cap equities, crypto majors).
Common use cases:
Intraday reversal filtering (5–30m)
Swing reversal context (1H–1D with MTF alignment)
Disclaimer
This tool is for charting/analysis only and does not constitute financial advice. Always use independent risk management and confirm with price action and market context.
📡🛡️ BK AK–Iron Dome (Zenith Edition) 🛡️📡
Script open-source
Nello spirito di TradingView, l'autore di questo script lo ha reso open source, in modo che i trader possano esaminarne e verificarne la funzionalità. Complimenti all'autore! Sebbene sia possibile utilizzarlo gratuitamente, ricordiamo che la ripubblicazione del codice è soggetta al nostro Regolamento.
Declinazione di responsabilità
Le informazioni e le pubblicazioni non sono intese come, e non costituiscono, consulenza o raccomandazioni finanziarie, di investimento, di trading o di altro tipo fornite o approvate da TradingView. Per ulteriori informazioni, consultare i Termini di utilizzo.
Script open-source
Nello spirito di TradingView, l'autore di questo script lo ha reso open source, in modo che i trader possano esaminarne e verificarne la funzionalità. Complimenti all'autore! Sebbene sia possibile utilizzarlo gratuitamente, ricordiamo che la ripubblicazione del codice è soggetta al nostro Regolamento.
Declinazione di responsabilità
Le informazioni e le pubblicazioni non sono intese come, e non costituiscono, consulenza o raccomandazioni finanziarie, di investimento, di trading o di altro tipo fornite o approvate da TradingView. Per ulteriori informazioni, consultare i Termini di utilizzo.