> 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/oscillator-concepts-tm/signals.md).

# Signals

This section standardizes the nudges you act on.

### **Two families**

* **Re‑entry markers:** Triangles when The Line returns from outside back toward the band—useful for fades and for trend pullback timing.

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-833f6256051fd3cd13768775775eb89924b24219%2Fdocs-oscillator-concepts-012.png?alt=media" alt=""><figcaption></figcaption></figure>

* **Divergence markers:** Diamonds for bullish, circles for bearish—visual anchors for your reversal plan.

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2Fgit-blob-44a6ce1e07a188dbea1342c514701e2136ea8b7b%2Fdocs-oscillator-concepts-013.png?alt=media" alt=""><figcaption></figcaption></figure>

### **How to prioritize**

* On **trend days**, prioritize signals that agree with the stripe and are not fighting a fresh Pulse.
* On **range days**, re‑entries matter more; take profits at the other side of the range or at obvious structure.
* After a **Pulse**, expect overshoots and messy retests—be patient before fading.

### **Display control**

Show all, only re‑entries, or only divergences. Keep charts clear and focused on your session objective.


---

# 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/oscillator-concepts-tm/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.
