# Manager Guide

Use each section as a checklist or template to fill with your vault-specific details.

***

### Who Can Create a Vault

* State the roles or entities permitted to create a vault (e.g., protocol team, approved strategists, governance).
* Specify any eligibility requirements, approval processes, or whitelisting steps.
* Describe any constraints (e.g., KYC/AML, on-chain permissions, multisig, legal entity requirements).

### How Deposits Flow into Your Strategy

Use the stepper below to describe the sequential flow from user deposit to strategy execution. Replace each step with the vault's actual mechanics.

{% stepper %}
{% step %}

#### User deposit

* Describe how users deposit assets into the vault (UI, contract call, supported tokens, minimums, etc.).
  {% endstep %}

{% step %}

#### Vault accounting / minting

* Explain how the vault issues shares or updates balances after a deposit (minting shares, accounting model).
  {% endstep %}

{% step %}

#### Allocation to strategy

* Detail when and how assets are moved from the vault to the strategy (timing, batching, rebalancing triggers).
  {% endstep %}

{% step %}

#### Strategy execution

* Describe how the strategy uses the funds (markets, protocols, leverage, lending/borrowing, etc.).
  {% endstep %}

{% step %}

#### Returns and reporting back to the vault

* Explain how profits/losses are realized and returned to the vault (harvests, rebase, realized vs unrealized P\&L).
  {% endstep %}
  {% endstepper %}

### Fee Configuration and Disclosure Expectations

* List the fees that apply (management fee, performance/incentive fee, withdrawal fee, strategist fee, etc.).
* Specify rate values, fee accrual methods, and when fees are taken (on deposit, on harvest, on withdrawal).
* Describe how fees are communicated to users (UI, contract metadata, documentation).

{% hint style="info" %}
Ensure fee mechanics and numerical values are easy for users to find and verify on-chain.
{% endhint %}

### Risk Management Guidelines

* Enumerate major risk categories to consider (smart contract risk, counterparty risk, liquidity risk, market risk, operational risk).
* Describe mitigation measures (audits, timelocks, limits, whitelists, circuit breakers, diversification).
* Define who is responsible for monitoring and executing emergency procedures.

{% hint style="warning" %}
Specify clear on-chain controls and off-chain processes for emergency response (e.g., pausing deposits or strategy exits).
{% endhint %}

### Reporting / Transparency Expectations

* State what on-chain and off-chain reports will be published (performance, positions, fees collected, audits).
* Define cadence for reporting (real-time dashboards, daily/weekly reports, periodic audits).
* Explain where users can verify claims (block explorer links, contract addresses, dashboards).

<details>

<summary>Example items to include in your reporting plan</summary>

* Links to deployed contract addresses and verified source code.
* Transaction hashes for major operations (strategic rebalances, large withdrawals).
* Historical performance data and methodology for calculating returns.
* Audit reports and security assessments.

</details>

### How to Build Trust (Clear Worldview, Consistent Behavior)

* Articulate the strategy's worldview — the core assumptions and market conditions under which the strategy operates.
* Commit to consistent behavior: predictable rules for deposits, withdrawals, rebalances, and fee changes.
* Maintain transparency: document decisions, publish rationale for major actions, and keep communication channels open.

{% hint style="success" %}
Trust is built through clarity and consistency: make your assumptions, limits, and decision processes explicit and repeatable.
{% endhint %}

***

{% hint style="info" %}
Use this guide as a template. Replace each checklist item and placeholder with vault-specific, verifiable details before publishing.
{% endhint %}


---

# 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://zeit-1.gitbook.io/zeit/vaults/manager-guide.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.