Alerts

Alerts

Axiom DC Pro provides a full set of alert conditions — three per slot plus nine on the blended channel, for a total of 39 individual alertconditions. Rather than walking through each one individually, this page teaches the alert system by family. Once you understand what a family does, you can apply that understanding to any slot or blended alert in the group.

Every alert in the indicator fires only on confirmed chart-bar closes. They will not trigger during intrabar price movement. That remains true even if a slot is allowed to use building higher-timeframe values for its calculations. If you need intrabar alerts, this indicator does not provide them.

Alert families

Per-slot regime alerts

Each of the ten slots has three alerts:

These are structural state alerts. "Above basis" means price is in the upper half of that timeframe's channel. "Below basis" means the lower half. "Basis change" fires once when the state flips — useful for tracking structural pivots on a specific timeframe.

What these alerts do not tell you: Nothing about trend direction, momentum, or whether the condition will persist. A single bar closing above the basis triggers the alert. If price dips back below on the next bar, the alert fires again in the other direction. These are positional readings, not trade signals.

Blended regime alerts

These work identically to the per-slot regime alerts, except they reference the blended channel. The blended basis is the weighted average of all enabled slots' midpoints that carry non-zero weight, so the alert reflects a composite structural position.

The extra consideration: Because the blended basis depends on weights, changing the weight distribution shifts where the blended basis sits and therefore shifts when these alerts fire. Two traders using the same indicator with different weights will get alerts at different price levels. The alert is only as meaningful as the blend feeding it.

Blended cross alerts

Cross alerts fire at the moment of the crossing — when price moves from one side of a level to the other. They fire once per crossing, not continuously while price stays on one side.

What to watch for: A cross of the blended upper or lower can look like a breakout or breakdown, and sometimes it is. But the blended levels are weighted composites, and a small weight change can shift the upper or lower enough to change when the cross fires. If you are relying on a blended cross alert as part of your process, make sure the weight distribution is deliberate and stable.

Alignment alerts

These are the broadest structural alerts in the indicator. They fire when every active slot agrees on the same regime.

The critical caveat: The meaning of "all slots agree" depends entirely on how many slots are enabled and how diverse their timeframes are. With one slot enabled, the alignment alert fires on every bar that closes above or below that single basis — it is trivially frequent. With three well-separated timeframes, alignment means something structurally meaningful. With ten slots on similar timeframes, the alert fires almost as often as it would with one slot.

Before setting up an alignment alert, count your enabled slots and check their timeframes. Ask yourself: when this alert fires, what am I actually being told?

Setting up alerts

To create an alert from this indicator:

1. Open the alert creation dialog in TradingView (shortcut: Alt+A on desktop, or the alarm clock icon).

2. Under "Condition," select Axiom DC Pro.

3. Choose the specific alert condition from the dropdown. The alerts are named as shown in the tables above — per-slot alerts include the slot number (DC 01, DC 02, etc.).

4. Set your preferred notification method (popup, email, webhook, etc.).

5. Name the alert something you will recognize when it fires — include the slot number and timeframe so you know what triggered it without opening the chart.

You can create multiple alerts for different slots or conditions. Each alert condition is independent.

Verification

You can verify that alerts are firing correctly, and it is worth doing at least once before you build a process around them.

1. Apply the indicator to a chart in replay mode on a liquid instrument.

2. Step forward one confirmed bar at a time.

3. At each step, check the data window for the slot's basis value and compare it to the closing price. If close >= basis, the "above basis" condition is true. If the state just flipped from the prior bar, the "basis change" condition is true.

4. Confirm that alerts do not trigger mid-bar. If you step forward during a building bar, no alert should fire — they are gated to confirmed closes only.

5. For blended alerts, verify the blended basis value in the data window against the close. Keep in mind that the blended basis depends on all contributing slots' weights, so if you changed weights since setting up the alert, the trigger level has shifted.

If you suspect an alert is firing at the wrong time, check two things. First, the On Bar Close setting for the relevant slot — if it is off, the slot's values update intrabar, which can shift the basis level between the time you expect the alert and the time it actually fires on the confirmed bar. Second, whether any hidden slots with weight are moving the blended basis to a level you did not anticipate.

Over-trust risks

Treating alignment alerts as strong signals. The "All DC Slots" alerts sound powerful, but their strength is a function of your slot setup. Know what is behind the alert before you act on it.

Stacking multiple blended alerts as "confirmation." If you set up alerts for blended-above-basis and blended-crossed-above-upper, both fire based on the same blended channel, the same weights, the same slots. Firing together does not add independent confirmation — it is the same composite read triggering two conditions simultaneously. If you want independent confirmation, the alerts need to come from structurally independent sources: a per-slot alert on one timeframe and a blended alert that draws from different slots, or alerts from entirely different tools.

Ignoring the bar-close-only design. All alerts fire on confirmed closes. If price spikes above the blended upper mid-bar and retreats before the bar closes, the alert will not fire. This is protective — it prevents false triggers from intrabar noise — but it means fast-moving events that reverse within a bar will not be captured. That is a feature, not a gap, but know it going in.

Forgetting that hidden slots affect blended alerts. If a hidden slot with weight is pulling the blended channel, all blended alerts are shaped by data that is not visible on the chart. If a blended alert fires at a price level you did not expect, check your hidden slots.

What alerts are for — and what they are not

These alerts are structural state notifications. They tell you that a condition is true on a confirmed bar close. They do not tell you what to do about it.

An alert that fires is the beginning of a decision process, not the end of one. When a per-slot basis change fires, it means the structural regime on that timeframe just flipped. Whether that flip matters — whether it is a meaningful structural shift or a single-bar noise event that will reverse on the next close — depends on context the alert cannot carry. Your job after an alert fires is to look at the chart, check the individual slots, assess whether the structural picture supports action, and decide based on your own process.

If you find yourself acting on every alert without checking the chart first, the alerts are running your process instead of serving it. Consider reducing the number of active alerts to the ones that genuinely flag structural conditions you cannot afford to miss, and treat the rest as informational rather than actionable.