Alerts

The alerts in Axiom DC CTX are deliberately narrow. They fire on computed conditions about the basis trend and about alignment across enabled slots. There are no channel-touch alerts, no breakout alerts, no squeeze alerts, and no "price crosses the basis" alerts. If you want those, you build them in another layer. This page covers everything that is here — what each alert means, what it does not mean, and how to use the four hidden count plots that are exposed specifically so you can reference them in custom alert message templates.

What you are actually subscribing to

When you create a TradingView alert on one of the conditions below, you are subscribing to a specific sentence: "as of the close of this chart bar, the following computed condition was true under the slot configuration in place at that moment." Three substitutions matter when you re-read that sentence later:

• This chart bar is whatever chart timeframe you attached the alert to. A 1-minute chart and a 5-minute chart will produce the same alert condition at different cadences and different resolutions.

• The slot configuration in place at that moment is whatever you had set when the alert fired — not what is set now. If you change timeframes or weights between alerts, your alert log becomes inconsistent with the configuration you see in the inputs dialog.

• The computed condition is either a basis-trend inequality (the basis is at/above or lower than it was Basis Trend Length: bars ago) or an alignment condition (every enabled slot is agreeing on trend direction). Nothing else.

A good alert-message template writes all three of those pieces into the notification so post-mortems are not guesswork.

The full alert inventory

All alerts in this indicator are gated at chart-bar close. A condition that is true mid-bar will not fire — the alert framework waits for the chart bar on which the condition held to close. Under the default On Bar Close? = ON posture, the HTF bar underneath a slot is also closed when the alert fires, so the value the alert evaluated against is confirmed. Under On Bar Close? = OFF, the chart bar closing does not mean the slot's HTF bar is closed; the value the alert fired against may have been a live HTF read.

Per-slot basis-trend alerts — twenty total

For each of the ten slots, two alerts exist:

• DC NN Basis Is Uptrend — fires when the slot's basis is at or above where it was Basis Trend Length: bars ago at the chart-bar close on which the alert triggers.

• DC NN Basis Is Downtrend — fires when the slot's basis is lower than it was Basis Trend Length: bars ago at the same close.

So: 10 slots × 2 directions = 20 alerts.

Interpreting a per-slot alert requires knowing three things about that slot:

1. Its TimeFrame: — what timeframe the basis was read at.

2. Its Basis Trend Length: — how far back the comparison was made.

3. Its On Bar Close? flag — whether the value that compared "at/above" or "lower" was a confirmed HTF read or a live one.

An alert message that does not reference those three fields will not, in post-mortem, tell you what the alert actually meant. Consider baking them into the alert message text.

Blended basis-trend alerts

Two alerts, on the blended channel:

• Blended DC Basis Is Uptrend — fires when the weighted majority of enabled slots' basis-trend states are rising.

• Blended DC Basis Is Downtrend — fires when the weighted majority are falling.

The rule behind these two is the weight-majority vote with a tie-to-uptrend convention. See Visuals & Logic and For the Geeks for the underlying logic. A reader who does not know the tie-to-uptrend rule cannot interpret the blended basis-trend alerts confidently; the rule matters specifically when you have even-weighted slots split on direction.

Alignment alerts

Two alerts, at the top of the inventory:

• All DC Slot Bases Uptrend — fires when every enabled slot with a non-na basis value is in the uptrend state.

• All DC Slot Bases Downtrend — fires when every enabled slot with a non-na basis value is in the downtrend state.

"Every enabled slot" is the phrase to read carefully. Hidden-plot slots are still enabled. A slot with Hide DC NN Plot ON still participates in the alignment check. A slot with Blended Weight: 0 is still enabled and still participates. The only way to exclude a slot from the alignment check is to disable it (Enable DC NN = off).

If the alignment alert is silent while three out of four slots agree, that is not an alert failure. That is the alert working — alignment requires every enabled slot to agree. Disagreement is the information, not a bug.

What an alert does and does not confirm

The distinction here is worth internalizing before you build anything on top of these alerts.

An alert does confirm:

• That on the close of the chart bar it fired on, the indicator's computed condition was true under the slot configuration you had in place at that moment.

• That the condition was evaluated at chart-bar close (not intrabar).

An alert does not confirm:

• That the HTF bar underneath the slot was closed. Under On Bar Close? = OFF, the alert may have evaluated against a live HTF bar, and the underlying value may still shift as that HTF bar closes. Under ON, the HTF value was confirmed.

• Any price direction. A basis-trend flip says the smoothed basis is at/above or lower than it was Basis Trend Length: bars ago — that is a computed relationship, not a market claim.

• Any setup, entry, intent, or trade. An alert is a notification about a state. It is not a call to do anything.

The two most common over-reads of these alerts:

• Treating a DC NN Basis Is Uptrend alert as a directional signal worth acting on. It is not a signal. It is a notification that a specific computed condition held at the close of a chart bar. The alert tells you the basis is at or above where it was Basis Trend Length: bars ago; it does not tell you whether the basis will keep rising, or whether price will follow.

• Treating a blended basis-trend alert as "the blend said up/down, so the stack agrees." The blended alert runs on a weight-majority vote. A 40-weight slot can outvote two 20-weight slots. Agreement in the blend is not agreement across slots; agreement across slots is what the alignment alerts cover.

Four hidden count plots for alert messages

The script exposes four plots that never draw on the chart but are available as values TradingView can substitute into alert message text:

• Active Basis Uptrend Count — the number of enabled slots whose basis is currently rising.

• Active Basis Downtrend Count — the number of enabled slots whose basis is currently falling.

• Active Above Basis Count — the number of enabled slots where the chart close is currently at or above that slot's basis.

• Active Below Basis Count — the number of enabled slots where the chart close is currently below that slot's basis.

These are handles, not alerts. They do not fire anything on their own. They exist so that when you attach one of the regular alerts above, you can write an alert message like:

DC 02 Basis Is Uptrend — {{plot("Active Basis Uptrend Count")}} of N slots voting up, {{plot("Active Above Basis Count")}} with chart close at/above basis.

(Check TradingView's current alert-message placeholder syntax; the indicator exposes the values but the templating rules are owned by the platform, not by this indicator. The placeholder text above is illustrative.)

Use cases:

• Context in alerts. When a per-slot alert fires, you also want to know whether the rest of the stack agrees. The uptrend/downtrend counts let your alert message carry that context without building a second alert to ask about the context.

• Position relative to basis. The above/below counts tell you where price sits across slots, independent of whether those slots' bases are rising or falling. This is a different question from basis trend, and the count plot is how you surface it.

• Sanity checks. If your alignment alert fires but the uptrend count is lower than the number of enabled slots you expected, you have a hidden slot enabled or a zero-weight slot you forgot about — the counts are a cheap way to catch that in post-mortem.

How to use these alerts without fooling yourself

Five habits go a long way:

1. Put the slot configuration in the alert message. Include TimeFrame:, Basis Trend Length:, and whether the slot was ON or OFF. Two weeks from now, you will not remember, and the alert log will be useless without those fields.

2. Match alerts to the slot posture. A trend alert on a slot running On Bar Close? = OFF is an alert that can fire mid-HTF-bar and then have the underlying value shift. That is a legitimate configuration if you know you are doing it; it is a foot-gun if you do not.

3. Use alignment alerts for confirmation, not for signaling. The alignment alert fires on a specific event — every enabled slot agreeing — and that event is strong context, not a trade call. The set of enabled slots you asked to agree was chosen by you; the alignment alert is telling you the setup you designed has lined up.

4. Do not hide a slot expecting it to stop counting. Hiding is visual only. Hidden slots vote in alignment. If you want a slot out of alignment, disable it.

5. Build your own signal layer, if you want a signal. This tool does not ship one. The alerts it does ship are narrow by design so that a reader who wants a signal builds the signal deliberately on top of honest conditions, rather than importing someone else's definition of "clean."

What is not here

Worth naming explicitly, so you do not spend time looking for things the indicator does not offer:

• No channel-touch alerts. Price reaching the upper or lower line does not fire anything.

• No breakout alerts. Price crossing outside the channel does not fire anything.

• No squeeze alerts. The blended or per-slot channel getting narrow does not fire anything.

• No "price crosses basis" alerts. Those events are visible on the chart; this indicator does not expose them to the alert framework.

If you want any of those, you wire them up in a separate indicator or a strategy. This one draws ranges and reports basis trend and alignment. That is the whole kit.

Why the alert surface is this narrow is worth a moment. Channel-touch and breakout alerts are the ones most commonly treated as entry signals, and the tool's design deliberately does not prefabricate those — both because the framing of a channel touch as a trade trigger assumes answers to questions (stop placement, confirmation filter, context at other timeframes) that only the reader can answer, and because a tool that looks like it is firing signals is a tool that gets read as signals, regardless of how many disclaimers are stapled to it. Basis-trend and alignment are narrow enough that they read unambiguously as state notifications. That narrowness is the feature.