What a value-area rotation actually claims

Value-area edges are among the most-watched levels in futures, and among the least examined. This is what the rotation reading asserts, where the assertion comes from, and what a tool can honestly show about it.

Where the value area comes from

The value area is the price range containing a chosen share of a session’s traded volume — conventionally about 70%, expanded outward from the point of control until that share is covered. The construction comes out of Market Profile, in Steidlmayer and Koy’s Markets and Market Logic and in James Dalton’s Mind Over Markets.

Two things follow from the construction itself, before any interpretation is added:

• It is descriptive. The value area says where trade concentrated. It is arithmetic on completed transactions, not a forecast.
• The 70% is a convention, not a constant. Nothing in the auction produces that number. It is a choice about how much of the distribution to call “value”, and a different share draws different edges.

Anyone quoting a value-area level is quoting the output of those two choices — the session boundary and the percentage. Change either and the level moves.

What a rotation claims

A rotation, in the ordinary usage, is price leaving the value area, being rejected, and returning inside. The claim attached to it is roughly: the market tested a price the previous session had already judged, found no acceptance there, and came back.

It is worth separating that into the part that is observed and the part that is inferred.

• Observed: price traded outside the edge and then traded back inside. That is a fact about a price path.
• Inferred: that the excursion failed because the area beyond was not accepted. That is an interpretation, and other explanations fit the same path — a scheduled release, a large order finishing, or nothing in particular.

The distinction matters because the observed part is cheap to detect and the inferred part is what people trade. Most of the disagreement about whether value-area levels “work” is really disagreement about that second step.

Why the previous session, and why the edges

Two practical reasons the previous session gets used rather than the developing one:

• It is finished. A developing value area moves as the session builds. An edge quoted at 10:00 may not be the edge at 14:00, which makes any record of “what happened at the edge” ambiguous about which edge it means.
• Both sides can see it. Whatever one believes about self-fulfilling levels, the previous session high, low, and value-area boundaries are computed the same way by most platforms, so a large number of participants are looking at approximately the same numbers.

The edges rather than the middle, because the middle is where trade already concentrated. The point of control is the least informative place to look for rejection — almost everything trades there. The edges are where the distribution thins out, and thin is where a small imbalance shows up as movement.

What the first touch does to the second

The first visit to an edge and the third are not the same event, and treating them as one is the most common way a level study gets muddled.

On the first visit, nothing has been consumed. Whatever resting interest sits there is intact. By the third, the same price has been offered repeatedly, and either it was absorbed each time or the participants who cared have already acted.

This is why a record of edge behaviour has to carry the visit number. Otherwise a level that held twice and broke on the third look is averaged into the same bucket as a level that broke immediately, and the average describes neither. It is also why “the level held N times” and “the level held N of M visits” are different statements — the second one has a denominator.

What a tool can honestly show

What is measurable at an edge, without inference:

• That price arrived — and at which visit, counted from the start of the session.
• What traded while it was there — volume at those prices, and how it split between the bid and the ask.
• How far it went past — penetration depth in ticks, which separates a touch from a break.
• What the path did afterwards — the bars that followed, recorded rather than judged.

What is not measurable is the reason. A tool can show that heavy volume traded at an edge and price did not continue — the classic absorption picture — but it cannot show that the absorption caused the reversal. Those are separate claims and only the first one is in the data.

So the useful design is to record the observable parts with their denominators attached, and leave the interpretation where it belongs. That is also the only form in which the record stays usable later: a stored judgement is stuck with the definition that produced it, while stored observations can be re-judged when the definition changes.

Honest limits

• The session boundary is a choice. “Previous session” is not one thing — the regular-hours session and the full electronic session produce different value areas from the same day. What a session boundary actually is covers why this is less settled than it looks.
• This is not a claim that value-area edges predict anything. The rotation reading is widely used and has a coherent story behind it. A coherent story is not evidence, and nothing here should be read as a measured edge.
• Visit counts are cheap to record and easy to get wrong. A price that hovers at a boundary can be counted as one visit or ten depending on how the band and the exit rule are defined.
• Not advice. A description of what the reading asserts and what is observable — not a recommendation to trade any level.

More research

• What a session boundary actually is The session your platform draws, the one your data has, and why “previous regular hours” is harder to pin down than it sounds.
• What a low-volume node actually claims Where the auction-theory reading comes from, what it asserts, and the gap between that and a trade.
• Five gates I set before looking at a backtest result Cost fixed in advance, break-even win rate from measured R:R, same-bar rate, a minimum sample, and pre-registration.
• What excursion distributions tell you that P&L does not MAE and MFE in R, logged per trade — how they separate an entry problem from an exit problem.
• All research The index, with what each piece measured.

Related docs: session levels · naked POC