Alerts

Axiom BB CTX exposes twenty-four alert conditions. None of them is a buy or sell signal. All of them are descriptions of computed conditions that held when a chart bar closed.

This page documents what each alert is, when it fires, what it is honest about, and the things readers are most often tempted to over-read into them.

The complete list

Every alert here is gated by the close of the chart bar. None of them fire intrabar.

What "uptrend" and "downtrend" actually mean for these alerts

The basis trend is a fixed-lookback comparison, defined per slot.

• A slot's basis is uptrend when its current basis value is greater than or equal to the basis value Basis Trend Length bars ago.

• A slot's basis is downtrend when it is lower than that comparison value.

Basis Trend Length is per slot. The default is 3. A trader who left the default has, in practice, a "basis at least as high as three bars ago" definition for each slot. That is a meaningful piece of information; it is not a regime call.

If you change Basis Trend Length on a slot, the meaning of every alert that depends on that slot changes with it. A 3-bar trend length and a 30-bar trend length produce very different alert cadences from the same price action. When you wire an alert, write the trend-length value into the alert's name or message so future-you knows which definition the alert is enforcing.

Bar-close gating, in detail

Every alert in the list is fired through TradingView's alertcondition, with the underlying expression gated by the close of the chart bar.

That phrasing matters. The alert fires when the chart bar closes and the condition was true on that closed chart bar. It does not wait for the slot's higher-timeframe bar to close. With a 60-minute slot on a 1-minute chart, a BB 03 Basis Is Uptrend alert can fire fifty-nine times during a single 60-minute window — once on each chart-bar close where the condition held — long before that 60-minute bar itself has closed.

The implication: the chart-bar gating tells you "this condition was true at the close of this chart bar." It does not tell you "this condition is now confirmed at the higher timeframe." If the slot is on On Bar Close? = OFF, the basis used to evaluate the condition was a live higher-timeframe read that may not survive the close of its own higher-timeframe bar. Read MTF & Repainting before you wire an alert on an OFF slot.

What an alert confirms

An Axiom BB CTX alert confirms exactly the following:

• The named condition (basis-trend state, blended-trend state, or full-stack alignment) was true at the close of a chart bar, evaluated under the slot configuration the indicator carried at the time the alert fired.

That is the entire confirmation. It is real, it is testable, and it is narrower than most readers' first instinct says it is.

An alert does not confirm:

• That price has done anything.

• That a trade is appropriate.

• That a setup is present.

• That the higher-timeframe bar has closed (for OFF slots).

• That the conditions on adjacent timeframes agree (for per-slot alerts; that is what alignment alerts are for).

• That the slot configuration that fired the alert is still the configuration on the chart now.

If you find yourself wanting to act directly off a basis-trend alert, ask what the alert told you that price action and the chart did not already tell you. The honest answer is usually "it sent me a notification at a moment I might not have been watching." That is genuinely valuable — a notification gets your attention onto a chart you would otherwise have missed. It is not the same thing as a confirmation. A notification is a prompt to look. A confirmation is an assertion that the conditions support the action you are considering. The indicator emits the first and does not claim the second. When you wire an alert, wire it as the first. When you catch yourself treating it as the second, stop and open the chart.

The alignment alerts, in particular

All BB Slot Bases Uptrend and All BB Slot Bases Downtrend are designed for the case where a reader wants to know when every enabled slot agrees on direction. They are stricter than the per-slot alerts, which makes them useful — and they have one feature that surprises new readers.

Hidden-plot slots count. An enabled slot whose Hide BB NN Plot is true still participates in the alignment vote. If you have hidden a slot because you do not want its lines on the chart, but you have not disabled it, that slot is still enforcing the "all" condition.

The implication is direct: if you ever find yourself thinking "I see three of three visible slots agreeing, why is the alert silent?", check for an enabled-but-hidden slot. It may be the slot voting against alignment.

To keep alignment alerts honest, decide which slots you want included and disable the rest. Hiding is a visibility choice, not an exclusion choice.

The alignment counters only include enabled slots that currently have a non-na basis. A slot that has not yet accumulated Length: bars of history — common on early bars after a chart load, or on a higher-timeframe slot at the very start of a session — is not part of the "all" vote until it produces a basis. On early history, alignment can describe the valid subset rather than every enabled slot you see in settings.

The blended-trend alert

The blended basis trend is a weight-majority vote across enabled slots with non-zero blend weight. The plain-language rule is: the side whose contributing slots carry more total weight wins, and a tie resolves to uptrend. On early bars where a weighted slot does not yet have a real basis value, do not lean on the blended trend; the script has not had enough history to make that slot meaningful yet.

That rule is documented at depth in For the Geeks. For alert wiring, the only thing you need to remember is that the blended-trend alert is a function of your weights. Change the weights, and the conditions under which the blended-trend alert fires change with them.

If your weights are 33.3 / 33.3 / 33.3 across the default three slots and all three slots have usable history, the blended trend reports uptrend whenever at least two of the three slots' bases are uptrend. If your weights skew heavily toward one slot, that slot dominates.

Wire the blended-trend alert when you specifically want a single notification that summarizes your weighted picture. Do not wire it as a substitute for per-slot alerts, because a single weighted slot flipping across its trend-length threshold can move the weighted vote, especially with skewed weights.

The hidden alert-count plots

Four count plots are exposed by the indicator and available inside TradingView's alert-message templates. They do not draw on the chart.

• Active Basis Uptrend Count — the number of enabled slots whose basis is in uptrend state.

• Active Basis Downtrend Count — counterpart for downtrend.

• Active Above Basis Count — the number of enabled slots where the chart's price is above that slot's basis.

• Active Below Basis Count — counterpart for below basis.

You reference them in TradingView's alert-message field with the standard placeholder syntax (TradingView's docs are the authoritative source for that syntax — this manual does not promise platform-side templating behavior). The use case is messages like:

"BB 03 basis uptrend; 4 of 5 enabled slots in uptrend; 3 of 5 above basis."

That kind of message gives a reader a more nuanced picture than the binary alert condition alone, without forcing them to open the chart.

The counts include enabled-but-hidden slots, the same way alignment alerts do. The "how many slots agree" picture you get from the count is a function of which slots you have enabled, not which slots you can see.

What you can wire — and what you cannot wire

The indicator does not expose:

• Band-touch alerts. Price touching an upper or lower line is not a fired condition; you would need to build a separate plot or alert in another layer to cover that case.

• Squeeze alerts. There is no built-in detection of compressed volatility.

• Crossover alerts. Price crossing a basis is not gated.

• Slot-disagreement alerts. There is no negative form of the alignment alert ("the slots are not aligned"). You can approximate one by inverting the alignment conditions inside TradingView, but the indicator does not ship one.

Those are deliberate omissions. The pack's posture is that touches, squeezes, and crossovers are reads you take at the chart, not alerts the indicator confirms for you. If you need them automated, you build them — and you carry the trust burden for what those alerts mean.

Wiring an alert without making it dishonest

A few habits will keep your alerts well-behaved.

1. Name your alerts with their context. Include the slot's timeframe, its Basis Trend Length, and its On Bar Close? posture in the alert name or message. "BB 03 Basis Is Uptrend (60m, trendlen=3, OnClose=ON)" is a longer name than "BB 03 Basis Is Uptrend," and it is the right name. When you reread the message at 2pm, you will know what the alert means.

2. Save the slot configuration with the alert. TradingView stores the indicator's settings inside each alert. If you change settings on the chart later, the alert keeps firing under the configuration it was created with. That is usually what you want, but it means the alert can drift away from what the chart shows. Recreate alerts when you change a slot's Length:, Basis Trend Length:, or On Bar Close?.

3. Do not wire alignment alerts on a chart with hidden slots you have not deliberately decided about. Walk the slot list once before you create the alert, decide which enabled slots are part of the "all" condition, and disable the rest.

4. Use the count plots when the binary alert is too coarse. "All slots agree" is a high bar. Most reads do not deliver it. If you find yourself wanting a softer notification, the count plots in an alert message are usually closer to the picture you actually want.

5. Treat OFF-slot alerts as soft notifications. A basis-trend alert on a slot with On Bar Close? = OFF is firing on a live higher-timeframe value. Treat the alert as a "look at the chart" prompt, not as a confirmation of state. The state may not survive the higher-timeframe bar's close.

Where to go next

• For the full meaning of "rising" and "falling" basis and how Basis Trend Length shapes them, Visuals & Logic.

• For why the OFF posture changes the trust posture of an alert, MTF & Repainting.

• For exactly how the blended-trend vote resolves and where ties go, For the Geeks.

• For the broader question of what to trust, what to verify, and what not to assume about alerts here, Limitations & Trust Boundaries.