Alerts
Axiom DC Lite provides 18 alert conditions. All of them fire only on confirmed (closed) bars — no alert will trigger while a bar is still forming. This is a deliberate safety choice: the alert tells you what happened...
Written By Axiom Admin
Last updated About 1 month ago
Alerts
Axiom DC Lite provides 18 alert conditions. All of them fire only on confirmed (closed) bars — no alert will trigger while a bar is still forming. This is a deliberate safety choice: the alert tells you what happened after the bar closed, not what is happening right now.
This page documents every available alert, what it confirms, what it does not confirm, and where overtrust is likely.
How alerts work in this indicator
Before diving into the catalog, understand three things about how alerts behave here:
1. Every alert is bar-close gated.
All 18 alert conditions require barstate.isconfirmed to be true. This means the condition is only evaluated after the current chart-timeframe bar has closed. An alert set on a 5-minute chart will only fire after the 5-minute bar closes, even if the condition was briefly true during the bar's formation.
2. Alert bar confirmation is independent of On Bar Close.
The On Bar Close setting controls whether the Donchian Channel values come from confirmed or building higher-timeframe bars. The alert firing is always gated by the chart-timeframe bar close. These are two different confirmation mechanisms operating at different levels:
On Bar Close controls what HTF data the channels use
barstate.isconfirmedcontrols when alerts are allowed to fire
Turning On Bar Close off makes the channels update faster, but alerts still wait for the chart bar to close.
One nuance matters here: the slot timeframe supplies the basis, but the chart timeframe supplies the closing price that gets compared against it. A 60-minute slot on a 5-minute chart still evaluates on confirmed 5-minute closes; the 60-minute part is the source of the basis, not the alert cadence.
3. Alert messages include dynamic placeholders.
Every alert message uses {{ticker}} and {{interval}}, which TradingView fills in when the alert fires. You will see the actual symbol and chart interval in the notification.
Per-slot basis regime alerts
Each slot has three alert conditions based on where price closed relative to the slot's basis (midpoint). With three slots, that gives nine per-slot alerts.
DC XX Is Above Basis
What it confirms: At the moment this chart bar closed, price was at or above the Donchian midpoint for this slot's timeframe.
What it does NOT confirm:
It does not confirm a trend. Price can be above the basis during a choppy sideways market.
It does not confirm that the condition will persist on the next bar. Price may cross below the basis on the very next close.
It does not tell you anything about the other slots. DC 01 can be above its basis while DC 03 is below.
Overtrust risk: Treating "above basis" as bullish confirmation. The basis is a structural midpoint, not a trend indicator. Price oscillating around the basis is normal, not a series of actionable signals.
DC XX Is Below Basis
What it confirms: At bar close, price was below the Donchian midpoint for this slot's timeframe.
What it does NOT confirm: Same caveats as above. Not a trend signal. Not persistent. Not multi-slot.
DC XX Basis Change
What it confirms: A regime transition occurred on this confirmed chart bar relative to this slot's basis. Price was on one side of the slot basis on the previous confirmed chart bar and is now on the other.
What it does NOT confirm:
It does not confirm a trend reversal. The transition may reverse on the very next bar.
It does not tell you the direction of the change. The alert fires on either direction — crossing above or crossing below. Check the chart or combine with the above/below alerts to know which direction.
Overtrust risk: Reading basis changes as early reversal signals. In choppy markets, the basis change alert can fire repeatedly as price oscillates around the midpoint. Each firing is technically a "regime change," but most of them are noise.
Blended basis regime alerts
The same three alert types, but for the blended channel:
Blended DC Is Above Basis
What it confirms: Price is at or above the weighted midpoint of the combined multi-timeframe channel.
Additional caveat: The blended basis is a weighted average of the individual slot bases. When timeframes diverge, the blended basis sits between conflicting midpoints. Being "above the blended basis" may mean you are above an arithmetic middle that does not correspond to any real structural level on any individual timeframe.
Blended DC Is Below Basis
Same structure and caveats as above, for the below-basis case.
Blended DC Basis Change
Same structure as the per-slot basis change. The additional risk with the blended version is that the blended basis can shift due to weight changes, slot enables/disables, or slot-level movements that partially cancel each other. A blended basis change is noisier than a per-slot basis change because it aggregates multiple sources of movement.
Multi-slot alignment alerts
These two alerts fire when all enabled slots agree about price's position relative to their respective bases.
All DC Slots Above Basis
What it confirms: At this bar close, price was above the Donchian midpoint on every active timeframe. All structural horizons agree about price's position relative to the range center.
What it does NOT confirm:
It does not confirm trend strength, momentum, or continuation.
It does not weight the agreement. If DC 01 is barely above its basis while DC 03 is strongly above, the alert fires the same way.
If only one slot is enabled, "all slots above" means that one slot. The alert does not require multiple slots.
Overtrust risk: This is the alert most likely to feel like a confirmation signal. Multi-timeframe alignment sounds authoritative. But "price is above the midpoint on all timeframes" during a strong trend is the default state — it is not a predictive signal, it is a description of what a trend looks like in structural terms. The alert becomes most useful as a filter (e.g., only consider long setups when this condition is true) rather than as a standalone trigger.
All DC Slots Below Basis
Mirror of the above. Same caveats apply.
Blended channel cross alerts
These four alerts fire when price crosses specific levels on the blended channel. They use TradingView's crossover/crossunder functions, which means they fire on the bar where the cross happens, not on every bar where the condition is true.
Blended DC Crossed Above Upper Channel
What it confirms: Price just moved above the blended channel's upper boundary. In structural terms, price has exited the top of the combined multi-timeframe range.
What it does NOT confirm: It does not predict whether price will stay above the boundary, return to the channel, or continue higher. The cross is a structural event, not a directional signal.
Blended DC Crossed Below Lower Channel
What it confirms: Price just moved below the blended channel's lower boundary — exiting the bottom of the combined range.
Blended DC Crossed Above Basis
What it confirms: Price moved from below to above the blended midpoint. This is a regime transition at the blended level.
Difference from Blended DC Basis Change: The Basis Change alert fires whenever the regime flips in either direction. This cross alert fires only on the upward cross. Use the specific cross alerts when direction matters.
Blended DC Crossed Below Basis
Downward counterpart. Same structure.
What is NOT available as an alert
There are no alerts for individual slot channel crosses. If you want to know when price crosses DC 01's upper line, no built-in alert exists for that — only the blended channel has cross alerts.
For per-slot structural edge events, you are limited to the basis regime alerts (above/below/change). If per-slot boundary cross alerts are important to your process, this is a current limitation of the indicator.
Combining alerts into a workflow
Alerts become more useful when combined rather than used individually. Here are some combinations worth considering:
Multi-timeframe regime alignment as a filter:
Set the "All DC Slots Above Basis" alert as a prerequisite condition. When it fires, it tells you all structural horizons agree about price's position. Use that as a filter for other tools or decisions — not as a standalone entry trigger.
Blended channel boundary cross as a structural event:
The "Crossed Above Upper Channel" alert marks the moment price exits the blended structural range. This is potentially significant because it means price is now above the weighted combination of multiple timeframes' ranges. Pair it with a quick check of the individual slots: did price also exit the individual slots' channels, or just the blend? If it exited everything, the structural breakout is confirmed across horizons. If it only exited the blend (because the blend is compressed between diverging slots), the event is less meaningful.
Per-slot basis change as a slower reference, not a slot-timeframe event:
A basis change against DC 03's basis often deserves more attention than one against DC 01 because the longer-horizon basis itself tends to move more slowly. But the alert still fires on confirmed chart bars whenever price flips around that basis. In chop, even the long slot can fire repeatedly.
A concrete multi-alert scenario
Suppose you are monitoring a US equity intraday. You have set up the following alerts:
All DC Slots Above Basis — your structural alignment filter
DC 03 Basis Change — your longer-horizon regime warning
Blended DC Crossed Above Upper Channel — your structural range exit event
Early in the session, alert 1 fires: all slots show price above their respective bases. You note it. This is not an action trigger — it is context. It tells you structural alignment exists across all three horizons. You factor that into whatever else you are looking at.
An hour later, alert 3 fires: price just crossed above the blended upper boundary. You open the chart. You check whether price also exited DC 01's and DC 02's upper boundaries. It did — all three channels show price above the upper line, and the blended upper was crossed on the same bar. The structural range expansion is happening across horizons, not just in the blend.
Now you have two pieces of context — alignment and range exit — both confirmed on closed bars. What you do with that depends entirely on your trading process. The alerts did not tell you to buy. They told you what happened: structural alignment to the upside, and price has now moved beyond the combined structural range. Whether that means continuation, exhaustion, or noise is a question the alerts cannot answer. You still need to look at the chart, consider the broader context, and make a judgment.
Later, alert 2 fires: DC 03 basis changed. Price just crossed the longest-horizon basis on a confirmed chart bar. That is worth attention — not because it predicts anything, and not because the 60-minute structure itself necessarily reset on that exact bar, but because the slowest basis in the stack is no longer holding the same side of price.
What not to automate blindly
None of these alerts should drive automated trading without additional validation. Every alert tells you what happened on the last confirmed bar. It does not tell you what will happen next, whether the condition will persist, or whether the structural context has changed by the time you see the notification. The alerts are most useful as a monitoring layer that tells you when to look at the chart — not as a substitute for looking at it.