Alerts

The alert surface in Axiom CVD Osc Pro is most useful when it reduces screen-watching without turning the stack into a command system. Done well, alerts let you stop staring at the pane. Done badly, they let the pane answer a question you never clearly asked.

Start with the question first. The key distinction to learn is not only 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.

The first rule

Every alert condition in this build is evaluated on the close of the chart bar.

That is good for discipline. It does not erase the higher-timeframe trust boundary inside the stack.

If one slot has On Bar Close? off, that slot can still be using live-forming higher-timeframe values even though the alert condition itself only becomes true on the closed chart bar.

Keep those two ideas separate:

• chart-bar-close gating
• slot-level higher-timeframe confirmation posture

They work together. They are not the same thing.

Alert families

This indicator exposes four practical alert families:

1. slot regime alerts
2. blended regime alerts
3. blended threshold and zero-line events
4. all-slot alignment alerts

Slot regime alerts

Per-slot alerts:

• CVD 01 Is Bullish through CVD 10 Is Bullish
• CVD 01 Is Bearish through CVD 10 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 whether one specific slot currently leans bullish or bearish
• help when one slot matters more than the whole blend
• support workflows where a diagnostic slot still deserves its own alert coverage

What they do not do:

• tell you that the state is new
• tell you that the other slots agree
• tell you that the slot belongs in the blend

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 Bullish
• Blended CVD Is Bearish
• Blended CVD Regime Flip

The first two are state alerts. They tell you whether the blended CVD currently sits 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 switched sides.

Those jobs are not interchangeable:

• use the state alerts when you care about the continuing condition
• use the flip alert when you care about the transition itself

Threshold and zero-line events

This build also exposes blended event alerts for key level changes:

• Blended CVD Crossed Above Zero
• Blended CVD Crossed Below Zero
• Blended CVD Overbought
• Blended CVD Oversold

These are event alerts, not persistent states.

They answer questions like:

• did the blend just move from negative to positive territory?
• did it just move above the chosen overbought line?
• did it just drop below the chosen oversold line?

Important boundary:

• overbought only fires on the cross above the upper threshold
• oversold only fires on the cross below the lower threshold

There are no slot-specific threshold alerts in this build, and these events are not a substitute for your broader workflow.

All-slot alignment alerts

Alignment alerts:

• All CVD Slots Bullish
• All CVD Slots Bearish

These alerts mean every enabled slot with a valid value currently agrees on direction.

That sounds strong, so the boundaries matter:

• a hidden slot still counts if it is enabled
• a zero-weight slot still counts if it is enabled
• an alternate-ticker slot still counts if it is enabled
• a live-forming slot still counts if it is enabled

So "all slots agree" does not mean:

• all slots are visible
• all slots are blended
• all slots share one trust posture
• the trade is approved

It only means the active slot states currently line up.

Which alert to use for which job

That table is worth checking before you build alert habits.

Common alert mistakes

Treating a state alert like a change alert

If you use Blended CVD Is Bullish but you only wanted the moment of transition, you asked the stack a different question than the one you meant.

Forgetting that slots can carry different timing assumptions

One slot can be confirmed while another is live-forming. The alert waits for the chart bar to close, but the stack under that alert may still be mixed.

Assuming hidden or zero-weight slots are gone

They are not.

• hidden slots can still matter
• zero-weight slots can still matter to slot alerts and all-slot alignment

Reading threshold events like completed trade logic

A blended overbought or oversold event tells you where the normalized summary moved. It does not tell you whether the rest of your workflow is finished.

A good verification drill

Run this once before you build habits around the alert set:

1. Keep a restrained same-symbol stack in confirmed mode.
2. Watch one slot alert and one blended regime alert on the same chart.
3. Note the difference between a continuing state and a flip event.
4. Set one slot weight to 0.
5. Confirm that the slot still matters for its own alerts and for all-slot alignment.
6. Hide one enabled slot and confirm that visual absence does not equal logical absence.
7. Turn one slot to live-forming mode and compare how much more caution that slot deserves even though the alert timing still waits for the chart bar.

That exercise teaches more than memorizing the alert names.

Keep this sentence nearby when you build alerts

"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."

If that sentence stops fitting the way you are using an alert, the alert is probably carrying too much weight in your process.

Visual placeholder: Alert reference showing slot regime alerts, blended regime alerts, threshold events, and all-slot alignment, with notes marking state-versus-event behavior and chart-bar-close gating.