Alerts

The Base trim exposes ten alert conditions and two hidden count plots. This page names each, describes what it fires on, and — importantly — describes what each one does not confirm. Alerts here report computed conditions on closed chart bars. They do not report intent, they do not report direction about future price, and they do not confirm that the higher-timeframe bar underneath a slot has closed.

The ten alert conditions

All ten alerts are gated by the close of the chart bar in which the condition was satisfied. None of them fire intrabar on the chart timeframe.

Per-slot basis-trend alerts (six total)

Two things to carry with you when you wire these:

• The Basis Trend Length: value for each slot governs how quickly the trend state can flip. Slot 01 with Basis Trend Length: 3 is making a three-bar comparison on the slot's higher timeframe. Slot 03 with Basis Trend Length: 10 is making a ten-bar comparison on its higher timeframe. Two slots with very different Basis Trend Length: values can disagree not because they disagree about the market but because they disagree about the memory length of the trend test.

• The alert fires when the condition holds at chart bar close. If the basis flipped intrabar and flipped back before close, the alert does not fire. This is the bar-close guard doing its job.

Blended basis-trend alerts (two total)

The blended basis-trend alert is not the blended basis changing direction visually. It is the vote result across the slots feeding the blend. A blended basis can curl slightly downward on the chart while the weight-majority of slots still reads uptrend, and the alert reports what the vote said, not what the curve looked like to the eye. See For the Geeks for the rule and the tie-break reasoning.

Note also: Hide Blended BB Plot does not silence these alerts. The blend math is still computed when the plot is hidden, and the alert still fires at chart bar close. If you want the alerts silenced, turn Enable Blended BB off.

Alignment alerts (two total)

The alignment alerts are the tightest read this indicator offers, because they do not average anything — they fire only when every voice in the stack that is currently present agrees on direction. Three qualifiers matter:

• Enabled only. A slot disabled with Enable BB 0N: false is excluded from the alignment count. If you disable a slot, alignment becomes a two-slot agreement check.

• Hidden plots still count. A slot with Hide BB 0N Plot: true is still enabled; it still participates in the alignment alert. Hiding a slot does not drop it out of the count.

• na slots are excluded. On the earliest bars of the chart, a slot's basis may still be na while Length: accumulates its first full lookback. Those bars are excluded from the alignment check.

Partial agreement — two slots uptrend, one slot downtrend — does not fire an alignment alert. That is the correct behaviour: partial agreement is not alignment.

The two hidden alert-count plots

The indicator also publishes two plots that do not render as lines on the chart but are available to TradingView as numeric values inside alert messages.

These are not chart visuals and they are not alerts in their own right. They exist so you can reference counts inside alert message templates using TradingView's placeholder syntax — something like writing an alert message that includes the phrase {{plot("Active Basis Uptrend Count")}} slots in uptrend. Because the plots use display.none, do not plan a live demonstration around seeing these rows in the Data Window. They are calculated hidden plots intended for placeholders and platform consumers that can reference hidden plots.

Two honest notes:

• The exact placeholder syntax and what TradingView will do with it is TradingView's behaviour, not the indicator's. TradingView's documented plot placeholder form uses double quotes inside the placeholder, for example {{plot("Active Basis Uptrend Count")}}. Refer to TradingView's alert message documentation for what is actually supported; this pack will not make promises about platform-side templating.

• The counts are from enabled slots — hidden-plot slots are included, disabled slots are not.

What a fired alert confirms and does not confirm

A fired alert confirms one specific thing: that a computed condition was satisfied at the close of the chart bar under the configuration in place when the alert fired. That is the whole claim.

It does not confirm:

• Any direction about future price. The alert is a description of a past computation, not a forward-looking signal of any kind.

• Any intent or action. Nothing in the indicator is structured as a setup or a trigger for a trade. The alert names a condition; the reader decides what the condition means for their process.

• That the higher-timeframe bar underneath a slot has closed. Under On Bar Close? OFF, the slot is reading the live higher-timeframe bar. The alert will still fire at chart bar close if the condition held at that moment, and the underlying higher-timeframe bar may still change before it itself closes. If you care about this distinction — and you probably should — read MTF and Repainting.

There is a pull, especially under pressure, to treat any fired alert as if it were permission. It is not. An All BB Slot Bases Uptrend message reaching your phone is not the tool telling you to buy anything; it is the tool reporting that under the Basis Trend Length: values you configured, on the slots you enabled, at the close of a specific chart bar, every basis was at or above its value that many bars ago. Whether that state is worth acting on is a separate decision — the one the reader owns — and it depends on context the alert has no access to. Holding the distinction between "condition reported" and "action licensed" is most of the discipline this indicator asks of you.

Bar-close gating and the interaction with On Bar Close?

Every alert on this indicator is gated by the close of the chart bar. Under On Bar Close? ON, that chart-bar gate is layered on top of a slot that is already returning the previous confirmed higher-timeframe value. Both postures agree that the value is stable and the alert is clean.

Under On Bar Close? OFF, a subtlety appears. The chart-bar gate still holds — the alert does not fire intrabar on the chart. But the slot value underlying the alert at that chart-bar close may have been a live higher-timeframe read, because the higher-timeframe bar had not yet closed. The alert reports what was true of the slot at chart-bar close. It does not report that the slot's higher-timeframe bar was itself confirmed.

If you treat an OFF-posture alert as definitive without accounting for this, you are over-reading it. Either accept the tradeoff on purpose and act on the higher-timeframe live read, or keep On Bar Close? ON so the alert and the slot it reads from are both on confirmed ground.

What this indicator does not alert on

Three alerts that readers often expect from a Bollinger indicator are not here:

• No band-touch alerts. Price crossing a slot's upper or lower band does not fire an alert from this indicator.

• No squeeze alerts. There is no "bands narrowing" alert.

• No crossover alerts. Basis-crossing-price, upper-crossing-lower, or any pair-wise cross is not exposed.

If you need any of those, you will build them in a separate layer — another indicator on the same chart, TradingView's generic price alerts, or your own broker-side logic. The Base trim deliberately ships the alert set above and nothing else.