> For the complete documentation index, see [llms.txt](https://bzl.gitbook.io/bzl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bzl.gitbook.io/bzl-docs/context/institutional-requirements.md).

# Institutional Requirements

{% hint style="info" %}
While tokenisation has progressed rapidly, many implementations remain optimised for open participation or speculative use cases. These approaches are not suitable for institutional financial products, which require controlled access, clearly defined lifecycle management, and alignment with existing market practices
{% endhint %}

Key limitations of existing tokenisation models include:

> * Coupling issuance with liquidity or trading venues
> * Assumptions of unrestricted market participation
> * Limited support for in-life asset events
> * Insufficient separation between technology providers and asset issuers

For products such as funds, treasury instruments, and private credit, these limitations introduce unnecessary operational and governance complexity. Institutional adoption requires infrastructure that prioritises precision, modularity, and long-term adaptability.

<figure><img src="/files/APalsspcggXc65USlE41" alt=""><figcaption></figcaption></figure>


---

# 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://bzl.gitbook.io/bzl-docs/context/institutional-requirements.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.