Judas & Silver Bullet Models
The named model sequences as composed events — sweep, shift, window — with full lineage.
The named models are where this vocabulary stops being objects and becomes sentences, and this instrument renders the sentences with their grammar showing.
What it draws
Composite events under the fixed grammar — a qualifying pool swept, a structure shift within the declared window, an array touched — with the named models as configurations over it: the judas swing anchored to its declared open, the 2022-model sequence, and the silver bullet’s restriction to its three taught one-hour windows on the same clock authority the killzone instrument uses. Every flag carries lineage: the exact sweep, shift and array that composed it, bar by bar, each leg checkable against the instrument that detected it. A sequence you cannot decompose is a story; these decompose on click, which converts the taxonomy’s most narrative layer into its most auditable one.
Shared components, not copies
Each leg of every sequence is detected by this line’s own instruments — the pool registry, the sweep test, the structure engine, the imbalance family — under one configuration.
The alternative, private reimplementations inside a models tool, is how the same name comes to mean different events in different products, and it is the specific failure this line exists to end. What the shared grammar cannot do is make the sequences resolve as taught. The judas name assumes the opening push betrays; the silver bullet’s windows assume the hour matters beyond the clock’s ordinary seasonality — both are base-rate claims the calibration layer tests against its stated incumbents, the bare hour included, and reports as found. What ships here is the grammar made checkable, with the named models counted as the separate configurations they are. Whether the sentences come true is the measurement’s verdict to give, and no name — however confident — pre-empts it.
The object it looks for
The frozen definition, drawn. This is the geometry the detector is built to find — not a capture of the instrument running, and not a result. A drawing that implied otherwise would be the one thing this line exists to refuse.
Grammar showing. The composite is a sequence of three component events — a sweep, a shift, and an array touch — and the lineage beneath names the instrument that detected each one, in the order it fired. A sequence you cannot decompose is a story; this one decomposes.
Decomposing a sequence establishes which components fired, in what order, and inside which window. It does not establish that a completed sequence is followed by anything.
Judas & Silver Bullet Models: what the frozen definition states, in full.
| Element | What the definition states |
|---|---|
| Sequence grammar | Sweep, then shift, then array touch. |
| LineageEach component event names the instrument that detected it, so the composite is checkable against its parts rather than taken whole. | On. |
| Model windows | For silver bullet, the three taught one-hour windows. |
| Declared openWhich open the model measures from is named in advance, because an open chosen afterwards fits any morning. | election pending |
| Component windowsHow long each component has to arrive before the sequence lapses is a parameter, not a fact. | election pending |
| Not established | Whether a completed sequence is followed by anything. |
The definition in full, with the terms it uses, is at the glossary entry.
The parameters, in the open
Every threshold is a named parameter with its shipped state visible. Where a default reads election pending, the calibration run has not yet frozen it, and this page says so instead of inventing a number. Presets populate editable fields; they never lock them.
Judas & Silver Bullet Models: every threshold it exposes, and the state each one is in.
| Parameter | Shipped state | What it decides |
|---|---|---|
| Sequence grammar | sweep → shift → array touch | The composer's fixed order; each component is the line's own detector, not a private reimplementation. |
| Declared open | election pending | Midnight New York versus London open as the judas anchor — stated, because the choice changes every event. |
| Model windows | silver bullet: the three taught one-hour windows | The time restriction a named model imposes, where it imposes one, on the same clock authority as the killzone instrument. |
| Component windows | election pending | How many bars may separate sweep from shift, and shift from array touch, before the sequence is void. |
| Lineage display | on | Every flagged sequence lists its components — which pool, which shift, which array, which bars. |
The calibration certificate
Every instrument in this line ships with its report: the reaction and state statistics for its objects, computed on this estate's own recorded data under the campaign's measurement design, with the vintage's hash and date printed — and a refusal state when the vintage ages past its declared cadence. The report ships whatever it says.
This instrument's certificateNOT YET COMPUTED
The campaign's entry bar is the reason: no driver takes a live reading before it recovers a planted effect through the measurement harness, and the harness comes before every certificate. The drafting instrument is in build for the platforms above. Nothing is purchasable yet, here or anywhere.
What this instrument does not do
It makes no claim that its objects predict anything, and it ships no signals. It draws defined geometry under stated parameters; whether that geometry carries information is the measurement layer's question, answered against stated nulls and published either way. No performance figures appear on this page because none have been computed — and when they are, they arrive as the certificate above, not as marketing.
The research on the claim it draws
The objects drawn by the Judas & Silver Bullet Models are taught with a claim, and no research note on this site examines that claim.
Questions and answers
How does the indicator draw the ICT silver bullet?
As one configuration of a fixed grammar, the 2022-model sequence: a qualifying pool swept, a displaced structure shift within the declared window, then a return into the fair value gap that shift left, restricted to the three taught one-hour windows. Those windows run on the same New York clock authority as the Session & Killzone Clock, and every flagged sequence lists the exact sweep, shift and array that composed it.
Which open does the judas swing anchor to?
The one the Declared open parameter names, midnight New York or the London open, stated because the choice changes every event. Which of the two ships as the default is still undecided. The component windows, how many bars may separate the sweep from the shift and the shift from the array touch before a sequence is void, are an election of their own.
What is the win rate of the ICT silver bullet?
This indicator states none. The silver bullet's windows assume the hour matters beyond the clock's ordinary seasonality, a base-rate claim the calibration layer tests against its stated incumbents, the bare hour included, and reports as found. Each named model is counted as its own configuration.
Why does each flagged sequence list its components?
Because a sequence that cannot be decomposed is a story. Each leg is detected by this line's own instruments under one configuration, the pool registry, the sweep test, the structure engine and the imbalance family, and the flag lists which pool, which shift, which array and which bars. Private reimplementations inside a models tool are how one name comes to mean different events in different products.
Where this sits
This instrument's concepts are defined in the glossary: judas swing · ict 2022 model · liquidity sweep · market structure shift · ict kill zones · fair value gap. Its drivers sit in the claims ledger (W2.10, W2.11, W2.12, W2.14) with their verdicts rendered honestly until computed.
Also in this line: Fair Value Gap Indicator · Order Block Indicator · Liquidity Sweep Indicator · Market Structure Indicator · Displacement Indicator · Session & Killzone Clock · Liquidity Pools Indicator · Premium-Discount & OTE Indicator · Opening Gap Indicator · SMT Divergence Indicator · Candle Range Theory Indicator.
Standing policy
- No promise of profit, ever. Hadal makes no performance claims and carries no implied edge. Past measurements describe instrument behaviour — never future returns.
- You own risk management. Hadal cannot control it and does not insure it. Good tools do not fix bad discipline — and this site says so.
- Analytical tools, for discretionary use. Nothing here is investment advice or a recommendation to trade. Every decision, and every outcome, is yours.
The same statement stands in the footer of every page.Terms Privacy