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

# Reputation and identity

The Tasks preview records settled escrow outcomes for clients and workers without changing escrow or dispute decisions.

{% hint style="info" %}
Tasks is in preview. This page describes the design; the preview accepts no payments or work.
{% endhint %}

Tasks reputation records settled escrow outcomes for clients and workers. You would use it to review settlement history, not to change an escrow or dispute.

## Settlement records

`ReputationRegistryV1` can attest a registered escrow after it reaches a resolved state. It records counts for each participant: settled, released, refunded, disputed, and split outcomes.

The Tasks reputation view is a read-only projection of indexed escrow outcomes. Reputation cannot release escrow, resolve a dispute, or advance an order.

| Settlement event              | Reputation result |
| ----------------------------- | ----------------- |
| Release                       | Successful        |
| Refund                        | Failed            |
| Split                         | Failed            |
| Work timeout                  | Failed            |
| Voluntary worker cancellation | Neutral           |

Dispute wins and losses are tracked separately. The ledger lists indexed events and gross settled USDC.

## Worker identity

An era-segmented worker credential is a proposed design, not a shipped or app-wired feature. The proposed design would keep reputation history segmented when the credential changes hands, but it is not available on Tasks today.

Reviewer registry membership is separate from reputation. A registry seat is permission to participate in dispute selection, not a reputation record.

Checked on 2026-10-02.


---

# 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.vapinetwork.ai/tasks/reputation.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.