MarketMaulers CISD

MarketMaulers CISD marks the level where delivery changed state: the open of the run that raided a level and then failed to hold it. It runs on the chart timeframe and on up to two higher timeframes at once, and it draws one line per setup rather than a lane of candles, because the level is the whole product.

Potential · Confirmed · Invalidated

FROM ZERO: WHAT A CISD IS
Read it as a three-candle story.

C1 is the candle whose high or low is worth taking. C2 is the candle that takes it and closes back inside. C3 is the candle that opens afterwards, where the reclaim either gets proven or does not.

The CISD LEVEL is not C1's extreme and it is not C2's close. It is the OPEN of the consecutive same-direction run that did the raiding. That run is a sequence of candles all closing the same way, and its open is where the move that swept began. When price closes back through that open, the run that swept is now the run that failed. Delivery has changed state. That is the entire concept, and everything below is about identifying that one price honestly.

THE TIMEFRAME NAMES A GRANULARITY, NOT A CANDLE
This is the part most implementations get wrong, and it is the difference between a tool that fires several times an hour and one that marks something.

A CISD timeframe names the resolution you are confirming on. Its C1 and C2 candles come from one fractal step ABOVE it:

1m from 15m · 3m from 30m · 5m from 1H · 15m from 4H · 1h from 1D · 4h from 1W · 1D from 1M

So a 5m CISD is a 1H C1 and C2, confirmed on 5m closes. Hunting "the current 5m candle sweeps the previous 5m candle" is a different and much noisier thing that happens several times an hour and means little.

Two consequences follow, and both are visible.
• A CISD only draws when your chart timeframe is at or BELOW its own granularity. From a 15m chart a 5m CISD stays hidden, because the chart cannot resolve the closes that confirm it.
• A slot confirms at ITS OWN granularity. On a 5m chart the 15m slot waits for a 15m close, not a 5m one. Set a slot to CHART and the chart timeframe becomes the granularity, with its C2 still pairing one step up.

THE TWO-SIDED SWEEP RULE
A candle that takes BOTH sides of the prior candle is indecisive. It swept the highs and the lows, so there is no side it committed to and no direction to deliver in. No C2, no setup, either way. This gates everything and it is on by default.

MAULER MODE is the single exception and it is off by default. If that two-sided candle CLOSED beyond one of C1's extremes then it was decisive after all, and the setup stands. It loosens the strictest gate in the model, so it is worth turning on deliberately rather than leaving on.

WHERE THE LEVEL COMES FROM, AND WHY IT MOVES
The anchor is the open of the first candle of the current same-direction run. Only an opposite-close candle resets it. Wicks, extremes and dojis are transparent to it, and a run can span a candle boundary, because delivery often starts inside the previous candle.

Two rules keep that anchor honest.
• A RATCHET. Any candle opening beyond the current anchor drags the anchor to its own open. A rally pulls a dead anchor up with it, so a shallow wick past the extreme can never capture a stale run from hours ago. The anchor always sits at the origin of the CURRENT move.
• RE-ANCHORING TO THE FINAL SWEEP. When price sweeps, pulls back, then sweeps again further, the level moves to that last leg. The anchor is structural, a run open, so a bare noise wick past the extreme re-captures the same value. Only a genuine pullback and resweep shifts the mark.

WHAT POTENTIAL MEANS, AND THE ONE CASE THAT SURPRISES PEOPLE
Potential means one thing only: price has not closed through the level yet. It is not a statement about which candle the close belonged to.

So when the C2's own sealing close is already through the level, the CISD is CONFIRMED at that seal and draws that way immediately. There is no waiting for a later candle to say what has already happened.

That test runs at the seal and never in the middle of C2, because the level re-anchors every time price sweeps a new extreme inside the candle. A bar confirming against the level as it stood an hour ago would be confirming against a level that no longer exists.

INVALIDATION
A hunt dies when price takes the C2's own extreme before the level is reclaimed. That is a raw trade through it, not a close, because a trade is a trade at any resolution and the setup does not survive the manipulation extreme being taken back.

Failed levels are removed by default, which keeps every line on the chart a setup that is still live or one that actually worked. Turn on Keep failed and they stay as dotted, faded history with an invalidation tag, which is the honest picture when you are reviewing rather than trading.

WHY IT DOES NOT REPAINT
There is no security call anywhere in this script. The engine accumulates its own higher-timeframe candles from the bars it runs on rather than requesting them, so there is no lookahead idiom to get wrong and no repaint surface at all.

Confirmation reads the previous, always-complete bar, and only on a bar where the slot's own timeframe has rolled, which is what makes a 15m slot confirm on 15m closes rather than on whatever the chart happens to be. Every state change is judged on closed data.

THE TABLE
Three rows, one per slot, bull state and bear state. It reports what happened LAST rather than what has ever happened, so a side that confirmed and was later invalidated reads as invalidated. A readout that cannot go backwards is not a readout.

Deliberately independent of what draws. Most people run one slot on the chart and want the state of the other two without adding lines to the price pane.

ALERTS
CISD armed (potential) · CISD confirmed · CISD invalidated

Messages carry the slot timeframe, the direction, the event and the level price, so what arrives is a level you can act on rather than a notification that something happened somewhere. Create one alert on this indicator with the condition set to Any alert() function call and it carries every enabled event for every slot at once.

An optional killzone filter quiets alerts outside three editable windows. It touches alerts only. Outside your windows the chart is identical: setups still arm, confirm, draw and invalidate on exactly the same rules, you do not get pinged for them.

MADE TO FIT YOUR CHART
Three slots each with their own bull and bear colour. Potential and confirmed lines have separate style and width. Labels on or off with three text sizes. Three right-extension modes, including freezing a confirmed level at the bar it confirmed, which is the honest history: the level did its job there. Keep failed on or off, with a budget for how many finished levels stay per side. Table position, text size, and a toggle per section.

The kept-level budget goes to 250 a side, and the tooltip is blunt about what that means. TradingView caps a script at 500 lines and 500 labels total. Past roughly 80 a side with more than one slot on, the platform ceiling decides what you see rather than this number does. It is a budget, not a promise.

HOW TRADERS ACTUALLY USE IT
Start with one slot and leave the other two off. The default pair, 5m and 15m, is two different fractals on one chart, and running both before you have read either one on its own is how a clean idea turns into noise.

Leave Draw potential off at first. With it off, every line on your chart is a CISD that actually confirmed. Turn it on when you want to see the setups the tool was watching that never paid, which is a different and slower kind of study.

The invalidation alert is the underrated one. Knowing a level died is a stand-down, and stand-downs are cheaper than entries.

WHAT THIS TOOL IS NOT
It marks a level and reports what happened to it. It does not project targets, it does not size a position, it does not stack or merge zones, and it does not tell you the setup was good. Those are layers on top of a CISD rather than part of one, and this file marks the CISD.

Works on any market and any timeframe.

Display only. This marks a level and reports what happened to it, it does not fire buy/sell signals and it does not forecast. Educational tool, not financial advice.

Published open-source. The fractal pair table, the two-sided sweep gate, the delivery-run anchor and its ratchet, the re-anchor-to-final-sweep capture, the seal confirm, the per-slot granularity gate and the alert transport are all readable in the source. Everything above explains what it marks and how it decides what to mark; the code is there so you can check that the description is accurate rather than take it on faith. Read it, fork it, argue with the constants.