> ## Documentation Index > Fetch the complete documentation index at: https://cogno.studio/docs/llms.txt > Use this file to discover all available pages before exploring further. # Task statuses > Understand the five visible statuses, hidden outcomes, Cogno groups, and transition rules. Every Task has one workflow status. Status controls where the Task appears; running state and Cogno ownership add treatments inside that status. ## Visible statuses | Status | Meaning | | --------------- | ----------------------------------------------------------------------------------------------------------------------------- | | **Backlog** | Work kept for later. | | **Ready** | Work ready for a person or agent to start. New Tasks normally begin here. | | **In Progress** | Work with active responsibility. Cogno-controlled Tasks can wait here between runs or while their assignee connects a folder. | | **In Review** | Delivered work waiting for a person to review. | | **Done** | Work a person has finished and closed. | The default query shows the four open statuses: `status:backlog,ready,in_progress,in_review`. ## Hidden outcomes | Status | Meaning | | ------------ | ----------------------------------------------------- | | **Archived** | Removed from active views without permanent deletion. | | **Rejected** | Cogno-created work that a person declined. | **Done**, **Archived**, and **Rejected** columns start hidden on the Board. You can include them with the Board visibility control or a `status:` filter. ## List and Board placement On a computer, List shows **In Progress** first as one lane with a tab per person. The open tab lists that person's running and waiting work, with Cogno-controlled work nested in an orange **Cogno** group. The remaining sections follow **In Review → Ready → Backlog**. Cogno-controlled Tasks exist only in **In Progress**. They stay in the orange **Cogno** group between runs and while an Environment is unavailable. Board keeps every Task in its status column. Cogno-controlled cards keep their orange treatment without gaining another column. On a phone, Tasks remain in their ordinary status sections and use the same treatment. ## Status proposals After a completed run, Cogno can propose **Backlog**, **Ready**, or **In Review** and move the Task there with an open proposal. That move releases Cogno control. A failed or stopped run leaves the Task in **In Progress**. **Done** remains a person's decision; an ordinary agent result that asks for Done is folded into **In Review**. When a person explicitly accepts work in the Task conversation, the agent can apply that decision and move the Task to **Done**. Proposal metadata does not create a list lane or Board column. Use `suggested:true` to filter for Tasks with an unresolved proposal. Choosing a status deliberately resolves that metadata. ## Transition rules | Transition | Behavior | | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Create a Task | Starts in **Ready**, except **Later** creates it in **Backlog** and a Board column's **+** uses that column. | | Move into **In Progress** by dragging onto the section | Refused with *Send a message in the Task to start work.* Sending the message claims an environment and moves the Task. | | Drop a Task on a person's tab in **In Progress** | Assigns the Task to that person and queues a run for their machine. The Task moves at once; without a folder on their machine it waits there with a hollow branch mark until they connect one. | | Drop a Task that already runs in an environment on another person | Refused: the lane shows **Fixed to \'s environment** and nothing changes. | | Move out of **In Progress** during a live run | Opens **Stop the running agent and move?** Confirming stops the run and keeps partial results. | | Move to **Done** | Applies when a person selects it or explicitly accepts the result in the Task conversation. | | Archive | Removes the Task from active views and can be reversed. Unfinished agent work on the Task is cancelled. | | An agent archives a Task | Allowed for a duplicate or for work that no longer exists, and reversible in the same way. An agent cannot archive the Task it is running, and archiving is never how a run reports work finished. | ## Filter aliases Old saved filters continue to resolve to the current vocabulary: | Input | Resolves to | | -------------------------------------------------------------- | ------------- | | `active`, `doing`, `started` | `in_progress` | | `proposed`, `todo`, `open`, `new`, `idea`, `triage`, `planned` | `backlog` | | `completed`, `closed`, `resolved`, `fixed`, `merged` | `done` | | `review` | `in_review` | | `cancelled`, `wontfix` | `archived` | | `declined` | `rejected` | ## Related docs * [Work with Tasks](/docs/tasks) * [Task views and filters](/docs/task-views) * [Run an agent on a Task](/docs/agents)