MTF & Repainting

Most traders meeting Axiom MA CTX have been burned by a multi-timeframe indicator at least once. The pattern is the same each time. A higher-timeframe line looks clean in replay. It confirms the direction you were already leaning toward. You size up. The HTF bar finishes forming and the line that "confirmed" un-flips back the other way. The read that felt like a fact while you were acting on it was a live guess that had not aged yet. The indicator did not lie — it was computing correctly at every tick. It was reporting a value it had no business letting you trust as final, and nothing in the tool told you that was what you were looking at.

This page is about the posture Axiom MA CTX takes on that problem, what you are actually choosing when you change it, and the runtime guard that keeps you from silently asking the indicator to do something it should refuse to do.

Read this page before you touch On Bar Close? on any slot. The switch is small; what it governs is not.

What repainting actually is

A moving average is a function of its input bars. On your chart's native timeframe, that function is simple: the MA at bar N uses bars up through N, and when bar N closes, the MA at bar N is final.

A higher-timeframe MA is different. On a 1-minute chart showing a 60-minute MA, every 1-minute bar that sits inside the live 60-minute bar is looking at a 60-minute bar that is not yet closed. What the 60-minute MA "is right now" depends on whether you take the last confirmed 60-minute bar (the one before the live one) or the live 60-minute bar's value at the moment you ask.

The "confirmed" read steps once per HTF close and does not change again. It lags the live read by up to one HTF bar. The "live" read is current at the moment you ask, but it can un-flip, slide, and settle differently as the live HTF bar continues to form.

Neither read is wrong as a computation. Both are wrong in specific use cases. An indicator that does not let you pick between them — or that silently reports the live read as if it were confirmed — is the one that has burned most of this manual's audience.

What Axiom MA CTX offers

Every slot carries its own On Bar Close? switch in its power-user group.

• ON (shipped default). The slot reports the last confirmed value of its timeframe. The line steps forward when the slot's HTF closes a bar. Once a value is plotted on a given HTF bar, it does not redraw. This is the slower, honest read.

• OFF. The slot reports the live value of its timeframe. The line can move inside the live HTF bar and can un-flip until the HTF bar closes. This is the faster, repaint-exposed read.

The switch is per slot. There is no master toggle. A reader who flips Slot 01 OFF and expects Slots 02 and 03 to follow will be wrong. If you want every slot OFF you have to flip ten switches, each one deliberately, one at a time.

What ON costs you

• Latency. Under ON, a trend flip that actually happened inside the current HTF bar does not register until the HTF bar closes. On a 60-minute slot, worst case is almost a full hour of lag before you see it.

• A sense that the tool is slow. It is not slow. It is refusing to give you a live-bar read and call it confirmed.

What OFF costs you

• Repaint exposure. A slot whose On Bar Close? is OFF can show an uptrend read at 12:17 and a downtrend read at 12:42 of the same 60-minute bar, and be honest both times — because each read is the live HTF value at the moment of reading. If you wired a per-slot trend alert on that slot, and the chart bar on which the uptrend condition held was confirmed, the alert fired. The HTF bar that produced the read is still forming.

• A temptation to call a live-bar read "confirmed." Do not. A confirmed chart bar is not a confirmed HTF bar. Alerts are gated by chart-bar close, not by HTF close. See Alerts for the full consequence.

When OFF is actually appropriate

OFF is a legitimate posture — but only for readers who want the live HTF value on purpose and will treat it as live. Examples of legitimate OFF:

• You are managing an open position and want to see the HTF MA drifting inside the current HTF bar, because that drift is exactly the early warning you are watching for. You will still wait for HTF close before treating the direction as settled; OFF gives you the heads-up in the interim.

• A specific slot in your stack is deliberately a live-context read — maybe a cross-ticker slot used for session-peek behaviour — and you accept its repaint as the price of seeing what the related market is doing right now rather than an hour ago.

• You are doing controlled research on how the live HTF read behaves on this symbol and this timeframe, so you can decide whether you trust OFF enough to use it in future configurations.

OFF is not appropriate for the slot you would actually act on. It is not appropriate as a global switch flipped across every slot on the theory that it makes the indicator feel snappier — all that posture buys is the right to remember different readings from the same bar. It is not appropriate on a scalping workflow that cannot hold an HTF read long enough for the HTF bar to close, because you will be acting on values that vanish while you wait for confirmation the workflow structurally cannot receive.

A useful litmus test before flipping a slot OFF: can you say out loud what you will do differently with a live read than with a confirmed read, and would you still flip OFF if you wrote that reason down and had to defend it to yourself an hour later? If yes, flip the slot. If not, leave it.

Verifying On Bar Close? on your own chart

You do not have to trust the description. Run the check yourself.

1. Load the indicator on a 1-minute chart. Leave Slots 01, 02, 03 at their defaults.

2. Open Slot 01's MA 01 PU group. Confirm On Bar Close? is ON.

3. Watch the teal Slot 01 line for one full 5-minute cycle (five 1-minute bars or so — pick a period when the symbol is actually moving so you can see the line do something). The teal line should be motionless between 5-minute closes. At a 5-minute close it steps to a new value. Repeat once more for certainty.

4. Flip On Bar Close? OFF. Watch another 5-minute cycle. The teal line now updates inside the 5-minute bar, can walk up and down, and can look very different at 1-minute intervals inside the same 5-minute bar.

5. Flip On Bar Close? back ON. Watch one more cycle. The step-only behaviour is back.

This is the whole distinction. If you remember one thing from this page, remember what the line looks like under ON versus OFF in that exercise.

Screenshot placeholder — "Side-by-side comparison of On Bar Close? ON versus OFF on Slot 01. Left panel: ON, the teal line steps exactly at each 5-minute close and is still between closes. Right panel: OFF, the teal line drifts inside each 5-minute bar and can un-flip colour before the bar closes." To be captured against a live chart before promotion.

The slot-timeframe guard

Every slot's TimeFrame: must be greater than or equal to the chart's own timeframe. A slot pointed at a timeframe below the chart raises a runtime error. The indicator stops rendering and TradingView displays a message naming the offending slot:

MA 01 timeframe cannot be lower than the chart timeframe.

This is a feature, not a defect. A slot requesting a below-chart timeframe is asking the indicator to compute an MA on a granularity the chart does not show, then to draw it on bars that do not correspond to that granularity. The resulting line would be lying about what it represents. The tool refuses rather than pretend.

Fix the guard by doing exactly one of the following:

• Set the slot's TimeFrame: to empty. The slot computes on the chart timeframe, whatever that is.

• Set the slot's TimeFrame: to the chart timeframe exactly. Same effect as empty for the current chart; will re-break if you switch to a higher-timeframe chart.

• Set the slot's TimeFrame: to a value above the chart timeframe.

The guard is per-slot. A single offending slot blanks the whole indicator. If the chart is blank and the status bar names a slot, start with that slot and do not assume the others are misconfigured too.

Screenshot placeholder — "Runtime-error state: the chart pane is clear of the Axiom MA CTX lines and a TradingView status-bar message reads 'MA 01 timeframe cannot be lower than the chart timeframe.' Intended to be captured by setting Slot 01's TimeFrame to '1' on a 5-minute chart." To be captured before promotion.

Cross-ticker slots inherit the repaint posture

When a slot has an Optional Ticker: set, the cross-ticker scaling factor is computed at the slot's timeframe under the slot's own On Bar Close? posture. Same posture as the MA itself.

Practically: if your cross-ticker slot is on OFF, the scale factor is live too. As the current HTF bar forms, both the alternate symbol's MA and the scale factor can drift. The slot's line can move for two independent reasons inside the same HTF bar — shape change and scale change — and both are live.

Under ON, the scale factor uses the previous confirmed HTF close ratio when that ratio is available. Same lag as the MA. Same honesty. If the two symbols are on different sessions, the scale factor can also be stale in a different sense: one symbol's HTF bar may have closed long ago while the other has not. The scaling still runs with the best data available; it can be stale nonetheless. If the ratio cannot be computed, the slot can fall back to the raw requested MA value, so cross-ticker lines should be checked visually before they are trusted or weighted into the blend.

See For the Geeks for the mental model of the cross-ticker scaling, and Limitations & Trust Boundaries for the trust-boundary treatment.

What a confirmed-bar alert does and does not prove

Every alert in Axiom MA CTX is gated by the chart bar's confirmed state. That is a different gate from the slot's On Bar Close? posture. Both can be true; both can disagree.

• A per-slot trend alert fires at the close of the chart bar on which the condition held. If that slot's On Bar Close? is ON, the condition used a confirmed HTF value and is as settled as a slot of that configuration can be.

• If that slot's On Bar Close? is OFF, the condition used the live HTF value at the moment of chart-bar close. The condition held on the chart bar; the HTF bar behind it can still redraw.

• Either way, the alert does not confirm that the slot's HTF bar is closed. Chart-bar-confirmed is the weaker of the two gates.

If you want your alerts to never fire on a live HTF read, keep every slot whose alerts you care about on ON. There is no separate alert-gating switch. The slot's posture is the alert's posture.

A summary worth copying into your own notes

• Shipped default is ON on every slot, because ON is the read that does not redraw.

• OFF is legitimate, per slot, with clear eyes about what the posture gives up. It is never a blanket upgrade.

• Chart-bar-confirmed is not HTF-bar-confirmed. Alerts are gated by the weaker of the two. Your confidence in an alert should be gated by the stronger one.

• The timeframe guard is a feature. It is the tool refusing to compute a configuration that would have to lie to render.

• Cross-ticker slots inherit the slot's On Bar Close? posture for both the alternate MA and the scale factor. One switch, two live dependencies.

If you are about to flip a slot from ON to OFF, write down the specific reason you expect the live read to serve you better than the confirmed one on that slot. If you cannot write that sentence, flip the slot back. This is how the tool stays an instrument rather than a preference.