> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/textual/entity-types/entity-type-custom-model/using-the-progression-tracker.md).
# Using the progression tracker
On the **Entity Types** page, the **Progression Tracker** column indicates the completion status of each step in the process.
Progression Tracker column to show the status for each model-based type creation step
For each step, the block color indicates the status:
* Grey - The step is not started.
* Yellow - The step is in progress.
* Red - There was an error in the step.
* Green - The step is completed.
Note that a step that was completed earlier can change status when a user returns to it. For example, you might publish a trained model, then go back to further refine the guidelines. In that case the model publishing step is still green, but the guidelines refinement is yellow.
To display the page for a given step, click the step block. You can only navigate to steps that are available based on the overall progress of the entity type creation. For example, if you have not yet assembled a set of test data, then you can only go to the test data step. You cannot refine guidelines or train models. If you don't have training data, then you cannot train or publish models.
---
# 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.tonic.ai/textual/entity-types/entity-type-custom-model/using-the-progression-tracker.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.
