> For the complete documentation index, see [llms.txt](https://docs.trueopen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trueopen.ai/protocol/v1/tasks.md).

# Task Lifecycle

The complete TrueOpen V1 Task lifecycle and its protocol boundaries.

The Task protocol turns a signed inference order into one final on-chain outcome. It coordinates off-chain compute and data without treating an off-chain service as the final judge.

## Five stages

```mermaid
flowchart LR
    A[Open Task] --> B[Inference]
    B --> C[Open Verify]
    C --> D[Verification]
    D --> E[Settlement]
```

1. **Open Task** accepts one signed order version, freezes its budget and snapshots, gathers Worker handraises, and selects one Worker.
2. **Inference** lets the selected Worker retrieve input, execute the bound Profile, and submit a signed receipt plus output and evidence commitments.
3. **Open Verify** gathers eligible Verifier handraises and selects the Verifier set using future randomness.
4. **Verification** has the selected Verifiers independently compute, commit, reveal, and submit results.
5. **Settlement** includes the challenge window and any challenge round, then applies one final accounting plan.

A challenge is a subdivision of Settlement, not a sixth Task stage. Settlement and finality are written together.

## Follow a Task

The stage walkthroughs explain cross-component exchanges, accepted transitions, and recovery paths. They illustrate the rules linked below; they do not define additional protocol stages.

1. [Task submission](/protocol/v1/tasks/task-01-open-task.md)
2. [Inference](/protocol/v1/tasks/task-02-inference.md)
3. [Verification assignment](/protocol/v1/tasks/task-03-open-verify.md)
4. [Verification](/protocol/v1/tasks/task-04-verification.md)
5. [Challenges](/protocol/v1/tasks/task-05-challenge.md)
6. [Settlement](/protocol/v1/tasks/task-06-settlement.md)

The final two walkthroughs expand the Settlement stage. Challenges remain part of Settlement in the five-stage protocol model.

## Governing rules

| Page                                                                         | Covers                                                                                |
| ---------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| [Orders and task identity](/protocol/v1/tasks/orders-and-identity.md)        | Sessions, order sequencing, signed orders, stable Task identity, and escrow admission |
| [Candidate selection](/protocol/v1/randomness/candidate-selection.md)        | Eligibility, handraises, immutable snapshots, and Worker/Verifier assignment          |
| [Data and evidence](/protocol/v1/data-and-evidence.md)                       | Task Builders, data commitments, access, retention, and availability responsibility   |
| [Verification](/protocol/v1/tasks/verification.md)                           | Full-output checking, commit-reveal, result formation, and deadlines                  |
| [Challenges and settlement](/protocol/v1/tasks/challenges-and-settlement.md) | Permissionless challenge rounds, effective verdict, accounting, and finality          |

## Lifecycle invariants

* One accepted Task uses one order hash and one Profile version.
* Its Task Builders remain fixed until all data responsibility ends.
* Candidate and parameter snapshots do not change retroactively.
* A selected node's duty is attached to its stable operator, not to a replaceable service key.
* Every accepted Task has a deterministic terminal path, including timeout and unavailable-data paths.
* No Task earnings become claimable before finality.


---

# 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://docs.trueopen.ai/protocol/v1/tasks.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.