Alerts

Alerts

Axiom BB Lite provides 18 alert conditions. This page documents every one of them, explains what they confirm, what they do not confirm, and where alert users are most likely to overtrust the signal.

How alerts work in this indicator

Every alert in Axiom BB Lite is gated on bar confirmation. An alert fires only after the current bar has closed, regardless of the On Bar Close setting. This means:

• Alerts never fire mid-bar. Even if a condition appears true while the bar is building, the alert waits for the bar to close before evaluating.

• This is a safety measure. It prevents false alerts caused by intrabar price spikes that reverse before the bar closes.

• The On Bar Close setting affects how the indicator's bands are computed (confirmed vs. building HTF values), but it does not change when alerts fire. Alerts always use confirmed bar data for their trigger moment.

All alert messages include TradingView's {{ticker}} and {{interval}} placeholders, so you can identify which chart and timeframe generated the alert. The messages do not include the slot's internal configuration (timeframe, MA type, etc.). If you run multiple instances of this indicator with different settings on the same chart, you will need to manage alert naming carefully to distinguish them.

Per-slot basis regime alerts

Each of the three slots has three alert conditions, for a total of 9 per-slot alerts.

BB 0X Is Above Basis

Fires on every confirmed bar where the slot is enabled and the close is at or above the slot's basis line.

This is a state alert, not a transition alert. It fires repeatedly — on every qualifying bar — as long as price remains at or above the basis. Use it when you want ongoing notification of the regime state, not a one-time crossing alert.

BB 0X Is Below Basis

Fires on every confirmed bar where the slot is enabled and the close is below the slot's basis line.

Same behavior as the above-basis alert, inverted. It fires on every qualifying bar, not just the first one.

BB 0X Basis Change

Fires on the confirmed bar where the above/below-basis state changes from the previous bar. If price was above the basis and is now below it, or vice versa, this alert fires once at the moment of the transition.

This is a transition alert. It fires once per regime flip, not continuously.

Blended basis regime alerts

Three alerts track the blended band's basis in the same way the per-slot alerts track individual slot bases.

Blended BB Is Above Basis

Fires on every confirmed bar where the blend is enabled and the close is at or above the blended basis.

Blended BB Is Below Basis

Fires on every confirmed bar where the blend is enabled and the close is below the blended basis.

Blended BB Basis Change

Fires on the confirmed bar where the blended basis regime changes from the previous bar.

Important context: The blended basis position depends on which slots are active and how the weights are set. If you change the blend configuration — even something as small as adjusting one slot's weight — the blended basis can shift enough to trigger a regime change that has nothing to do with price movement. The alert fires because the condition changed. It cannot tell you whether the change came from the market or from your settings panel. If you receive a blended basis change alert shortly after editing your configuration, check whether the flip was price-driven or settings-driven before acting on it.

All-slots alignment alerts

Two alerts track whether all active slots agree on price's position relative to their basis lines.

All BB Slots Above Basis

Fires on every confirmed bar where every enabled slot with a resolved basis has price at or above that basis line. If one active slot is below its basis, this alert does not fire.

All BB Slots Below Basis

Fires on every confirmed bar where every enabled slot with a resolved basis has price below that basis line. Same unanimity requirement.

What these alerts mean: Full-stack alignment tells you that price is on the same side of the basis across the active slots that currently have resolved basis values. It is a state report — it says "right now, the stack agrees." It does not say the agreement will hold, that the trend is strong, or that the next bar will continue in the same direction.

Important implementation detail: In the code, "active" means enabled plus a non-na basis value. If a slot is enabled but its basis did not resolve, that slot does not get counted into the unanimity check.

What to watch for: Full-stack alignment is relatively uncommon when your slots span meaningfully different timeframes. When it occurs, it means the shorter timeframes have caught up with the longer timeframes. When alignment breaks, it usually breaks at the fastest slot first. Watching which slot breaks alignment can tell you something about where the disagreement started.

Blended band cross alerts

Four alerts track when price crosses specific levels of the blended band.

Blended BB Crossed Above Upper Band

Fires on the confirmed bar where the close crosses above the blended upper band. This is a transition — price was at or below the blended upper on the previous bar and is now above it.

Blended BB Crossed Below Lower Band

Fires on the confirmed bar where the close crosses below the blended lower band. Price was at or above the blended lower and is now below it.

Blended BB Crossed Above Basis

Fires on the confirmed bar where the close crosses above the blended basis. A bullish basis cross.

Blended BB Crossed Below Basis

Fires on the confirmed bar where the close crosses below the blended basis. A bearish basis cross.

Alert summary table

What alerts do not confirm

Every alert tells you that a specific condition was true on the most recently closed bar. That is the full extent of what it confirms. Everything beyond that — whether the condition will persist, what it means for the next bar, how strong the move is — is interpretation you are adding. The alert has no opinion about any of it. What it does not confirm:

• That the condition will persist. The next bar can reverse the state immediately.

• That the condition was visible mid-bar. The alert fires only after bar close. The condition may or may not have been observable during the bar's building phase.

• That the underlying BB values are non-repainting. Alerts fire based on the indicator's current values at bar close. If On Bar Close is off, those values may differ from what was visible when the bar was building. The alert itself is bar-close gated, but the band values it references may still reflect building-bar computations.

• Anything about magnitude, speed, or conviction. A basis change alert fires whether the cross was by 0.01 or by 50 points. An alignment alert fires whether the alignment just formed or has been holding for 200 bars.

Where alert users tend to overtrust

These are the patterns that lead to the most misplaced confidence. Each one involves reading more into an alert than the alert actually contains.

"All Slots Above Basis" as a directional signal

Full-stack alignment is a fact about the current bar's state. It is not a momentum indicator, a trend strength measure, or a prediction. When you see all slots aligned above basis, it means price is above every configured basis right now.

The overtrust pattern works like this: the alert fires, the trader reads it as "all timeframes agree, the trend is confirmed," and they enter a position. But the alert does not distinguish between fresh alignment that just formed and stale alignment that has been holding for 200 bars. It does not know whether the fastest slot barely crossed its basis or crossed it decisively. It does not know whether the alignment is about to break because the fastest slot is already reversing within the current bar. The alert reports a state. The trader fills in a narrative. The narrative is where the risk lives.

Use alignment alerts as filters or state checks — "is the stack currently aligned?" — not as entry triggers. A filter that says "only consider longs when all slots are above basis" is using the alert within its means. An entry that says "go long because all slots are above basis" is asking the alert to do more than it can.

Blended band crosses as entry triggers

A cross above the blended upper band means price moved outside the composite envelope. The instinct is to read this as significant — price broke out of the bands. But what the alert cannot tell you is whether the blend's configuration makes that event meaningful or routine.

Consider: a blend configured with three tightly spaced timeframes (5m/6m/7m) and equal weights produces a narrow composite envelope. Price will cross the blended upper band frequently because the bands are tight. Each cross fires an alert. Each alert looks the same. A blend configured with widely spaced timeframes (5m/15m/60m) and heavy skew toward the longest timeframe produces a wider envelope that price crosses less often. A cross on this blend is a rarer event with more structural context behind it.

The alert itself has no awareness of your configuration. It reports every cross identically. The significance is entirely in the setup, and the setup is your responsibility to understand.

Basis change alerts as timing signals

The basis change fires once when the regime flips. It tells you the flip happened. It does not tell you whether the flip will hold past the next bar, how decisive the cross was, or whether the other slots are confirming.

The timing trap: a trader sets a basis-change alert on the fastest slot (5m) and uses it as a timing signal. The alert fires often because short-timeframe regimes flip frequently. Most of these flips are noise — the 15-minute and 60-minute slots have not moved. The trader acts on the 5-minute flip, and the market reverses back before the slower timeframes confirmed anything.

A basis-change alert on a single slot is most useful when paired with information about the other slots. If you use basis change alerts for timing, pair them with the alignment alerts or with a manual check of the other slots before acting. A regime flip that cascades from the fastest slot to the slowest has more structural meaning than one that stays confined to a single timeframe.