> For the complete documentation index, see [llms.txt](https://docs.t-rex.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.t-rex.network/security-and-trust-model.md).

# Security and trust model

The guarantees of the protocol rest on a set of security properties and on a set of trust assumptions. A register for securities has to be auditable in its assumptions as much as in its code. This section states both plainly: what the contracts guarantee whatever anyone does, whom the protocol trusts and for what, what happens when something goes wrong, and how the code is verified.

| Page                                                                            | What it covers                                                                                                              |
| ------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| [Trust assumptions](/security-and-trust-model/trust-assumptions.md)             | Every party the protocol trusts, what for, and what bounds that trust.                                                      |
| [Invariants](/security-and-trust-model/invariants.md)                           | The properties that hold at all times: supply, balances, gates, positions, validations, identity bindings, access.          |
| [Emergency behavior](/security-and-trust-model/emergency-behavior.md)           | What the protocol does on its own when something is wrong, the levers available, who holds them, and how operation resumes. |
| [Audits and verification](/security-and-trust-model/audits-and-verification.md) | The audits, the test suites, the formal specifications, and how to report a vulnerability.                                  |

The central property is that compliance is enforced by construction, not by detection. An ineligible or non-compliant holding cannot be brought into existence: every change of ownership passes the eligibility gate and the compliance gate before it is recorded, on the chain that sees the complete distribution of the asset. There is no window in which a bad state exists and has to be caught and unwound.


---

# 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://docs.t-rex.network/security-and-trust-model.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.