> For the complete documentation index, see [llms.txt](https://unipilot.gitbook.io/unipilot-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unipilot.gitbook.io/unipilot-v2/the-pilot-protocol/range-prediction-and-strategy.md).

# Range Prediction & Strategy

Each vault’s range strategy will begin with default parameters relating to spread, tick average in a duration (twapDuration), and maximum price deviation. When the rebalance function is called, the smart contract calculates how much the price has deviated from the average tick in twapDuration, and the deviation should not be more than the max deviation threshold.

For the base position in a Community vault, the spread is either added or subtracted from the current tick. Maximum liquidity possible is added in the base position, while the remaining reserves are placed in the next range, which is either above or below the base range, depending upon the tokens remaining in reserve. The default parameters can also be modified for each pool using governance. For example, the spread for stable pairs could be set to a lower value compared to more volatile pairs. The architecture for this strategy is modular, allowing it to be adjusted to support any algorithm.


---

# 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://unipilot.gitbook.io/unipilot-v2/the-pilot-protocol/range-prediction-and-strategy.md?ask=<question>&goal=<endgoal>
```

`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.