Alerts

Alerts are useful in this indicator when they bring you back to review. They become risky when they start feeling like commands.

Axiom Stoch Osc Lite exposes several alert surfaces because different traders want different kinds of reminders. Some want persistent state alerts. Some want event-style flips or threshold crossings. Some want full-stack alignment. This page helps you keep those categories separate.

If the slot ladder is still hard to explain, use fewer alert types, not more. Alert coverage is only helpful when you still know what the alert is reporting on.

Why this matters: alerts can lower monitoring load, but they can also hide confusion. A noisy workflow with too many alert classes usually feels informed before it is actually clear.

The first truth to keep in mind

All alerts in this script are evaluated on chart bar close.

That means:

• they do not fire intrabar
• state alerts can remain true across multiple closes
• flip and cross alerts are event-style conditions

If you want a fast mental model, think of the alert system as "check the stack at close" rather than "trade the moment the line twitches."

That framing helps keep the alert in its proper role: a return-to-chart tool, not a substitute for chart review.

Slot state alerts

Each slot exposes three alerts.

These alerts are useful when one slot has a specific job in your workflow and you do not want the blend to hide that local story.

If you are new to the stack, slot alerts are often the safest place to start because they force you to stay close to the actual structure of the design.

Blended regime alerts

The blended pair exposes three state-style alerts of its own.

These are useful when the blend is already a trustworthy summary of your slot design. If it is not, these alerts can make a weak summary feel stronger than it deserves.

Blended event alerts

These are event-style alerts, not persistent-state alerts.

These are useful when the midpoint or stretch zones matter to your review process. They are not enough on their own to settle whether a setup is actionable.

They are strongest when they send you back to a workflow you already trust. They are weakest when they become the workflow by themselves.

Alignment alerts

The script also exposes two full-stack alignment alerts.

Alignment is not the same thing as the blend.

That matters because:

• a zero-weight slot can still count toward alignment
• a hidden slot can still count toward alignment
• one heavily weighted slot can dominate the blend even when full alignment is missing

If you use alignment alerts, keep that distinction in view.

When alignment and blend disagree, do not ask which one is "right" first. Ask which question each one is answering.

What hidden visuals do not change

Two common assumptions are wrong here:

• Hiding a slot plot does not disable that slot's alerts.
• Hiding the blended visuals with Plot Blended K/D does not remove the blended alerts.

Visuals and alert logic are separate in this script.

A sensible way to choose alert types

Use alert classes based on the job you need:

• Use slot state alerts when one slot carries a distinct role.
• Use blended regime alerts when the weighted summary already makes sense to you.
• Use zero-line or threshold alerts when you want review prompts around midpoint or stretch movement.
• Use alignment alerts when agreement across enabled slots is part of your process.

If you find yourself turning on every alert class at once, that is usually a sign to simplify the workflow first.

A good first pass is one alert class, one reason for using it, and one chart check you will make after it fires.

Verification checklist

Before you rely on an alert, confirm:

1. which slot or summary it belongs to
2. whether the stack is confirmed or still forming
3. whether the relevant slot is enabled, hidden, or zero-weighted
4. whether the alert is state-style or event-style
5. what you still need to check on the chart after the alert arrives

That last point matters. An alert is a return-to-chart tool, not a replacement for chart review.

One practical standard helps here: before you create an alert, finish this sentence in plain English first.

"If this alert fires, I will come back to check ..."

If you cannot finish that sentence clearly, the alert probably does not belong in the workflow yet.

That is a trust check as much as a workflow check. If the post-alert action is fuzzy, the alert is probably asking the tool to do more than it earned.

Common mistakes

"The alert fired, so the setup is complete."

The alert only tells you one condition is true at chart close.

"If the blended pair is hidden, those alerts are off too."

They are not.

"Alignment means the blend and the slots all tell the same story."

Not always. Weighting and agreement can diverge.

"Threshold alerts mean reversal."

They mean blended K crossed a stretch line on this tool's own scale. Nothing more is settled by that alone.

What to remember when alerts start multiplying

Choose alerts for the job they actually do, then verify the chart state they point you back to.