> For the complete documentation index, see [llms.txt](https://docs.allo.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allo.xyz/tokenize/architecture.md).

# Architecture

<figure><img src="/files/BF0oNmongxPk7DKfWFdD" alt=""><figcaption><p>Tokenization flow</p></figcaption></figure>

1. **User**: The process begins with the user, who initiates the tokenization process.
2. **Create Token**: The user creates a digital token that represents ownership of the real-world asset they wish to tokenize.
3. **Asset Preparation**: After the token is created, the user prepares the asset for tokenization, ensuring it meets the necessary legal, financial, and technical requirements.
4. **Launch Token**: The user then launches the token, making it available on the blockchain, allowing others to participate in or invest in the tokenized asset.
5. **Trade**: Once launched, the token can be traded, enabling liquidity and allowing users to buy, sell, or transfer their ownership stake in the asset.


---

# 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.allo.xyz/tokenize/architecture.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.