> 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/components.md). # Components Breaker Model Components The Breaker Model relies on several interconnected components to validate and display trade setups. ### Liquidity Sourcing The foundation of the model. It tracks up to 4 discrete HTF sources (`Source A`, `Source B`, `Source C`, `Source D`). You can configure whether these sources look for major Swing Highs/Lows, or static OHLC (Open, High, Low, Close) levels from the higher timeframes. The indicator draws a sweep line when these levels are raided. ### Breaker Detection Once a liquidity level is swept, it monitors the immediate reaction. It looks for the origin of the sweep and waits for a confirmed candle close that breaks structure and officially forms the Breaker Block. ### Projections & Risk Manager Upon confirmation of a setup, this component calculates the distance between the entry zone and the invalidation point (the risk). It then projects your predefined Risk-to-Reward multipliers (`Targets: 1, 2, 2.5`) as take-profit lines on the chart. ### Visual Lifecycle Manager Handles the aesthetics of the setup. It draws the Breaker Box in an "Active" color when formed, and transitions the box to an "Inactive" color (e.g., gray) once the setup either hits its target or breaches its invalidation level. If `Discard Invalidated` is enabled, failed setups are removed from the chart entirely. --- # 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/components.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.