# Architecture Overview

BTOS is structured as a layered operating stack.

<figure><img src="/files/7PHubLBu7dRzZT0RzU7P" alt=""><figcaption></figcaption></figure>

At its foundation are tokenisation standards such as ERC-3643, ERC-4626, and ERC-7540. These support permissioned tokenisation, vault-based product structures, and asynchronous operational flows.

On top of this sits Byzanlink’s unified compliance model, which supports permissioning, whitelisting, policy control, lifecycle rule enforcement, and investor qualification logic.

At the delivery layer, BTOS provides a white-label solution and API engine that allow institutions to deploy branded product experiences and connect tokenisation workflows into their existing systems.

BTOS also connects to supporting services such as wallets, signatures, verification providers, and interoperability infrastructure.


---

# Agent Instructions: 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:

```
GET https://docs.byzanlink.com/byzanlink-tokenisation-os/architecture-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.