Alerts

Axiom MA CTX exposes twenty-four alert conditions. This page lists every one, tells you what each condition actually confirms, and names the reads that get traders into trouble — not because the alerts are misleading, but because alerts of this shape are easy to mistake for more than they are.

Before the catalogue, one distinction carries the rest of the page. Every alert here is gated by the chart-bar confirmed state. When an alert fires, the chart bar on which the condition held is closed. Chart-bar confirmed is not the same thing as HTF confirmed. A slot whose On Bar Close? is OFF is reading the live HTF value, which can still redraw until the slot's HTF bar closes. That slot can satisfy a trend condition at chart-bar close using a value that walks away from you five minutes later. The alert fired honestly — the condition was true at chart-bar close — and the HTF read behind the condition is still free to move. If this is the first time you are meeting that distinction, stop and read the split in MTF & Repainting before you wire any alerts live.

The twenty-four conditions

Per-slot trend family (twenty)

Two conditions per slot, ten slots, twenty total.

A slot's trend state is computed from that slot's current MA compared to the MA Trend Length bars ago on that slot's timeframe. A slot's Trend Length is independent of every other slot's Trend Length. The slot's own repaint posture (On Bar Close?) decides whether the current MA is the last confirmed HTF value or the live HTF value.

A disabled slot never fires either of its two alerts — disabled means out of everything.

Blended trend family (two)

Two things worth noting:

• The blended trend direction is resolved by a majority-weight vote across slot trend states, not by the slope of the blended line itself. The blended plot can look almost flat on the chart while the blended trend alert still fires uptrend — because the uptrend-voting weights added to more than the downtrend-voting weights.

• Ties register as uptrend. The comparison is up-weight ≥ down-weight. The exact tie-break rule is disclosable; the code pattern that implements it is not something this manual publishes.

Alignment family (two)

The word to notice is every, but the set is the active set. A four-slot configuration with three active slots in uptrend and one active slot in downtrend does not fire the All Uptrend alert. A slot whose MA is na is not counted in that alignment set on that bar; if the remaining active slots all agree and at least one active slot exists, the aggregate can still fire.

And the phrase to sit with: every enabled slot, whether its plot is visible or not. Hiding a slot does not take it out of the alignment count. Disable the slot if you want it out of this alert.

Bar-confirmation gating in plain words

The chart-bar-confirmed gate means the alert looks at the conditions as they stood at the close of each chart bar. Inside the chart bar, the conditions may be coming and going. They are not alerted on. The alert fires at the close of the bar in which the condition was true.

What this does not mean:

• It does not mean the slot's HTF bar was closed. On Bar Close? and bar-confirmed are two different things. On Bar Close? decides what value the slot is reading; bar-confirmed decides when the alert fires.

• It does not mean the slot was computed honestly. A slot with On Bar Close? OFF might have satisfied the trend condition at chart-bar close using a live HTF value that will redraw when the HTF bar closes. The chart-bar-confirmed gate does not save you from that; only ON does.

• It does not mean anything about price.

Hidden count plots

The script exposes two invisible plots (display.none) whose values can be referenced inside TradingView alert message templates if you want to include them in the notification text you receive:

• Active Uptrend Count — the count of enabled slots with non-na MA values whose trend state at chart-bar close is uptrend.

• Active Downtrend Count — the same, for downtrend.

These are bar-by-bar counts across enabled slots. You can reference them in alert messages to add context to the notification — "3 up, 1 down" is a more useful string than a bare condition name. TradingView's alert-message templating is outside the scope of this manual; the plots are here for you to use, not for this manual to teach TradingView's UI.

One boundary matters: these active counts describe alert and alignment participation. They do not describe which slots are weighted into the blended value.

What an alert confirms

• That the computed condition was true on a closed chart bar, under the slot configuration present at the time the alert fired.

• That the slot or slots referenced by the condition's name were the ones evaluated.

• That barstate.isconfirmed on the chart bar was true at the moment of evaluation.

What an alert does not confirm

• That the slot's HTF bar was closed. On an OFF slot, the trend state could have been derived from a live HTF value.

• That price is doing anything in particular. The alert is about the slot's own smoothed state, not about price.

• That your Trend Length was a reasonable choice. A Trend Length: of 1 will produce noisy trend alerts. The alert cannot warn you that you chose the comparison window to be noisy.

• That the slot's On Bar Close? posture is what you wanted. Alerts fire on conditions, not on configurations.

• That you ought to act. This tool does not decide that for you.

Reading trend alerts honestly

A per-slot trend alert is context, not instruction. It reports that the slot's comparison between its current MA and the MA Trend Length bars ago on the slot's timeframe resolved in the named direction at chart-bar close. It does not say anything about price, anything about the other slots, anything about the blended line, anything about whether the read will persist past this bar, and anything about whether the market is in a regime where this kind of comparison is informative at all. The alert is smaller than it looks.

If you want an aggregate read, use the All-Uptrend or All-Downtrend alert. Those aggregates look at every enabled slot — including the hidden ones. If you are building a routine on a subset of slots, the way to exclude the others is to disable them, not to hide them. Hiding is a visual control. The alert logic does not read pixels; it reads enabled slots.

The blended trend alert is also context. It is a weighted-majority vote. A lime blend with a nearly flat blended line is a legitimate alert fire — it means the summed up-weight edged or tied the summed down-weight by the tie-break rule. It does not mean the composite curve is turning. A trader who reads the blended alert as "the blend is trending up" and the blended line as "the composite curve is going up" will occasionally see the two disagree and assume the tool is broken. It is not. The alert is reporting the vote. The line is drawing the weighted average. The two are not the same measurement.

Common misreads to avoid

• "The All Uptrend alert did not fire so the visible stack is not aligned." Accurate in letter, misleading in practice if one hidden active slot is voting the other way. If a slot is na, it drops out of the active alignment count for that bar rather than forcing the aggregate to wait. Check your Data Window before drawing the conclusion.

• "The per-slot alert fired so the HTF slot is confirmed up." Only true if the slot's On Bar Close? is ON. Under OFF, the trend state was computed against a live HTF value.

• "The blended alert agrees with the visible blend colour." It does, because both read the same weight-majority vote. That does not make the blend a consensus read; the alert reports the same vote the line colour reports.

• "Hiding a slot excluded it from the All Uptrend alert." No. Hidden slots are counted. Disable them to drop them.

• "The per-slot alert is a crossover alert." It is not. The tool has no crossover alerts. A per-slot trend alert is not the same as "price crossed this MA" and is not the same as "Slot A's MA crossed Slot B's MA." There are no price-cross or MA-cross alerts in this indicator.

• "My alert fired but the chart does not show a flip." Check whether the chart bar closed. Alerts fire on the close of the bar whose condition satisfied the rule. On low timeframes this is fast enough to be invisible; on higher timeframes the chart bar may still be forming when you receive the notification on the previous bar's close.

Creating and managing alerts

Alerts are created via TradingView's standard alert dialog. This manual does not reproduce TradingView's UI, because TradingView controls that surface and revises it independently. The general path on every TradingView build: open the alert dialog, select Axiom MA CTX as the condition source, choose one of the twenty-four conditions listed above, configure the message text (the {{Active Uptrend Count}} and {{Active Downtrend Count}} plot references are available), and save.

If you do not see an alert fire when you expect one, Troubleshooting has a symptom-to-cause table. The most common causes: the slot you expected to contribute was disabled, the chart bar did not close yet, or the alignment alert was waiting on a hidden slot you thought was excluded.