Alerts

Alerts are here to reduce chart-watching, not to outsource judgment.

That matters with Axiom BB Pro because the indicator can monitor a lot of layers at once. Done well, alerts bring you back to the chart when a condition matters. Done poorly, they turn a flexible context tool into a stream of commands you never really verified.

Use alerts when you already understand the state. Do not use them to skip understanding the state.

If you are still unsure which slots matter, alerts are early. Build the stack first.

What alert families are available

Per-slot basis alerts

Each slot has 3 alert conditions:

• BB 0X Is Above Basis
• BB 0X Is Below Basis
• BB 0X Basis Change

Across BB 01 through BB 10, that gives you 30 slot-specific alerts.

Use these when one particular slot matters more than the whole stack.

Blended basis alerts

The blended band exposes:

• Blended BB Is Above Basis
• Blended BB Is Below Basis
• Blended BB Basis Change

Use these when you care about the summary regime more than one slot's local state.

Full-stack alignment alerts

The indicator also exposes:

• All BB Slots Above Basis
• All BB Slots Below Basis

Use these when full-stack agreement is part of your workflow and genuinely worth reviewing.

Blended cross alerts

The blended band also exposes:

• Blended BB Crossed Above Upper Band
• Blended BB Crossed Below Lower Band
• Blended BB Crossed Above Basis
• Blended BB Crossed Below Basis

Use these when you want the moment price crosses a blended boundary rather than a persistent regime state.

Important timing rule

All alert conditions are gated by the chart bar closing.

That means the alert engine waits for barstate.isconfirmed on the chart timeframe. This reduces intrabar noise, but it does not mean every slot inside the indicator is confirmed in the higher-timeframe sense.

That leads to the rule most readers need stated plainly:

• chart-bar-close alerts do not erase higher-timeframe trust risk
• if some slots have On Bar Close? off, those slots can still be using live-forming higher-timeframe values underneath the closed chart bar

So the alert can arrive on a confirmed chart bar while still reflecting a stack with mixed timing posture underneath it.

State alerts versus change alerts

This distinction will save you frustration.

If you only want the moment of change, start with Basis Change or a blended cross alert. Do not default to ongoing state alerts unless you truly need the state to persist.

What the alert surface does not include

The current source does not expose:

• per-slot cross-above-upper alerts
• per-slot cross-below-lower alerts
• slot-count threshold alerts beyond the hidden count plots

That matters because traders often assume those families exist once they see how broad the rest of the alert surface is. In this build, they do not.

A clean setup order

1. Decide which chart state you actually care about.
2. Verify that state visually on the chart first.
3. Verify whether the relevant slots are confirmed, live-forming, or mixed.
4. Create the alert only after the state makes sense without the alert.

If you reverse that order, you end up trusting the notification before you understand the condition.

Good fit for alerts, and poor fit

Alerts are a good fit when:

• the condition is rare enough that you do not want to monitor it constantly
• you can explain the condition in one sentence without looking at the alert name
• you already know what you will check when the alert fires

Alerts are a poor fit when:

• you are still experimenting with slot roles
• blend weights are still drifting around
• some slots are live-forming but you are still reading them like confirmed history
• you are hoping the alert will decide whether the setup is good enough to trade

When each alert type is usually useful

Hidden count plots

The script exposes hidden plots for:

• Active Above Basis Count
• Active Below Basis Count

These do not add visible chart clutter, but they can help with alert workflows when you want messages or downstream logic to carry stack context.

Treat them as support utilities, not as a substitute for reading the chart.

Verification checklist before you rely on alerts

• Confirm the relevant slot timeframes fit your chart timeframe.
• Confirm the relevant slots are enabled.
• Confirm whether the relevant slots are confirmed, live-forming, or mixed.
• Confirm whether a slot has zero blend weight and therefore does not shape the blended band.
• Confirm what you will verify on the chart after the alert fires.
• Confirm that the alert meaning still makes sense when you explain it out loud in one sentence.

A good first alert

If you are new to the indicator, start with one BB 03 Basis Change alert or one Blended BB Basis Change alert on a fully confirmed stack.

That is usually easier to verify than turning on slot, blend, and alignment alerts all at once.

It also makes the follow-up question simpler: "What changed, and do I agree with the chart's explanation of that change?"