MTF and Repainting

This page explains the timing truth behind Axiom Stoch Osc Pro. That truth matters because the stack can look calm on the chart while the active slots do not all share the same trust posture. This page becomes non-optional as soon as you do any of these:

• mix timeframes in the stack
• let a live-forming slot into the blend
• create alerts from higher-timeframe slots
• compare another symbol on a different requested timeframe

If you only remember one thing from this page, remember this: each slot makes its own timing choice.

What "repainting" means here

In this indicator, the practical question is not "Is the whole tool pure or impure?" The practical question is: "For this slot, am I looking at the last settled requested-context value, or at a value that is still taking shape?" That is what On Bar Close? is deciding for each slot. So the most honest answer to "Does this repaint?" is:

• a confirmed slot is using the last settled requested-context values
• a live-forming slot can still change before its requested bar finishes
• one stack can contain both at the same time

That is why blanket slogans are not useful here.

Two clocks are always involved

Every multi-timeframe slot has to deal with two clocks:

• the chart bar you are currently viewing
• the requested bar for that slot's own timeframe

If the slot is also using another symbol, it is still living on that requested timeframe's clock for that symbol. The indicator has to choose whether to show:

• the last settled answer from the requested clock
• or the answer that is still forming on that requested clock

That choice lives inside each slot's On Bar Close? setting. If you remember only the label and not the tradeoff behind it, timing starts turning into borrowed confidence very quickly.

The hard legality rule

Before timing even becomes a trust question, the slot has to be legal. An enabled slot timeframe must stay at or above the chart timeframe. That means:

• a 5m slot can run on a 1m chart
• a 5m slot can run on a 5m chart
• a 5m slot cannot run on a 15m chart

If a slot timeframe is blank, it inherits the chart timeframe. This is a hard guard, not a style preference.

Confirmed mode versus live-forming mode

Confirmed mode

When On Bar Close? is on for a slot:

• that slot uses the last settled requested-context values
• the line is steadier
• history and live use are easier to compare cleanly
• you pay for that steadiness with delay

This is the right starting posture for most readers.

Live-forming mode

When On Bar Close? is off for a slot:

• that slot can use the current requested-context values while the requested bar is still building
• the line can move sooner
• the read is more responsive
• the tradeoff is that the slot can still change before that requested bar closes

Earlier is not the same thing as final.

What changes when the slot is higher timeframe

The higher the requested timeframe is relative to the chart, the easier it is to forget that a requested bar is still unfinished. On the chart, everything can look neat because you are seeing many lower chart bars step through the life of one higher-timeframe bar. That is where confusion usually starts:

• confirmed mode can feel later than expected
• live-forming mode can feel smarter than it really is
• a blended summary can compress the difference into one cleaner line

The solution is not to avoid higher-timeframe slots. The solution is to know which trust posture each slot is carrying.

Alerts and timing are related, but they are not the same thing

All alerts in this script are chart-bar-close gated. That means:

• a live-forming slot may move during the requested bar
• but the alert logic still evaluates on chart bar close

So a slot can be "early" in one sense and still not produce intrabar alerts. If you felt an alert came late, ask two separate questions: 1. what timing posture was the slot using 2. what cadence was the chart bar closing on Those are not interchangeable questions.

Mixed timing inside one stack

This is the biggest timing risk in the tool. Because timing is chosen per slot, one stack can contain:

• confirmed slot values
• live-forming slot values
• a blended pair built from both

That is not automatically wrong. It simply raises the burden on the reader. If you mix timing postures, you should still be able to answer:

• which active slots are confirmed
• which active slots are live-forming
• whether the blend is being influenced by the live-forming slots
• whether you would still trust the summary if the slot labels were hidden

If not, the stack is probably ahead of your explanation. That is the point where simplification is protective, not restrictive.

Alternate tickers follow the same timing rule

If a slot reads another symbol through Optional Ticker:, the timing question does not go away. That alternate-symbol slot still has:

• its own requested timeframe
• its own confirmed or live-forming posture
• its own session and liquidity quirks

So cross-symbol context can feel persuasive for two reasons at once:

• the symbol is different
• the timing posture may also be different

Keep those two differences separate in your head.

A practical replay test

If you want to understand this without reading code, run this test:

1. open a 1m or 5m chart
2. keep one slot on the chart symbol
3. set that slot timeframe to 15 or 60
4. duplicate the slot into another slot with the same settings
5. leave one copy with On Bar Close? on
6. turn the other copy off
7. watch both slots during a still-open requested bar

What to look for:

• the live-forming slot can move sooner
• the confirmed slot stays on the last settled read until the requested bar finishes
• the difference is easy to miss if you only stare at the blend

That one test teaches more than a vague repaint label ever will.

A safe timing progression

If you are still building trust in the tool, use this progression:

1. keep all active slots in confirmed mode
2. learn the baseline stack
3. test one duplicated slot in live-forming mode
4. decide whether the earlier movement actually helps your process
5. only then allow mixed timing in the real stack

This keeps the tool teachable while you are still learning it.

Common timing mistakes

Mistake 1: thinking the whole stack shares one posture

It does not. Timing is chosen per slot.

Mistake 2: calling confirmed mode "better"

Confirmed mode is steadier. It is not universally superior. It simply trades speed for a firmer trust boundary.

Mistake 3: calling live-forming mode "smarter"

Live-forming mode is earlier. It is not automatically more useful. Sometimes it only gives you more motion to narrate.

Mistake 4: forgetting that the blend inherits slot timing choices

The summary does not wash those choices away. It compresses them.

A quick timing checklist

Before you rely on a stack, ask:

1. Is every enabled slot legal on this chart?
2. Is each active slot confirmed or live-forming?
3. Are the blended contributors sharing one posture or mixing several?
4. Have I watched at least one confirmed-versus-live comparison on replay?

If the answer to the fourth question is no, do that before you let timing language become part of your conviction.

Where to go next

• Multi-Ticker Mixing: understand how timing and cross-symbol context can compound each other
• Alerts: match timing posture to realistic alert expectations
• For the Geeks: get the deeper mental model behind requested-context timing without code-level implementation detail

Visual placeholder: Side-by-side comparison of two identical higher-timeframe slots, one confirmed and one live-forming, with a note showing how the blend would inherit their differences if both stayed weighted.