A mitigation block is a way to describe what happens when an earlier order area loses its original role and price returns to work through the remaining interest. It is a review label, not proof of reversal or a standalone entry signal.

The structure must change first

Before calling an area mitigation, identify the prior range, the meaningful break and the later return. A bounce from an old zone without a structural change is only a reaction. Keep the sequence visible so the label does not become hindsight decoration.

A changed role needs a break and a later response.

What the return can show

Price may accept the old area, reject it briefly, or pass through it. A return can therefore support, weaken or leave unresolved the explanation that unfinished orders remain there. Record the response rather than assuming that a visit must produce a reversal.

Mitigation and ordinary order blocks

An order-block candidate describes a possible work area before its later role is known. Mitigation language describes a changed role after the original structure has been damaged or invalidated. The distinction depends on sequence and context, not on the visual shape of one candle.

Review exercise

Choose a completed range with a failed directional idea. Mark the original candidate, the structural break and the return. Write one explanation for acceptance and one for rejection, then classify the evidence as supports, weakens or unresolved.

Learning boundary

Mitigation blocks do not provide automatic entries, stops, targets, probabilities or proof of institutional intent. Continue with Unit 029: Breaker Blocks to compare a changed role after a failed structure.

Review questions

1. What structural change happened before the return?
2. What did price do inside the old area?
3. Is the mitigation explanation supported, weakened or unresolved?
4. How does the area differ from an unconfirmed order-block candidate?