Alerts
The alert surface in Axiom CVD Osc Lite is useful when it reduces screen-watching without turning the indicator into a command system.
Written By AxiomCharts
Last updated About 3 hours ago
Alerts
The alert surface in Axiom CVD Osc Lite is useful when it reduces screen-watching without turning the indicator into a command system. This page exists to keep those expectations clean. The main distinction to learn is not just which alerts exist. It is the difference between:
- an alert that says a condition is true right now
- an alert that says something just changed
If you blur those together, the stack becomes much easier to overtrust. That matters most when you are tired or rushed, because an alert is often where traders start outsourcing judgment without noticing they did it.
The first rule
Every alert condition in this build is gated by the chart bar closing. That means the script only marks the condition true on confirmed chart bars. This is good for discipline, but it does not erase the higher-timeframe trust boundary. If On Bar Close? is off, the stack can still be using live-forming higher-timeframe values before the chart bar closes.
So keep these two ideas separate:
- chart-bar-close gating
- higher-timeframe confirmation mode
They are related, but they are not the same thing.
Alert families
This indicator exposes four useful alert families:
- slot regime alerts
- blended regime alerts
- blended threshold and zero-line events
- all-slot alignment alerts
Slot regime alerts
Per-slot alerts:
CVD 01 Is BullishCVD 01 Is BearishCVD 02 Is BullishCVD 02 Is BearishCVD 03 Is BullishCVD 03 Is Bearish
What they mean:
- bullish means that slot's CVD is above its Signal
- bearish means that slot's CVD is below its Signal
What they do well:
- tell you that one slot currently leans bullish or bearish
- help when you care about a specific timeframe or context slot
- support workflows where one slot matters more than the whole blend
What they do not do:
- tell you that the state is new
- confirm the move is strong enough to trade
- tell you whether the other slots agree
These are state alerts. They answer, "Is this condition true?" Not, "Did this condition just flip?"
Blended regime alerts
Blended regime alerts:
Blended CVD Is BullishBlended CVD Is BearishBlended CVD Regime Flip
The first two are state alerts. They tell you whether the blended CVD is above or below the blended Signal on the closed chart bar.
Blended CVD Regime Flip is different. It is a change alert. It tells you the blended regime has switched sides.
That distinction matters because these three alerts solve different jobs:
Blended CVD Is Bullishis useful when you want to know whether the blend currently leans bullishBlended CVD Is Bearishis useful when you want the bearish mirror of that conditionBlended CVD Regime Flipis useful when you care more about the transition than the continuing state
If you only want the moment of change, use the flip. If you want ongoing state awareness, use the state alerts.
Threshold and zero-line events
This build also exposes blended event alerts for threshold and zero-line changes:
Blended CVD Crossed Above ZeroBlended CVD Crossed Below ZeroBlended CVD OverboughtBlended CVD Oversold
These are event alerts, not persistent state alerts. They answer questions like:
- did the blend just move from negative to positive territory?
- did it just push above the chosen overbought line?
- did it just drop below the chosen oversold line?
Important boundary:
- the overbought alert only fires on a cross above the upper threshold
- the oversold alert only fires on a cross below the lower threshold
There are no slot-specific threshold alerts in this build, and there is no claim here that crossing a threshold creates a complete trade signal.
All-slot alignment alerts
Alignment alerts:
All CVD Slots BullishAll CVD Slots Bearish
These are useful when you want to know whether every enabled slot with a valid reading currently agrees on direction.
What makes them powerful:
- they compress the stack into one coordination check
- they reduce the need to watch each slot manually when agreement itself matters
What usually makes them vulnerable to misuse:
- a zero-weight slot still counts if it is enabled
- a hidden slot still counts if it is enabled
- agreement does not mean certainty
These alerts are best used as workflow prompts, not as permission slips.
Which alert to use for which job
That table is worth keeping in mind when the alert menu starts feeling crowded.
Common alert mistakes
Treating a state alert like a change alert
If you use Blended CVD Is Bullish but you really only wanted the moment the regime changed, the alert will answer a different question than the one you thought you asked.
Forgetting the whole stack shares the same higher-timeframe trust mode
If On Bar Close? is off, the alert conditions still wait for the chart bar to close, but the stack underneath them may still reflect live-forming higher-timeframe values.
Assuming hidden or zero-weight slots are gone
- hidden slots can still matter
- zero-weight slots can still affect slot alerts and all-slot alignment
Reading threshold events like completed trade logic
A blended overbought or oversold event tells you where the normalized blend just moved. It does not tell you whether that move fits the rest of your process.
A good verification drill
Run this once before you build habits around the alert set:
- Keep a simple same-symbol stack in confirmed mode.
- Watch one slot alert and one blended regime alert on the same chart.
- Note the difference between a continuing state and a flip event.
- Set one slot weight to
0. - Confirm that the slot can still matter for its own alerts and for all-slot alignment even after it leaves the blend.
- Hide one enabled slot and confirm that visual absence does not equal logical absence.
That exercise teaches more than memorizing the alert names ever will.
If you only have time for one verification pass, do steps 2 through 4. They usually reveal whether you are using the correct alert family before bad habits set in.
A healthy sentence to be able to say
"This alert is telling me that a defined condition exists or changed on the closed chart bar. It is not telling me the rest of my workflow is finished."
Visual placeholder: Alert setup reference showing slot regime alerts, blended regime alerts, threshold events, and all-slot alignment, with notes marking state-versus-event behavior and the chart-bar-close gating rule.