> 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/oscillators/momentum-concepts/signals.md).

# Signals

Momentum Concepts classifies signals into three levels of conviction based on the synergy between the Momentum Wave, MFI, and the Confidence Engine.

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2FDAG5T7hkVGhtIaTaaxCy%2Fdocs-momentum-concepts-006.png?alt=media&amp;token=fedd43f2-ceb4-4534-9b8d-08210abcb350" alt=""><figcaption></figcaption></figure>

### Signal Levels

1. **Standard (L1) - Circle Marker**:
   * **Logic**: Base momentum reversal detected (Momentum Wave crossover) with standard confidence support.
2. **Strong (L2) - Diamond Marker**:
   * **Logic**: Confirmed momentum shift with **Moderate Confidence (> 25%)** and supporting capital flow.
3. **Elite (L3) - Triangle Marker**:
   * **Logic**: High-conviction setup where momentum, volume flow, and the Confidence Meter are all in alignment at **Strong levels (> 35%)**.

### Signal Filtering

Through the settings, you can filter which signals appear on your chart:

* **Aggressive**: Shows almost all reversals as soon as they meet the base L1 criteria.
* **Balanced**: Filters for signals that have a verified confidence build.
* **Conservative**: Only shows signals that have significant trend support or reversal context.


---

# 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/oscillators/momentum-concepts/signals.md?ask=<question>&goal=<user_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.