Alerts

The CTX trim ships twenty-four alert conditions. All of them are state observations on confirmed bars. None of them is a trade trigger, and reading them as triggers is the misuse pattern the rest of this page is trying to prevent. This page lists what each condition reports, what it does not report, and the shape of the state-transition alerts that deliberately do not exist in this script so you do not build a workflow that depends on them.

The one gating rule

Every alert in this script is gated by barstate.isconfirmed. A bar has to close before any of these fire. That means:

• There are no intrabar alerts from this indicator, regardless of the per-slot On Bar Close? setting. The repaint switch on a slot affects how that slot reads its higher-timeframe value during the forming bar. It does not change when alerts fire.

• An alert's timestamp is the close of a bar. The state the alert reports is the state that existed at that close, not the state that existed while the bar was forming.

• A "just flipped" feel you may experience when an alert fires is a property of the bar having just closed, not of the alert watching for a transition. See the "state versus transition" section below.

The twenty per-slot conditions

For each slot from 01 to 10, two conditions exist:

• MA Osc 0N Is Bullish — fires on the close of a bar when the slot is enabled and its fast value is above its slow value at that close.

• MA Osc 0N Is Bearish — fires on the close of a bar when the slot is enabled and its fast value is below its slow value at that close.

What they confirm:

• That the slot was enabled at the bar close.

• That on the closed bar, the slot's fast-vs-slow relationship matched the reported direction.

What they do not confirm:

• Direction of price on the chart instrument (unless the slot is reading the chart instrument).

• Any transition. The state may have held for many bars before the alert fired. The alert does not know.

• Anything about intrabar price action between the previous close and the current one.

• That the slot is meaningful for the instrument. A slot configured with a mismatched timeframe or a cross-asset ticker will still fire these alerts truthfully, and the truth it reports is about the slot as configured, not about the chart.

The blend and alignment conditions

Four conditions sit above the per-slot set:

• Blended MA Osc Is Bullish — the blend's fast is above its slow at bar close.

• Blended MA Osc Is Bearish — the blend's fast is below its slow at bar close.

• All MA Osc Slots Bullish — every enabled slot is bullish at bar close.

• All MA Osc Slots Bearish — every enabled slot is bearish at bar close.

The blend conditions are the closest thing to a single "what is the pane saying" alert this script offers. They read the thicker line pair directly. They inherit the bar-close gating of the per-slot conditions.

The alignment conditions are the ones most likely to be misread, and they deserve the most caution:

• Alignment is a statement about your configuration, not the market. If your enabled slots share source, length families, and overlapping timeframes, alignment will be common in trendy history and the alerts will fire frequently. That frequency is telling you about the configuration, not about broad market agreement.

• Alignment is not a test of independence. The tool does not ask whether the slots carry distinct information. It only asks whether they currently agree. Those are different questions, and the alignment alert does not answer the one you probably care about.

• The alignment alerts ignore disabled slots. "All MA Osc Slots Bullish" means "all enabled slots," not "all ten slots." A configuration with only two slots enabled can fire this alert every bar for long stretches.

• If you route an alignment alert to an external service — a phone push, a webhook, a Discord channel — remember that the label in the message is the name of a condition inside your configuration, not a label the market has earned. The message still reads like "everything agrees." It does not measure that.

State versus transition — what does not exist

The script does not ship cross-event alerts. There are no conditions for:

• A slot transitioning from bearish to bullish or the reverse on a specific bar.

• The blend crossing above or below the 30/50/70 reference lines.

• A slot value crossing its own slow line on a specific bar.

• The alignment state flipping.

If you need a transition alert, there are two honest paths. First, you can layer one externally — for example, an alert service that only notifies on the first fire after a period of silence. Second, you can use the slot and blend state alerts and reason about transitions yourself by comparing the last fire timestamp to the current one. Both paths put the logic outside the script, which is on purpose — the script's job is to report state truthfully, and the transition definition is a choice that belongs to the user.

Reading an alert after it fires

When an alert arrives, the minimum audit is:

1. Note the timestamp. That is the close of a bar.

2. Reopen the chart at that timestamp. Look at the slot(s) the alert refers to.

3. Confirm the reported relationship held on that bar.

4. Check which slots were enabled and how they were weighted. The configuration you had running is what the alert measured.

If the alert is an alignment alert, add one more step:

1. Ask whether your slots are independent enough to interpret "all bullish" as anything more than "my current configuration rewards alignment." If two slots are basically duplicates, the alignment is a duplicated observation, not a consensus.

A short alert inventory

Honest use of the alert feed

A reasonable posture:

• Use the per-slot alerts to monitor specific slots you have reason to watch. A cross-asset slot tied to a macro reference, for example, can alert you to stretch on the ticker without pulling your attention from the chart.

• Use the blend alerts to monitor the headline of the pane when you cannot be on the chart.

• Treat the alignment alerts as the loudest and most easily misread. They will feel confirmatory. The confirmation is inside your configuration, not across the market.

An unreasonable posture:

• Routing alignment alerts directly into order execution.

• Treating "bullish state" alerts as entries. Every per-slot alert is a state report, not a trigger.

• Assuming silence is information. The alerts report when their state condition is true on a closed bar. Silence can mean the state was false, that your slot was disabled, or that the bar has not closed yet.

Where to go next

• What the alerts are referring to in visual terms: Visuals & Logic.

• Why the alignment alerts deserve the most care: Limitations & Trust Boundaries.

• When an alert fires and the pane does not look like you expected: Troubleshooting.