> For the complete documentation index, see [llms.txt](https://docs.aozo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aozo.io/aozo-earn/transparency/governance-and-controls.md).

# Governance and controls

How product limits and valuation checks can support risk management.

### Valuation and exposure controls

The product design includes checks on strategy valuations. It also includes limits on allocations to individual strategies, asset categories, and slower-to-exit positions.

{% hint style="info" %}
If valuations cannot be assessed reliably, or configured control limits are reached, AOZO Earn may pause or limit deposits, new strategy allocations, or withdrawal routes.
{% endhint %}

{% hint style="warning" %}
These controls do not eliminate risk. They do not ensure an external strategy can return funds. They do not guarantee recovery.
{% endhint %}

Read [Portfolio composition](/aozo-earn/transparency/portfolio-composition.md) and [Key risks](/aozo-earn/risks-and-security/key-risks.md).


---

# 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://docs.aozo.io/aozo-earn/transparency/governance-and-controls.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.