> 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/guides/journeys.md).

# Journeys

A journey orders several guides end to end, for one persona or one situation. A guide says how to do one operation. A journey says which operations come in which order, who performs each, and where the path branches. Read a journey first to see the whole path, then open the guide of each stage for the calls.

| ID | Journey                                                                                                                                                             | Persona                        | From                            | To                                                         |
| -- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------ | ------------------------------- | ---------------------------------------------------------- |
| J1 | [Issuer journey: launch an asset](/guides/journeys/j1.-issuer-journey-launch-an-asset.md)                                                                           | Issuer                         | The decision to issue           | A live asset with its first holders                        |
| J2 | [Investor journey: from onboarding to secondary transfer](/guides/journeys/j2.-investor-journey-from-onboarding-to-secondary-transfer.md)                           | Investor                       | No identity                     | A first position, and a transfer to another holder         |
| J3 | [Transfer agent journey: operations on a live asset](/guides/journeys/j3.-transfer-agent-journey-operations-on-a-live-asset.md)                                     | Token Agent and Registry Agent | The grant of the agent roles    | Every agent operation, by situation                        |
| J4 | [Cross-chain journey: distribute and reconcile](/guides/journeys/j4.-cross-chain-journey-distribute-and-reconcile.md)                                               | Issuer and Investor            | An asset on the reference chain | Positions active on satellites, reconciled on the register |
| J5 | [Offboarding journey: an investor that must no longer hold or receive](/guides/journeys/j5.-offboarding-journey-an-investor-that-must-no-longer-hold-or-receive.md) | Issuer and its agents          | A holder to exclude             | No position, and no eligibility when the claim is revoked  |

A journey does not repeat what its guides say. Each stage links to the guide that documents it. The numbers of the guides are permanent references, not steps: see [How guides are numbered](/guides/about-the-guides.md).


---

# 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/guides/journeys.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.