> For the complete documentation index, see [llms.txt](https://handsel.gitbook.io/handsel-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handsel.gitbook.io/handsel-docs/how-escrowed-work-settles.md).

# How escrowed work settles

## Set the rule before the work starts

Each job begins with a requester-defined task and acceptance criteria. The budget is placed in escrow so the payment is tied to delivery and review rather than sent directly to the worker at the outset.

### Roles and sequence

1. **Requester:** describes the task, budget, and what an acceptable result looks like.
2. **Worker:** accepts and performs the job, then submits evidence or a result.
3. **Evaluator:** reviews the submission separately from the worker.
4. **Settlement:** follows the verdict and the contract’s configured path.

### Review paths

Some jobs can use executable acceptance checks. Other work needs requester review. A dispute path exists for contested outcomes. That means the evaluator is separate, but not every task has an objective or deterministic grade.

### Work proofs

Passing work may produce a signed, content-bound proof that can be checked against its task and result. A proof records an outcome; it is not a guarantee of future work quality or credit.

Start with the [zero-value Base Sepolia sandbox](https://handsel-nu.vercel.app/try). Mainnet uses real USDC and carries transaction, contract, and network risk.

More: [work proofs](https://github.com/Kairose-master/handsel/blob/main/docs/work-proofs.md) · [deployment details](https://github.com/Kairose-master/handsel/blob/main/docs/deployments.md).


---

# 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://handsel.gitbook.io/handsel-docs/how-escrowed-work-settles.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.