Alerts

Axiom DC ships ten alert conditions on the Base trim. They fall into three groups: six per-slot basis-trend alerts, two blended basis-trend alerts, and two alignment alerts. This page lists every alert, states what each one does and does not confirm, and explains the two hidden count plots the indicator exposes as handles for custom alert messages.

The ten alerts, at a glance

Every one of these is gated at chart-bar close, not at higher-timeframe-bar close. More on what that means below.

The per-slot basis-trend alerts

Each slot has two alerts, one per direction. "Rising" and "falling" are decided by comparing the slot's current smoothed basis to its value Basis Trend Length bars ago on the slot's own timeframe. The comparison is greater-than-or-equal for rising.

Two things follow:

• The trend read is a slot-local condition. It says something about that slot's smoothed midpoint at that slot's timeframe, not about price generally.

• The meaning of "rising" depends on two numbers on that slot: Basis MA Length (which sets how smoothed the basis is) and Basis Trend Length (which sets how far back the comparison reaches). A rising alert on a heavily smoothed basis with a long trend length is a different event from a rising alert on a one-bar basis with a length-1 trend window.

Before you attach a per-slot basis-trend alert, know what those two numbers are on that slot.

The two blended basis-trend alerts

The blended alerts fire on the blended channel's basis-trend state. That state is resolved by weighing enabled, non-zero-weight slots' trend booleans against each other — sum the weight voting rising, sum the weight voting falling, report rising when the rising sum is greater than or equal to the falling sum.

The tie-break is deterministic and is worth naming before you rely on a blended alert: equal weight on both sides resolves as rising. This is not an opinion about what the market is doing — it is a rule so the blended state always has a value. If your weights are set up in a way that produces common ties, the blended alerts will lean toward the rising side in those ties. Read Visuals & Logic for worked examples.

One warmup boundary matters here. The blend can stay numeric while slot values are still na, because missing values are zero-filled before the blend is calculated. If every contributing slot is still warming up, or every enabled slot has a zero weight, the blended alert state can be technically present without being useful. Do not use blended alerts until at least one enabled, non-zero-weight slot has valid plotted data.

The two alignment alerts

Alignment is the strictest of the three groups. All DC Slot Bases Uptrend fires only when every enabled slot with a non-na basis is rising at the chart-bar close. Not a majority, not the blended composite. The falling alert is the mirror. Disabled slots are excluded from the alignment test, and early-warmup slots do not count until their basis is valid.

A subtlety worth spelling out: hidden-plot slots still count toward alignment. Hide DC NN Plot suppresses the slot's three lines but does not change its enable state, so the alignment vote sees it. If Slot 03 is enabled, hidden, and disagreeing with Slots 01 and 02, the alignment alert stays silent. That is the alert working correctly. If a reader wants a slot excluded from alignment, they need to disable the slot (Enable DC NN off), not hide it.

On a three-slot stack, alignment is a strong agreement condition. It asks for all three independent timeframes to agree on direction at the same moment, which is a useful fact on its own. Treat the alert that way — as a notification that the condition held on a closed bar, not as a trade trigger. Visuals & Logic covers the reading side of alignment in more depth.

What an alert does, and does not, confirm

Every alert in this indicator, including the alignment ones, is a notification that a computed condition held on a closed chart bar, under the configuration you had at that moment. That is what it confirms.

Specifically, an alert does not:

• Confirm the higher-timeframe bar was closed. Under On Bar Close? = OFF, the trend boolean underneath the alert may have been computed against a live higher-timeframe bar. The alert still fires at the chart-bar close, but the value that drove it can change as the higher-timeframe bar keeps forming.

• Confirm price direction. A rising basis on a slot is exactly that — a smoothed midpoint that is higher than it was some number of bars ago. Price can be below the basis, moving away from the basis, or doing anything else.

• Confirm that the configuration you had when you set up the alert is still the configuration the alert means. Change a slot's Basis Trend Length and the same-named alert on that slot now fires on a different event.

• Confirm a trade, an entry, a setup, or any intent. There is no execution-grade signal in this indicator. The tool surfaces computed conditions. The reading is yours.

This is worth sitting with before you set up an alert. The difference between "the condition held on a closed bar" and "the market just told me to do something" is the difference between a helpful notification and a trigger you should not be trusting to that degree.

A small habit that pays off later: when you create an alert, jot down the four numbers behind it — the slot's Length, Basis MA Length, Basis MA Type, and Basis Trend Length — wherever you keep trade notes. Three weeks later, when the alert fires on a setup you are about to act on, you will want to know whether the meaning of the alert has drifted with a configuration change you half-remember making. Alerts are durable; the configuration that gives them meaning is not.

Chart-bar close gating, explained

The indicator gates every alert through a confirmed-bar check: the condition must be true on a chart bar that has just closed. In practice that means:

• Alerts do not fire mid-chart-bar. If a trend boolean flips at the start of a chart bar and flips back before the bar closes, no alert fires.

• "Chart bar" is the chart's own timeframe. On a 1-minute chart, alerts fire at each 1-minute close. Under On Bar Close? = OFF, a 60-minute slot is reporting the live 60-minute bar's value at each 1-minute close — so the alert you see was evaluated against a value that may redraw before the 60-minute bar finishes.

• Under On Bar Close? = ON, the slot's value at any chart-bar close is the previous confirmed higher-timeframe value. The alert you see is evaluated against a value that no longer changes, which is what most readers actually want from an alert.

A simple rule: if you are going to rely on alerts, run the indicator with On Bar Close? = ON. The tradeoff is exactly the same as everywhere else — you accept one higher-timeframe bar of latency in exchange for values that do not move underneath you. MTF & Repainting has the full treatment.

A verification habit worth building: after you first set up a meaningful alert, watch one or two of its fires with the chart open before you trust it unsupervised. Was the slot value the alert fired on still on the chart when you reviewed it an hour later? Under ON it will be. Under OFF it may not be, and that is what you are learning from the drill. It takes two sessions to know whether your alert configuration is telling you the truth you think it is.

The two hidden count plots

The script exposes two hidden plots that do not draw on the chart and are not alerts themselves:

• Active Basis Uptrend Count — the count of enabled slots with valid bases currently reporting rising basis.

• Active Basis Downtrend Count — the count of enabled slots with valid bases currently reporting falling basis.

These are plot handles, available inside alert-message templates as values you can reference. They let you write an alert-message body that says something like "two slots are up, one is down" without hard-coding the numbers. Referencing them is a TradingView alert-message mechanic; for the exact syntax the platform expects in the alert-message body, consult the TradingView documentation — this indicator exposes the plots, it does not define the template language.

Two notes on the counts that matter for the Base trim:

• There are two count plots, not four. The hidden counts are basis-trend counts only. There is no Active Above Basis Count or Active Below Basis Count on this trim. If you need richer count plots, the CTX trim carries a broader set.

• The counts reflect enabled slots with non-na bases, regardless of hide state. A hidden-but-enabled slot still shows up in the count. This is consistent with how alignment treats hidden slots.

A few practical notes on setup

• Set up alerts from TradingView's alert dialog after the indicator is on the chart and you can see its output. Input toggles do not rewrite the alert roster; an alert can still exist while its enable gate keeps it from firing. For example, a blended alert will not fire while Enable Blended DC is off.

• A per-slot alert for a disabled slot will never fire. This is by design — the enable gate is checked inside the alert-trigger condition.

• If you are running a hidden-plot slot for alignment-only purposes (Enable = true, Hide DC NN Plot = true, Blended Weight = 0), the slot participates in alignment alerts and does not steer the blend. See Workflows for where this pattern earns its keep.