> 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.md).

# Protocol

Versioned rules governing the TrueOpen network.

The TrueOpen protocol coordinates accountable AI inference without placing model execution or bulk Task data on-chain. The chain owns the identities, assignments, deadlines, commitments, economic state, settlement, and finality required for independent participants to reach the same result.

This section explains the design principles, trust assumptions, mechanisms, and algorithms behind TrueOpen, alongside the versioned rules implementations must follow. Design explanations and stage walkthroughs provide context; versioned rules define protocol requirements.

Start with [Design principles](/protocol/design-principles.md) and the [Trust model](/protocol/trust-model.md), then explore the [V1 protocol](/protocol/v1.md).

## Current version

| Version               | Status                      | Scope                                                                                                                |
| --------------------- | --------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| [V1](/protocol/v1.md) | Current documentation track | Phase 0 chain, service participation, Task execution, verification, economics, governance, and canonical asset route |

A network release identifies the exact protocol and software versions it supports. Implementations must not infer compatibility from a page title or silently substitute rules from another version.

## Protocol boundary

```mermaid
flowchart LR
    U[Users and applications] -->|signed orders and transactions| C[On-chain protocol]
    B[Builders and Nexus] -->|proposals and relayed actions| C
    N[Cortex Nodes] -->|signed service actions| C
    C -->|assignments, deadlines, commitments, settlement| U
    C --> B
    C --> N
    B <-->|Task data and results| N
```

The protocol governs accepted actions and state transitions. Task inputs, model execution, outputs, and most evidence move through authenticated off-chain services, but off-chain arrival or acknowledgement cannot independently assign responsibility or move funds.

## How to read this documentation

* Start with the [V1 overview](/protocol/v1.md) for domain relationships and system-wide invariants.
* Read [protocol conventions](/protocol/v1/conventions.md), [accounts and signatures](/protocol/v1/accounts-and-signatures.md), [Models and Profiles](/protocol/v1/models-and-profiles.md), and [randomness](/protocol/v1/randomness.md) for foundational rules.
* Use [service participation](/protocol/v1/service-participation.md) for provider responsibility and bonds.
* Use the [Task protocol](/protocol/v1/tasks.md) for admission through finality.
* Read economics, governance, and cross-chain pages for their respective state domains.
* Follow the stage walkthroughs within [Task lifecycle](/protocol/v1/tasks.md) for participant-by-participant interactions and their governing rules.

## Documentation policy

Protocol pages are maintained and reviewed in this repository. Draft proposals, open questions, implementation blockers, and future-roadmap material are not protocol documentation.


---

# 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.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.