> For the complete documentation index, see [llms.txt](https://docs.auto.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.auto.finance/auto-pools-protocol/protocol-mechanics.md).

# Protocol Mechanics

## Design Goals

The purpose of the Autopool Protocol is to continuously rebalance assets into destinations with the best risk-return profiles, aiming to outperform any individual destination included in the autopool over the long term. Earnings are auto-compounded back into the autopool and subsequently rebalanced.\
\
To achieve this, the autopool's rebalance logic does not merely chase the highest advertised yield but instead processes a comprehensive set of data, applies sophisticated logic, and adheres to safety constraints. \
\
This section will provide an accessible overview of the system's general architecture and essential features.

## Components & Logic

This section provides a simplified overview of the components, their functions within the Autopool Protocol, and a summary of the rebalance logic to help users achieve a basic understanding of the autopools.

[Read more](/auto-pools-protocol/protocol-mechanics/components-and-logic.md)

## Asset Flow Example

To understand the general architecture and functioning of the system, it helps to consider a simplified flow of assets within the system

[Read more](/auto-pools-protocol/protocol-mechanics/asset-flow-example.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.auto.finance/auto-pools-protocol/protocol-mechanics.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.