← Two free tracks · Prop-risk foundations
Free · ICT / SMC · 2 · written draft for review
Liquidity hypotheses and failed breaks
Prerequisite: Complete structure without hindsight.
Original English written learning is available here. Real clean ATAS captures/continuous replays and independent review are not complete. Hypothetical examples are not trading records.
Orders are not visible simply because a swing is obvious
Traders often describe equal highs or lows as liquidity areas. That is a hypothesis that some stops or orders may cluster there, not a complete observation of the order book. Stops can be broker-held, conditional or absent; visible resting orders can cancel. A wick past a swing does not prove a coordinated institutional “stop hunt”.
First distinguish a fact from a proposed explanation. “The high exceeded yesterday's high” is a price fact. “A bank took everyone's stops” asserts an actor and intent not established by the candle. Even a depth feed does not disclose every participant's full inventory or motive.
Worked hypothetical area
Before playback, mark previous high 150.00 and attention band 149.75–150.25. A later five-minute bar trades to 150.75 and closes at 149.50. The observable statement is: price probed above the band and closed below it. Under a prewritten descriptive rule, call it a failed break candidate. Do not rename it a profitable reversal after seeing the next decline.
There are at least two future branches. Price might remain below the band, supporting a provisional rejection description. Or it might return, close above the band and continue, weakening that description. For this lab, write “two consecutive completed closes above 150.25 invalidate my below-band rejection description”. This chosen rule makes the exercise auditable; it is not validated market law or trade advice.
Do not turn a map into a stop-loss recipe
A reference band is not automatically the right place to trade or hide a stop. Spread, volatility, upcoming events and execution mechanics matter. A touch gives no entry permission. If your data are incomplete, the timestamp is wrong, or risk limits are unknown, stand aside from execution. You can still practise describing the available information offline.
If no stop orders are visible in your dataset, say so. Use conditional language: “possible stop-related activity”, not “confirmed trapped institutions”. A valid analysis can stop at insufficient evidence.
Practice · 3 points
- A bar wicks above a prior high but closes below it. Name one observation and one unsupported causal claim.
- Using the lab rule, closes above the band are 150.50 and 150.75. What happens to the rejection description?
- Does invalidation automatically authorise a long trade?
Reasoned answer key
1. Observation: probe above followed by a close below. Unsupported claim: a named institution deliberately hunted stops (1). 2. Two completed closes above the upper edge invalidate the stated below-band rejection hypothesis (1). 3. No: entry, timing and risk conditions are not supplied by a descriptive invalidation (1).
Readiness: 3/3, a premarked area, both future branches and an invalidation written before outcome. Genuine clean replay evidence remains pending.
Education only. Futures involve substantial loss risk. No profit, pass rate or institutional intent is established by these examples. No signup, evaluation purchase or paid feed is required.
Next in the recommended reading order: Imbalance labels: define, test, invalidate