Alerts

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

That matters with Axiom BB Lite because the indicator can watch several layers at once. Done well, alerts help you return to the chart when a condition matters. Done poorly, they turn a flexible context tool into a stream of commands you did not really verify.

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

What alert families are available

Slot alerts

Each slot has 3 alert conditions:

• BB 01 Is Above Basis, BB 02 Is Above Basis, BB 03 Is Above Basis
• BB 01 Is Below Basis, BB 02 Is Below Basis, BB 03 Is Below Basis
• BB 01 Basis Change, BB 02 Basis Change, BB 03 Basis Change

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

Blended-band alerts

The blended band exposes:

• Blended BB Is Above Basis
• Blended BB Is Below Basis
• Blended BB Basis Change
• 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 care about the summary structure rather than every slot detail.

Alignment alerts

The indicator also exposes:

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

Use these when full-stack agreement matters to your workflow more than the blended view alone.

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 people need to hear clearly:

• chart-bar-close alerts do not erase higher-timeframe trust risk
• if On Bar Close? is off, the stack can still be reading still-forming higher-timeframe bars

So the alert may arrive on a confirmed chart bar while still reflecting slot values that were built from unfinished higher-timeframe data.

State alerts versus change alerts

This distinction will save you frustration.

Alert type / What it tells you / Best use

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 persistent state.

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 stack is in confirmed mode or live-forming mode.
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
• the blend weights are still drifting around
• you are using live-forming mode but still reading it 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 in alert workflows when you want the message 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 stack is confirmed or live-forming.
• 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 or one Blended BB Basis Change alert on a confirmed stack.

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