> 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/crt-model-tm/labels.md).

# Labels

CRT Model Labels

The model assigns specific labels based on certain conditions. Below is an explanation of what each label represents.

**C** - *Current Model Label:* These models are generated and displayed based on the number of candles present on the Higher Time Frame (HTF).

**R** - *Realtime Model Label:* These models are created on the Lower Time Frame (LTF) for the same HTF candle. Although they may reach 2 standard deviations or the first liquidity level, they can be invalidated later within the same candle.

**H** - *History Model Label:* These models are derived from historical data.

{% hint style="warning" %}
Models generated on the LFT for the same HTF candle, even if they reach 2 standard deviations or the first liquidity level, may be invalidated later within the same candle if it hasn't closed yet. These are marked as "real-time invalidated models." Be cautious when using these models, as their status could change once the candle closes.
{% endhint %}


---

# 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/models/crt-model-tm/labels.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.