Direct answer
A worked example of “breakout definition” is a fully specified scenario that states: (1) the reference level you are watching, (2) the exact rule for what counts as a breakout, (3) the time window and data resolution used to evaluate it, and (4) what outcomes you will measure after the breakout event. The key point is that “breakout” is not a vague idea—you define it as a concrete set of conditions you can verify on a chart.
Mechanism or definition (what you must specify)
“Breakout definition” means the operational rule that turns a chart idea into something checkable. Common elements you should define include:
- Reference level: For example, a horizontal high/low, or the highest close over a recent range.
- Trigger condition: For example, “price touches and then closes beyond the level” versus “any intrabar wick crosses the level.”
- Evaluation moment: Which timestamp ends the evaluation—close, tick, or a fixed number of bars after the trigger.
- Lookback and buffers: How far back you measured the level, and whether you allow a tolerance (buffer) around the level.
- Outcome metric: What you call success or failure after the trigger, such as whether price returns inside the level within N bars.
Stable mechanics are the definitions and the measurement steps. Variable conditions include market volatility, liquidity, bid-ask spread, and execution timing; those can change whether a breakout is tradable in practice.
Evidence or example (fully worked scenario with assumptions)
Below is one transparent, self-contained example. No real prices are used; all numbers are assumed for the purpose of demonstration.
Assumptions
- You work on a chart where each bar represents one hour.
- You compute the reference level using the previous 10 hourly closes.
- Reference level = the maximum of those 10 closes, which equals 1.1000.
- Breakout trigger = the first bar where the hourly close is strictly greater than 1.1000 (not just touching).
- False-breakout test = within the next 3 hourly bars, the price closes back at or below 1.1000 at least once.
- You ignore transaction costs for the example, because the goal is definition testing, not trading performance.
Scenario
- Hours t-10 to t-1 (10 previous closes): all are ≤ 1.1000, and the highest close is exactly 1.1000.
- Hour t (candidate bar): the intrabar range goes from 1.0990 to 1.1010, but the hourly close is 1.0996.
- Result: Not a breakout, because your trigger requires a close strictly above 1.1000.
- Hour t+1: intrabar range 1.1002 to 1.1012, and the hourly close is 1.1004.
- Result: This is the first breakout by your definition.
- Hour t+2: close = 1.0999.
- False-breakout test: Yes, because you closed back at or below 1.1000 within 3 bars.
Conclusion from this worked example Under the stated rules, the event at hour t+1 is a breakout, and the sequence is classified as a false breakout because the market returned inside the level quickly.
Limitations and risks (why definitions can fail)
Material limitations come from how your definition interacts with real market behavior:
- Data resolution and trigger choice: If you used “any intrabar touch” instead of “close strictly above,” your breakout count could rise dramatically due to noise.
- Buffer and level stability: Real levels are seldom perfectly horizontal. A tiny tolerance or redraw rule can change classifications.
- Lookback and sample bias: Choosing a particular lookback window (like 10 bars) can fit one period and behave differently later.
- Execution vs. chart outcome: Even if a breakout is “true” on a chart, bid-ask spread, slippage, and latency can affect what you could realistically achieve.
- Failure mode: overfitting: If you adjust definitions repeatedly to make past behavior look good, the definition may stop generalizing.
Because outcomes vary by volatility regime, costs, and execution, historical testing of a breakout definition does not establish future results.
Verification or next question
To verify your own breakout definition, you can replay the same chart rules deterministically: mark the reference level using your stated lookback rule, then scan bar-by-bar for the first bar that meets your trigger. After that, apply your false-breakout test window exactly as defined.