02 · Confirmation

Bar-close confirmation and repainting

“Confirmed at the close” is a useful promise only when its limits are stated alongside it.

The open bar is still forming.

Price, range, and volume can change while a bar is open. A reading built from that bar can change with them. Watching the live calculation is different from reading the decision after confirmation.

MIZAN ships with bar-close confirmation enabled. Keep it enabled when you want the engine’s decision to wait for the completed bar.

What the close settles.

The engine confirms its decision against the data and settings available at the close. A provisional live-bar state should not be treated as a confirmed setup.

When reviewing a recording, follow the bar through its close. Read the score, blocking reason, and risk geometry together instead of judging a single frame taken while the candle was still moving.

Why a later calculation can differ.

A chart reload reconstructs calculations from the history available to it. Changing the loaded bars, symbol, session, timeframe, or settings changes the calculation’s context.

Footprint data has a further boundary: TradingView classifies volume from intrabar price movement, and the available historical intrabar granularity can change. A historical footprint read can therefore be recalculated.

A blanket claim that nothing can ever change would erase that distinction. The useful questions are when a decision confirms, which source fed it, and what changed between two comparisons.

Compare like with like.

Chart context

Match the symbol, timeframe, session, timezone, and loaded history.

Engine context

Match the build, preset, confirmation settings, and active data tier.

For Institutional, read the data tier on the dashboard. For ledger comparisons, keep the resolution window and intrabar-resolution setting consistent as well.

The ledger accounting guide explains how those inputs affect recorded outcomes. The troubleshooting section covers practical checks.

Read the platform boundary.

TradingView’s documentation distinguishes live-bar changes from other forms of historical recalculation. Its footprint reference explains how the underlying intrabar data is classified and requested.

TradingView: repainting ↗
TradingView: footprint data ↗

← All documentation · Operator’s Guide →