> 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/operators/builders.md).

# Builders

Coordination, relay, and data availability responsibilities of a TrueOpen Builder.

Builders run Nexus to coordinate Task proposals, deliver Task data, and relay signed participant actions. They support off-chain progress while the chain determines assignments, verdicts, and settlement.

## Responsibilities

* Coordinate Task proposals and participant handraises.
* Deliver input, output, and evidence under the accepted Task bindings.
* Relay signed material and distinguish relay acknowledgement from chain acceptance.
* Preserve required Task data through the retention and cleanup windows.
* Continue serving accepted Tasks whose fixed Builder group includes the operator.

Phase 0 uses a governed Builder set. A replacement applies at its defined future boundary; it does not replace the Task Builders already fixed for historical Tasks.

## Operating boundaries

Builder operation requires reliable chain connectivity, authenticated data transport, durable Task storage, and monitoring of pending relays and retention obligations. Public deployment commands and endpoint configuration will accompany supported Nexus releases.

Builders do not execute inference merely by running Nexus. See [Data and evidence](/protocol/v1/data-and-evidence.md), [Task submission](/protocol/v1/tasks/task-01-open-task.md), and [Governance](/protocol/v1/governance.md) for the governing responsibilities.


---

# 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/operators/builders.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.