> 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/governance-and-infrastructure.md).

# Governance and infrastructure

A register for securities is long-lived infrastructure. The assets it records can outlast many versions of the software that records them. The protocol has to be governable, so that it is always clear who may do what, and it has to evolve without putting the register at risk.

This section describes the infrastructure that serves both: one access model for every privileged action, standard mechanisms for upgrades, deterministic addresses across chains, and a storage layout that survives upgrades. Each is built from a standard mechanism in preference to a bespoke one.

| Page                                                                                                          | What it covers                                                                                                                                                   |
| ------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Access management: roles and domains](/governance-and-infrastructure/access-management-roles-and-domains.md) | The AccessManager model, how roles are scoped to domains, how a suite is commissioned, and who administers what.                                                 |
| [Upgradeability: beacons and versions](/governance-and-infrastructure/upgradeability-beacons-and-versions.md) | What is upgradeable and by whom, shared and isolated suites, published versions, and the safeguards of an upgrade.                                               |
| [Deterministic deployment (CREATE3)](/governance-and-infrastructure/deterministic-deployment-create3.md)      | Addresses that depend only on the factory and a salt: one address per asset and per identity across EVM chains, and contracts wired to each other at deployment. |
| [Namespaced storage (ERC-7201)](/governance-and-infrastructure/namespaced-storage-erc-7201.md)                | How each layer keeps its state in its own region, the namespaces of the protocol, and what that protects in an upgrade.                                          |


---

# 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/governance-and-infrastructure.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.