MTF and Repainting

This page exists because the indicator's main trust boundary is behavioral, not visual.

Higher-timeframe overlays can look very calm in history and still behave differently live if they are allowed to follow a candle that has not closed yet. Axiom MA Lite gives you a direct switch for that tradeoff. It also applies that switch across the whole stack in this build.

If you understand that clearly, the indicator gets easier to trust. If you do not, the chart can still look clean while the trust boundary drifts out of sight.

The two timing modes

On Bar Close? | What the stack reads | What you gain | What you give up

If you only remember one line from this page, keep this one:

Earlier is not the same as settled.

That sentence matters because a lot of over-trust begins with a harmless-sounding idea: "I only wanted the stack to update sooner." Sometimes that is true. Sometimes it is also the moment the chart stops being read with the right kind of caution.

One control, whole stack

This is worth saying plainly:On Bar Close? is global in this version of the script.

That means:

• all three slots change timing posture together
• optional cross-ticker scaling follows the same timing posture
• you are not mixing confirmed and live-forming slot modes inside this lite build

That makes the tradeoff easier to reason about. It also means the switch deserves more attention than a minor toggle usually gets.

What repaint means here

In this manual, repaint does not mean "the indicator is dishonest." It means the stack can behave one way while a higher-timeframe candle is still forming and settle into a different finished state once that candle closes.

When On Bar Close? is off:

• slot values can move before the requested higher-timeframe candle closes
• slot trend states can also change before that close
• the final historical picture can look steadier than the live path that produced it

When On Bar Close? is on:

• the stack waits for confirmed higher-timeframe values
• the chart gives up some speed
• the historical picture lines up more cleanly with live expectations

What does not change when you turn it off

These points are easy to miss:

• chart-timeframe compatibility still matters
• alerts still wait for the chart bar to close
• the slot MA type, source, and length are still the same
• the blend still depends on active non-zero-weight slots

The timing switch changes trust posture. It does not turn the rest of the indicator into a different product.

When confirmed mode is the healthier default

Stay with confirmed mode when:

• you are still learning the tool
• you want the chart to be easier to verify in replay
• you are building alerts around the stack
• you want less room for hindsight confusion

This is why the default profile ships with On Bar Close? enabled.

If you are building first trust, confirmed mode is usually the right place to earn it.

When live-forming mode is worth testing

Test On Bar Close? = Off only when:

• you can explain why earlier higher-timeframe movement matters to your workflow
• you are prepared to verify the difference in replay or live observation
• you are willing to accept a weaker history-to-live trust boundary

Even then, it is usually better to test that on a simple stack before you make the rest of the layout more complicated.

Five-minute verification drill

Run this once. It pays for itself.

1. Open a 1m or 5m chart.
2. Leave one slot on a clearly higher timeframe such as 15 or 60.
3. Keep On Bar Close? enabled and watch the slot during an unfinished higher-timeframe candle.
4. Notice that the stack holds to the last confirmed higher-timeframe read.
5. Turn On Bar Close? off.
6. Watch the same kind of unfinished higher-timeframe candle again.
7. Notice whether the slot value or slot state moves before the higher-timeframe close.

What you are learning is not which mode is morally correct. You are learning which kind of evidence your workflow can actually carry without pretending.

The common misunderstanding

The usual mistake is not toggling the mode off.

The usual mistake is toggling it off and then continuing to read the chart as though the higher timeframe were already settled.

That often sounds like:

• "It only makes the stack faster."
• "The alerts still close on the bar, so it should be fine."
• "The chart looks clean, so it must be telling the same story."

None of those sentences keeps the trust boundary clear enough.

A healthier sentence to be able to say

"The stack is live-forming right now, so I am using it for earlier context, not for hindsight-clean certainty."

If you can say that and still want the mode, you are probably using it for the right reasons.

What to do next

• Go to Cross-Ticker Scaling if you plan to combine timing choices with another symbol.
• Go to Alerts if you want to understand how chart-bar-close alert confirmation fits with the timing switch.
• Go to For the Geeks if you want a deeper mental model of how the stack carries confirmed higher-timeframe values without exposing cloneable implementation detail.

Visual placeholder: Side-by-side chart sequence showing the same slot with On Bar Close? on and off during one unfinished higher-timeframe candle, with notes marking confirmed versus still-forming behavior.