Each timeframe votes independently, and the theory says they shouldn't.

The theory's shape

Nesting means lower timeframes are components, not witnesses.

In a strict reading, a five-minute structure is not independent evidence about an hourly structure — it is a part of it. The hourly impulse is built out of the lower-degree legs, so asking whether the five-minute agrees with the hourly is close to asking whether a paragraph agrees with the chapter containing it. Under nesting, most of the interesting configurations are ones where lower degrees are supposed to disagree: a healthy hourly impulse contains a five-minute correction at every pullback. Agreement across all degrees is not the strong case in the theory. It is the case where a move is late.

The read's shape

Flat rows, one classification each, and a simple tally.

The HUD makes no attempt to model containment. Every enabled timeframe gets a row, each row gets a phase, and the convergence figure is a count of rows sharing a side. There is no weighting by degree, no requirement that faster rows be consistent with slower ones, and no arithmetic connecting a row to the row above it. Structurally this is a voting system applied to a hierarchy, and it is a substitution rather than an approximation — the flat tally is not a computationally cheaper version of the nested analysis, it is a different question with a different answer.

Why the substitution is defensible

The nested question needs an answer the tool cannot get.

Computing containment requires knowing the degree of each structure, and degree is exactly the judgment the reduction refused to make. There is no way to be rigorous about nesting without first being rigorous about labelling, and once labelling is in scope every disagreement between two analysts is back in the output. The flat tally is what remains available after that refusal. It is a weaker instrument on paper and a usable one in practice, and the honest framing is that the tool answers an adjacent question well rather than the original question badly.

What the flat read buys

A number that means the same thing every time it appears.

Because no row is weighted and no relationship is modelled, the convergence figure has an unusually stable meaning: it is the number of enabled timeframes currently classified on the dominant side, and nothing else. That stability is what makes a threshold legal. An operator can commit to a minimum before the week starts and know the commitment will not quietly shift depending on which timeframes happened to be involved. A degree-weighted score would produce a more theoretically satisfying number that no one could set a threshold against, because the same value would mean different things on different days.

The cost, stated plainly

The configuration the theory likes best reads as weak here.

The flat tally systematically underrates the early continuation setup — higher timeframes impulsing while lower ones finish a pullback — because it counts that as disagreement. This is the tool's known blind spot, and it is not corrected internally. It is corrected by the operator, who reads the rows rather than only the total, and by the second beat of the workflow, where the price overlay resolves where the structure is actually turning. An operator who trades the convergence number alone will pass on some of the best continuation entries, and the number will not warn them.

• Higher-timeframe impulse over lower-timeframe correction is scored as a mixed book.
• The total is a summary; the row pattern carries information the total drops.
• Timeframe selection is a real decision — enabling more rows changes what the same threshold means.

The key idea

Know which question your instrument is answering, especially when it borrows a name.

The tool carries an Elliott label and does not implement Elliott's structure. That is not a criticism of it, but it is something an operator has to hold, because the gap explains every case where the read and a careful manual count disagree. When they diverge, neither is malfunctioning — they are answering different questions, and the operator has to know which answer the trading plan committed to. The plan committed to the tally, with a threshold, recorded before the trade. The count remains available as judgment, and judgment is exactly what the governance layer downstream is built to constrain.