Alerts

Alerts are useful here when they bring you back to a chart state you already understand. They become risky when they replace that understanding.

This indicator exposes several alert families because it answers several different questions:

• what one slot is doing
• what the weighted blend is doing
• whether a change event just happened
• whether every active slot agrees

Treat those as different tools, not one generic alert idea.

Before you set the first alert

Answer these three questions first:

• Am I monitoring one slot, the weighted summary, or full-stack agreement?
• Do I care about a condition that is true now, or a change that just happened?
• Are any of the slots I care about still live-forming even though the chart bar will close before the alert checks?

If those answers are clear, the alert setup usually becomes straightforward. If they are not, the alert tends to create urgency faster than understanding.

First truth: all implemented alerts are chart-bar-close gated

Every alert condition in this script is checked on chart bar close.

That means:

• alerts do not fire tick by tick inside the bar
• a still-forming higher-timeframe slot can still be part of an alert, because the slot itself may be live-forming even though the chart bar has just closed
• chart-bar-close alerting is not the same thing as confirmed higher-timeframe slot behavior

That last line matters most. If a slot uses On Bar Close? = off, the slot can still be following a higher-timeframe bar that has not finished even though the alert is firing on a closed chart bar.

The four alert families

1. Per-slot state alerts

These alerts tell you when one slot is currently bullish or bearish.

Examples:

• MACD 01 Is Bullish
• MACD 01 Is Bearish
• MACD 05 Is Bullish
• MACD 10 Is Bearish

What they mean:

• bullish = that slot's Fast side is above its Slow side
• bearish = that slot's Fast side is below its Slow side

What they are good for:

• watching one specific slot role
• tracking a diagnostic slot that is outside the blend
• separating local slot behavior from the broader summary

What not to assume:

• these are continuing state conditions, not one-shot flip alerts
• hiding the slot plot does not disable the alert if the slot stays enabled

2. Blended state alerts

These alerts tell you the current state of the blended summary.

Available alerts:

• Blended MACD Is Bullish
• Blended MACD Is Bearish

What they are good for:

• monitoring the current weighted summary
• filtering when you care about persistent blended state rather than a single change event

What not to assume:

• the blend is only listening to active slots with non-zero weight and valid values
• a bullish blend does not guarantee that every active slot agrees

3. Blended event alerts

These alerts focus on change rather than ongoing state.

Available alerts:

• Blended MACD Regime Flip
• Blended MACD Crossed Above Zero
• Blended MACD Crossed Below Zero
• Blended MACD Overbought
• Blended MACD Oversold
• Blended MACD Histogram Crossed Above Zero
• Blended MACD Histogram Crossed Below Zero

What they are good for:

• being notified when the summary changes character
• watching transitions instead of steady-state conditions
• using the histogram or zero line as a timing checkpoint inside a broader workflow

What not to assume:

• a regime flip is not the same thing as alignment
• a threshold cross is not automatic trade permission
• one event alert is not proof that the whole stack has become cleaner or stronger

4. Alignment alerts

These alerts tell you when every enabled slot with valid values agrees.

Available alerts:

• All MACD Slots Bullish
• All MACD Slots Bearish

What they are good for:

• checking stack unanimity
• spotting moments when the full active ladder is pointing the same way

What not to assume:

• alignment is not a weighted vote
• a zero-weight slot can still count toward alignment
• alignment can be true even when the blend is not the most useful read on the chart

A simple way to choose the right alert family

If you do not know which question you are asking, do not set the alert yet.

Two distinctions that prevent a lot of false confidence

State alerts versus event alerts

State alerts tell you what is true now. Event alerts tell you what just changed.

Those are not interchangeable.

If you need the chart only when something new happens, start with event alerts. If you need to filter for an existing condition, state alerts are the better fit.

Blend alerts versus alignment alerts

Blend alerts tell you what the weighted summary is doing. Alignment alerts tell you whether every active slot agrees.

One can be true without the other:

• a heavy slot can keep the blend bullish while a lighter slot has already turned down
• a zero-weight slot can still prevent alignment even though it does not touch the blend

What the script comments do not match

The script's comment block mentions per-slot regime-flip alerts. The implemented alert list does not provide per-slot regime-flip alerts.

For this manual, the alert picker is the source of truth.

If you are hunting for per-slot flip alerts and do not see them, that is not user error. They are not part of the implemented alert surface in the current documented build.

A safer alert workflow

If you are new to the indicator, this order keeps alerts from outrunning understanding:

1. start with the same-symbol baseline stack
2. verify slot state versus blend state on the chart first
3. choose one alert family that matches one question
4. test it in replay or during live observation
5. only then add more alert families

That process sounds plain because it is. It also prevents a lot of "the alert fired, but I no longer know what it means."

Quick verification routine

1. Open the alert picker and confirm all four alert families are present.
2. Hide one active slot and confirm its slot alerts are still available.
3. Set that slot's Blended Weight: to 0 and confirm the slot alerts still make sense while the blend responds differently.
4. Compare Blended MACD Is Bullish with All MACD Slots Bullish during a moment of disagreement.
5. Turn On Bar Close? off on one active higher-timeframe slot and watch how that changes your interpretation of an otherwise normal alert.

By the end of that routine, you should know whether the alert is pointing at a local slot, a weighted summary, or full-stack agreement.

Visual placeholder: Alert-family matrix showing slot-state alerts, blended-state alerts, blended-event alerts, and alignment alerts, with one note explaining that chart-bar-close gating does not make a live-forming slot confirmed.