> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/models/breaker-model-tm/statuses.md). # Statuses Breaker Model Statuses The Breaker Model tracks the complete lifecycle of a trade setup, categorizing it into distinct statuses from inception to completion. ### 1. Potential A setup enters the "Potential" status the moment a Higher Timeframe (HTF) liquidity pool is swept and price begins to reverse. At this stage, the Breaker Block has not yet been confirmed by a candle close. * *Note: You can enable alerts specifically for when a setup is in this potential phase.* ### 2. Confirmed (Active) A setup becomes "Confirmed" (or Active) once the required structural shift occurs and the candle closes, officially validating the Breaker Block. * The indicator will draw the Breaker Box in your active color (e.g., solid green or red) and plot the R:R projection targets. * If `Unicorn Mode` is enabled, the setup will only reach this status if a Fair Value Gap (FVG) is present. ### 3. Target Hit A confirmed setup transitions to "Target Hit" when price action successfully reaches one of your active Risk-to-Reward projection lines. * Once this happens, the visual components of the setup (boxes, lines) will fade to your designated inactive color (e.g., gray) to signify the trade has played out. ### 4. Invalidated A confirmed setup becomes "Invalidated" if price action breaches the stop-loss level before hitting the target. * Depending on your settings, the stop-loss is either the absolute extreme of the liquidity sweep (`Use Swing as Invalidation`) or the opposite edge of the Breaker Block. * Upon invalidation, the setup will either turn inactive (fade to gray) or be completely removed from the chart if `Discard Invalidated` is enabled. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.candelacharts.com/models/breaker-model-tm/statuses.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.