> For the complete documentation index, see [llms.txt](https://volosui.gitbook.io/volo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://volosui.gitbook.io/volo/volo-vaults/technical-layout.md).

# Technical Layout

Volo Vault is built rather flexible for curators (vault creators and admins) to onboard new strategies, switch between automated and less-automated approaches and performing any bespoke actions without compromising the integrity of the vault NAV. 

<figure><img src="https://3466679256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbGzidXqHHyC2MOZET4ED%2Fuploads%2FgODJMUT4chebPaVYxHIb%2Fimage%20(1).png?alt=media&amp;token=153fa795-d6eb-4e30-89bc-69a227eba9be" alt=""><figcaption></figcaption></figure>

We also utilizes the Programmable Transaction Block (PTB) feature of Sui to allow more dynamic transactions for the vault curator to accommodate strategies and portfolio shifts.

<figure><img src="https://3466679256-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbGzidXqHHyC2MOZET4ED%2Fuploads%2FdlAoLibsAxywLlPPty7l%2Fimage%20(2).png?alt=media&amp;token=77344085-3f52-49d2-b3e3-ab8b547c7999" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://volosui.gitbook.io/volo/volo-vaults/technical-layout.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.