MTF and Repainting

Timeframe behavior is where this indicator most often looks simpler than it really is. Axiom CVD Osc Pro can mix multiple higher-timeframe slots in one pane, and each slot can carry its own confirmation posture. This page is here so the clean look does not outrun the timing truth underneath it. If you only remember one warning from this page, keep this one: a chart-bar-close alert does not mean every slot inside the stack was confirmed.

The hard geometry rules

Three rules are non-negotiable:

1. an enabled slot cannot run below the chart timeframe
2. Lower TF Precision: must stay below that slot's timeframe
3. Window: cannot be smaller than that slot's timeframe

If one of those relationships breaks, the script throws a runtime error. That is not the indicator being temperamental. It is the script protecting the stack from invalid geometry.

What On Bar Close? means

Each slot has its own On Bar Close? setting.

When it is on

The slot waits for the last confirmed higher-timeframe reading. This is the steadier choice when you want:

• history and live use to line up more cleanly
• fewer surprises from unfinished higher-timeframe bars
• a clearer trust posture across the stack

When it is off

The slot can move with the still-forming higher-timeframe bar. This can be useful when you want:

• earlier motion
• one exploratory slot that reacts before the higher timeframe closes

It also means that slot can shift during the unfinished higher-timeframe candle. That is the repaint tradeoff for that slot.

Why this matters more in Pro

In the Lite version, confirmation is one shared decision. In Pro, each slot can choose its own confirmation posture. That flexibility is real. So is the risk:

• one slot can be settled
• another can be live-forming
• both can feed the same blend
• all-slot alignment can still compress them into one apparent agreement

The pane will not warn you every time you build that mixed posture. You have to keep track of it on purpose.

Session and Rolling are different timing jobs

Session and Rolling are not repaint settings, but they do change how the slot behaves through time.

Session

• the slot builds its active-window story from a reset anchor
• visible session slots draw reset markers when that anchor changes

Rolling

• the slot keeps a sliding-duration window instead
• rolling slots do not print reset markers because there is no one anchor event to draw

So even two confirmed slots can feel different through time if one is anchored and the other is rolling.

Chart-bar-close alerts do not erase slot timing differences

All alert conditions in this build are checked on the close of the chart bar. That does not mean the whole stack is confirmed. If one slot is live-forming, the alert can still be summarizing a mixed stack on the closed chart bar. The chart-bar-close gate protects one layer of timing. It does not flatten the higher-timeframe trust choices underneath it.

A replay drill worth running

If you want to understand this page without touching code, run this once:

1. Keep one slot on the chart symbol in confirmed mode.
2. Duplicate that slot idea on another slot.
3. Turn On Bar Close? off on the duplicate.
4. Keep everything else matched.
5. Watch both slots through an unfinished higher-timeframe candle.
6. Then compare the finished higher-timeframe close.

What you are looking for:

• how much sooner the live-forming slot moves
• how much that earlier motion changes before the higher timeframe settles
• whether the earlier slot is truly helping your workflow or only making the pane feel more active

A safe first rule

Keep the active weighted slots confirmed until you can explain, from experience, what you are giving up when one slot goes live-forming. That is not about fear. It is about earning the faster read instead of borrowing it.

If you do use mixed timing

Do it on purpose:

1. keep the mixed slot visible
2. give it one explicit job
3. keep its blend influence modest at first
4. compare it against a confirmed counterpart
5. do not let all-slot agreement talk you into forgetting the timing mix

Mixed timing can be useful. It should never be accidental.

What usually causes confusion here

The most common misunderstandings are:

• chart-bar-close alerts being mistaken for full-stack confirmation
• a clean blend being mistaken for a clean timing posture
• live-forming motion being treated like free speed
• invalid timeframe geometry being treated like a script failure

If one of those is happening, go back to a smaller confirmed stack before you keep tuning.

Keep this timing rule in view

MTF behavior in this indicator is not only about higher timeframes. It is about whether each slot is settled, what window it is built from, and whether those choices still make sense once they are blended together. That is the part worth verifying before you trust the neatest-looking moments in the pane.

Visual placeholder: Side-by-side comparison of two matched slots where one is confirmed and the other is live-forming, with notes marking how the two diverge during an unfinished higher-timeframe candle.