MTF and Repainting

This page exists because the main trust boundary in Axiom MA Pro is not cosmetic. It is behavioral.

Multi-timeframe overlays can look clean on history and still behave differently live if the script is reading a higher-timeframe bar before that bar has closed. This indicator gives you a direct switch for that tradeoff on every slot. That is useful, but only if you treat the switch with the right amount of respect.

If you skip this page, it becomes much easier to build habits around chart behavior you did not actually mean to trust.

The two modes

On Bar Close? table below describes what each setting does.

If you only remember one thing from this page, make it this: Earlier is not the same as safer.

What changes, and what does not

When you turn On Bar Close? off:

• the slot can change while the higher-timeframe candle is still forming
• the slot's trend state can also change during that unfinished bar
• the finished historical picture can look calmer than the live path that created it

What does not change:

• the slot still has to respect the chart-timeframe compatibility rule
• the slot is still built from your chosen MA type, length, source, and symbol
• the alert system still waits for the chart bar to close

That last point matters more than many readers expect. A chart-bar-close alert can still reflect a slot that was built from unfinished higher-timeframe data.

Before you change the mode

Ask yourself two questions:

1. Do I want earlier context, or do I want cleaner history-to-live consistency?
2. Will I still remember which slot is live-forming once the chart starts looking normal again?

If the answer to the second question is no, stay with confirmed mode for now.

What repaint means here

In this indicator, repaint risk is not a vague accusation. It is a specific behavior.

When On Bar Close? is off:

• the slot can move before the higher-timeframe bar is finished
• the slot's trend state can move with it
• the final historical chart can hide that intrabar path

When On Bar Close? is on:

• the slot waits for the higher-timeframe bar to close
• the chart gives up some speed
• the tradeoff is usually worth it when you care about cleaner history-to-live consistency

A five-minute verification drill

Run this once before you build habits around live-forming mode.

1. Open a lower chart timeframe that can legally request a higher slot timeframe.
2. Keep one slot on a clearly higher timeframe than the chart.
3. Watch the slot with On Bar Close? enabled during a still-forming higher-timeframe candle.
4. Note that the slot stays anchored to the last closed higher-timeframe read.
5. Turn On Bar Close? off on that same slot.
6. Watch the same kind of unfinished higher-timeframe candle again.
7. Notice whether the slot value or trend state shifts before the higher-timeframe bar is finished.

What you are trying to learn is not whether one mode is morally better. You are trying to learn which tradeoff your workflow can actually carry without self-deception.

If you cannot see a meaningful difference yet, that is a good reason to keep the slot confirmed a little longer.

When confirmed mode is usually the better default

Stay with confirmed mode when:

• you are still learning the indicator
• you care about cleaner history-to-live consistency
• you are building alerts around higher-timeframe structure
• you want your stack to behave in a more reproducible way

When live-forming mode might be worth testing

Test live-forming mode when:

• you know exactly why earlier higher-timeframe feedback matters to your process
• you are prepared to verify the behavior in replay or live observation
• you are willing to accept that the chart can look less stable while the higher-timeframe bar is open

Even then, test it on one slot first.

Misuse to avoid

The common mistake is not turning confirmed mode off. The common mistake is turning it off and then continuing to read the chart as though nothing about trust changed.

That usually shows up as:

• treating the live-forming slot like hindsight-clean evidence
• forgetting that alerts still wait for chart-bar close
• using several live-forming slots at once before you know how one of them behaves

A healthy sentence to be able to say

"This slot is earlier because I turned confirmed mode off, so I trust it for early context only, not for hindsight-clean interpretation."

That kind of sentence keeps the tool in the right place. It turns uncertainty into a named condition instead of a hidden one.

Visual placeholder: Side-by-side chart captures of the same slot with On Bar Close? on and off during one unfinished higher-timeframe candle, with arrows marking where the live-forming mode can move before the close.