> For the complete documentation index, see [llms.txt](https://docs.hyperhive.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hyperhive.finance/hyperhive-vaults/overview.md).
# Overview
The protocol is built as a yield aggregator vault using the ERC-4626 interface. Capital flows through three layers:
#### **Vault Layer**
the entry point for all deposits and withdrawals, managed by the Vault contract; it mints a share token (vault token) representing each user’s claim on the vault.
#### **Strategy Layer**
a set of Strategy Adapters that route vault assets into specific protocols on HyperCore and HyperEVM.
#### **Execution Layer**
HyperCore and HyperEVM, where yield is actually generated — spanning lending, staking, and delta-neutral strategies.
\
The three layers are decoupled: users interact only with the Vault Layer, and changes to strategy allocation or weighting do not affect the custody logic governing user assets.
---
# 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.hyperhive.finance/hyperhive-vaults/overview.md?ask=&goal=
```
`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.