Alerts

Alerts are useful here because this indicator organizes context. They are not useful when they get treated like orders.

This page shows what alert types exist, what each one is actually saying, and what to verify before you lean on any of them.

Why this matters: alerts feel clean by design. That can lower workload, but it can also let a trader outsource too much judgment too early. The goal of this page is to keep alerts in the role of review prompts, not command signals.

The first alert truth to keep in mind

All alerts in this script are evaluated on chart bar close.

That does not mean all inputs are confirmed in the higher-timeframe sense. It means the alert conditions themselves are not firing intrabar on the chart. In live-forming timing mode, a higher-timeframe slot can still be using a requested bar that is not settled yet when the chart bar closes.

That distinction matters:

• chart-bar-close gating tells you when alerts are checked
• On Bar Close? tells you whether the higher-timeframe slot values are confirmed or still forming

If you blur those two ideas together, the alert can sound more settled than the stack actually is.

Alert families

The script exposes four alert families:

• slot state alerts
• blended state alerts
• blended event alerts
• alignment alerts

Open the TradingView alert picker once before you rely on any workflow. The names below should be there exactly as written.

1. Slot state alerts

These alerts tell you what one slot is doing relative to its own internal Slow side.

State alerts stay true as long as the state stays true. Regime flips are event-style alerts.

Verification habit:

1. Trigger one slot state alert in replay or on a quiet chart.
2. Confirm you can point to the slot line and explain why the condition is true before you rely on it.

2. Blended state alerts

These alerts track the current weighted summary state.

Use these when the slot design already makes sense. Do not use them as a substitute for understanding which slots are shaping the summary.

Verification habit:

1. Change one slot weight and see whether your reading of the blended state still matches what the pane is actually doing.

3. Blended event alerts

These alerts trigger on specific blended events, not on a persistent state.

These are useful because they are precise. They are risky when precision gets mistaken for completeness.

Verification habit:

1. When an event alert fires, look for the slot or blended context around it.
2. Do not let the event itself become the whole workflow.

4. Alignment alerts

These alerts ignore blend weight and ask whether the enabled slots agree.

These alerts are often the cleanest answer to "Do the enabled slots agree?" They are not the same as "Does the blend look strong?"

Verification habit:

1. If alignment fires while the blend looks muted, or the reverse, stop and check weights before assuming one side is wrong.

Hidden plots and zero-weight slots

Two alert behaviors surprise people regularly:

• hiding a slot plot does not remove slot alerts
• setting Blended Weight: to 0 does not remove slot alerts or alignment alerts

Why: those actions change visibility or blend participation. They do not erase the slot from logic unless you disable it.

A sensible first alert setup

If you are new to the indicator, start with only one or two alert types:

1. one slot regime flip on the timeframe you trust most
2. one blended regime flip or one alignment alert

That gives you a manageable feedback loop without pretending the script owes you a full execution plan.

Quick verification routine

Before relying on an alert, verify it in this order:

1. confirm whether the stack is in confirmed or live-forming mode
2. confirm which slots are enabled
3. confirm which slots have non-zero blend weight
4. trigger the alert condition once in replay or on a quiet chart
5. compare what the alert says to what the pane actually shows

If the alert wording makes more sense than the chart itself, you are leaning on the alert too early.

When an alert is helping versus hiding

An alert is helping when it brings you back to a chart state you can still explain.

An alert is hiding when:

• you cannot name which slots created the condition
• you do not know whether the stack is confirmed or still forming
• you are using overbought or oversold as a shortcut around context
• you are reading mixed-symbol agreement as proof

Go back to Visuals and Logic or MTF and Repainting if any of those are still in play.