Alerts

This page maps the alert surface to what the indicator is actually checking.

Written By AxiomCharts

Last updated About 2 hours ago

Alerts

This page maps the alert surface to what the indicator is actually checking.

The most important truth up front: alerts are useful here as review prompts, not as trade approval.

That matters because alerts reduce chart-watching load by design. They also arrive stripped of the surrounding context that made the state meaningful in the first place.

This indicator can watch slot state, blended state, threshold events, and full-slot alignment. Those are helpful summaries. They are not a replacement for checking what changed underneath them.

If you keep that boundary intact, alerts can save time. If you lose it, alerts can make a tidy state change feel more certain than it deserves.

The timing rule that governs every alert

All alert conditions in this build are checked on confirmed chart bars.

That means:

alerts do not fire mid-chart-bar
live-forming slot values can still exist before the alert checks them
alert timing and slot timing are related, but not identical

If you turned one slot's On Bar Close? off and expected instant alerts, this is the missing piece.

Slot alerts

Each enabled slot has three alert types:

MA Osc 0x Is Bullish
MA Osc 0x Is Bearish
MA Osc 0x Regime Flip

Where 0x is the slot number from 01 through 10.

Alert family	What it means	What to verify before trusting it
Slot bullish	That slot Fast is above that slot Slow on the confirmed chart bar	Which symbol, timeframe, and MA settings that slot is using
Slot bearish	That slot Fast is below that slot Slow on the confirmed chart bar	Whether the slot is still one you actually care about
Slot regime flip	That slot's bullish or bearish regime changed on the confirmed chart bar	Whether the flip matters in context or is only local noise

Slot alerts are good when one slot has a clear job, such as:

the fastest warning read in the stack
the slowest confirming read
the one outside symbol you are watching on purpose
a diagnostic slot that you kept out of the blend

Blended alerts

The blended surface exposes these alerts:

Blended MA Osc Is Bullish
Blended MA Osc Is Bearish
Blended MA Osc Regime Flip
Blended MA Osc Crossed Above Zero
Blended MA Osc Crossed Below Zero
Blended MA Osc Overbought
Blended MA Osc Oversold

Alert name	What it means	What to verify before trusting it
`Blended MA Osc Is Bullish`	Blended Fast is above Blended Slow	Which active slots are actually shaping the blend
`Blended MA Osc Is Bearish`	Blended Fast is below Blended Slow	Whether one heavier slot is quietly dominating the summary
`Blended MA Osc Regime Flip`	The blended bullish or bearish regime changed	Whether the slot stack agrees, or only the summary changed
`Blended MA Osc Crossed Above Zero`	Blended Fast crossed above the midpoint	Whether the move matters in your workflow or is only a reference-line event
`Blended MA Osc Crossed Below Zero`	Blended Fast crossed below the midpoint	Whether the move matters in your workflow or is only a reference-line event
`Blended MA Osc Overbought`	Blended Fast crossed above the configured overbought level	Whether that threshold means anything in this configuration instead of only by habit
`Blended MA Osc Oversold`	Blended Fast crossed below the configured oversold level	Whether that threshold means anything in this configuration instead of only by habit

Important detail: the overbought and oversold alerts watch blended Fast only. They do not require blended Fast to cross blended Slow at the same moment.

Alignment alerts

The stack also exposes:

All MA Osc Slots Bullish
All MA Osc Slots Bearish

These only fire when every enabled slot with valid data agrees.

Alignment is stricter than the blend.

That means a blended bullish state can exist while full bullish alignment does not.

Hidden plots, weight-zero slots, and why alerts can still fire

This is one of the easiest places to get surprised.

Hidden slot

If a slot is hidden but still enabled:

slot alerts can still fire
alignment can still include that slot
the blend can still include that slot if its weight is above 0

Weight-zero slot

If a slot stays enabled but its Blended Weight: is 0:

slot alerts can still fire
alignment can still include that slot
the blended pair stops listening to that slot

So if you get an alert from a slot you are not seeing in the blend, the first question is not "Did the script break?" The first question is "Did I hide the slot or remove it from the blend without disabling it?"

Mixed timing and what it means for alerts

One slot can be confirmed while another is live-forming.

That means:

a slot state can be based on a still-forming requested-context value
the alert still waits for the chart bar to confirm before it fires

If the alert feels late, the usual issue is not broken logic. The usual issue is expecting the slot's timing choice and the alert's timing choice to be the same thing.

A practical way to use the alert surfaces

Use the surfaces for different jobs instead of asking one alert to do everything.

If you are still learning the stack, start with one family only. Add the others after you can explain why the first one helped.

Slot alerts are best for local context

Use them when one slot has a specific role, such as:

fastest warning read
slower confirmation read
outside-market context read
zero-weight diagnostic read

Blended alerts are best for summary monitoring

Use them when you already trust the stack design and want one higher-level check before returning to the chart.

Alignment alerts are best for stricter stack agreement

Use them when your workflow truly cares about all enabled slots agreeing, not merely the weighted summary staying on one side.

What not to assume from an alert

Do not let any alert quietly become one of these:

a trade instruction
proof that all slots agree
proof that a live-forming slot is already settled
proof that mixed-symbol context is causal

The alert is telling you a state condition happened. You still have to decide what that state means in your method.

A clean first alert setup

If you are new to the indicator, start with this:

keep the three baseline slots confirmed
keep all active slots on the chart symbol
use one slot regime alert on the slot you trust most
use one blended regime alert
compare how often they agree before adding more

That is usually better than turning on every alert surface at once and creating a second overload problem.

Quick troubleshooting checks

If an alert feels wrong, ask these in order:

Is the slot still enabled?
Is the slot hidden instead of disabled?
Is the slot weight zero, which would remove it from the blend but not from slot alerts?
Is the slot confirmed or live-forming right now?
Am I expecting mid-bar behavior from a chart-bar-close alert?

Those five checks solve most confusion faster than re-reading the whole settings menu.

Before you build habits around alerts

You should be able to answer these without hesitation:

Which alert family matches the job you actually want: slot, blend, or alignment?
Would that alert still make sense if one active slot were hidden or weight-zero?
Am I using the alert to review context, or am I quietly asking it to approve a trade?

If the third answer starts sounding like "approve a trade," step back to the slot stack before you add more notifications.

Where to go next

Go to Visuals and Logic if you want the underlying chart states explained more carefully.
Go to MTF and Repainting if alert timing still feels slippery.
Go to Workflows if you want alert use tied to actual reading patterns instead of isolated conditions.

Visual placeholder: Alert setup example showing one slot regime alert, one blended regime alert, and one note explaining that alert checks happen on confirmed chart bars even when some slot values can move sooner.