> For the complete documentation index, see [llms.txt](https://aeriform.gitbook.io/tape/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aeriform.gitbook.io/tape/states.md).

# Working with States

**States** are an important aspect of Tape to help with keeping track of the status of a project and its tasks.

Clicking on the right most part of any **Item** will change the state. In this example we set the first item to "Priority".

![](/files/-MZLereXlLjrBjLlBUux)

There are six states in total that range in progression, based on a common production workflow. 

Clicking to change the State will cycle through each of them in order, back around to Neutral.

With a few more Items we can set each with appropriate states, for example:

![](/files/-MZLfJ5useuWsnaZ3ROj)

| State     | Intention                            |
| --------- | ------------------------------------ |
| Neutral   | A normal item with no specific state |
| Priority  | An item with high priority           |
| Working   | Work in Progress                     |
| Submitted | Sent for approval                    |
| Approved  | Work has been approved               |
| Done      | Task is done                         |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://aeriform.gitbook.io/tape/states.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.