> 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/investing/market-structure-and-rotation/altseason-index/features.md). # Features Altseason Index Features The Altseason Index comes packed with features and customizable settings to tailor the indicator to your trading style. * **Composite Modeling**: Aggregates four independent metrics into a single, noise-reduced 0-100 oscillator. * **Deep Opportunity Highlights**: Automatically flashes vertical chart backgrounds when the index dips below the critical 20 level, pinpointing prime accumulation zones on both the oscillator and main chart. * **Tiered Zones**: Distinct visual gradients highlight the standard Opportunity zone (under 30) versus the Deep Opportunity zone (under 20). * **Fully Customizable**: Control component weights, timeframes, symbol inputs, and all visual colors directly from the settings panel. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.candelacharts.com/investing/market-structure-and-rotation/altseason-index/features.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.