Alerts

Alerts are most useful here when they reduce monitoring without pretending to think for you.

Axiom DC Pro gives you several alert families, but they do not all solve the same problem. Some tell you a condition exists right now. Others only tell you when a condition changed. If you mix those up, the alerts can feel noisy or strangely quiet for reasons that have nothing to do with the market.

If you are new to the indicator, start with one slot's Basis Change alert before you build anything more elaborate. The easiest way to overload this page is to enable several alert families before you know which question each one is answering for you.

First truth: every alert condition is chart-bar-close gated

The script only marks its alert conditions true on confirmed chart bars.

That gives the alert surface a cleaner rhythm, but it does not erase the higher-timeframe trust boundary. If On Bar Close? is off on a slot, that slot can still be built from a still-forming higher-timeframe bar even though the alert itself waits for the chart bar to close.

So keep both truths in view:

• alert conditions wait for the chart bar close
• slot values can still be live-forming higher-timeframe values if you chose that mode

Alert inventory at a glance

The current source snapshot exposes four alert groups:

• 30 per-slot basis alerts across DC 01 through DC 10
• 3 blended basis alerts
• 2 full-stack alignment alerts
• 4 blended cross alerts

That matters because it tells you what this build is actually prepared to watch for. It is broad, but it is not unlimited.

Alert families by job

State alerts versus change alerts

This is the distinction most readers need first.

State alerts answer:

• Is price above basis right now?
• Is price below basis right now?

Change alerts answer:

• Did the basis state just flip?
• Did price just cross the blended upper channel, lower channel, or basis?

If your workflow needs one clean notice when a condition changes, use change alerts.

If your workflow needs a check that a condition still holds at the close, state alerts may fit better.

The slot alerts

Per-slot alerts are best when one layer in the stack matters more than the others for a specific job.

Good uses:

• one slot defines your main directional frame
• one slot acts as a "do not fight this" filter
• one zero-weight diagnostic slot still matters for review, even though it no longer shapes the blend

What to verify before trusting a slot alert:

• the slot timeframe is valid on the current chart
• the slot is running on the symbol you think it is running on
• the slot is confirmed or live-forming in the mode you intended

The blended alerts

Blended alerts are useful when the summary layer is already well-designed.

They are usually better at reducing screen checks than at making decisions for you. A blended cross can be a strong review prompt. It is still downstream of several earlier choices:

• which slots are active
• which weights are non-zero
• whether any slot is remapped from another ticker
• whether any contributing slot is live-forming

If any of those choices are weak, the alert can still arrive on time and still deserve less trust.

Keep blended alerts out of the workflow until you can name the current contributors without opening the settings panel.

The alignment alerts

All DC Slots Above Basis and All DC Slots Below Basis can be helpful when you want to know whether the active basis lines agree.

They are not the same thing as:

• breakout confirmation
• trend quality
• a finished trade setup
• proof that the blend is well calibrated

Use alignment alerts as workflow prompts. They tell you that the stack is aligned, not that the trade is settled.

What is not in the alert surface

The current build does not expose per-slot upper-channel or lower-channel cross alerts.

That matters because many users assume a ten-slot indicator must expose every imaginable event. This one does not. The alert surface is focused on basis-state reading, blend-level crosses, and full-stack alignment.

Practical alert setups

Setup 1: monitor one decisive slot

Use:

• one slot's Basis Change alert

Why:

• you care about the flip, not the continuing state
• you do not want repeated attention on every close

Setup 2: monitor summary pressure

Use:

• Blended DC Crossed Above Upper Channel
• Blended DC Crossed Below Lower Channel

Why:

• you want event-driven reminders when price pushes beyond the current blended envelope

Check first:

• every contributing slot weight still reflects your intended workflow

Setup 3: monitor stack agreement

Use:

• All DC Slots Above Basis
• All DC Slots Below Basis

Why:

• you want to know when the whole active stack is leaning the same way

Do not forget:

• agreement can be real and still not be enough on its own

Three verification drills before you automate attention around this tool

1. Compare one slot's Is Above Basis alert with that same slot's Basis Change alert on the same chart.
2. Change one active slot's Blended Weight: to 0 and confirm the blended alerts are now speaking for a different contributor set.
3. Toggle one slot's On Bar Close? during an unfinished higher-timeframe bar and watch how your confidence in the same alert should change.

If those checks feel unnecessary, that is usually a sign the alert surface is carrying more certainty than it should.

What not to ask alerts to do

• do not ask them to decide whether the setup is good enough
• do not ask them to hide poor slot design
• do not ask them to compensate for unclear timing posture
• do not ask alignment to stand in for analysis

Used well, alerts reduce chart babysitting. Used carelessly, they only automate confusion.