> For the complete documentation index, see [llms.txt](https://pool-party-xyz.gitbook.io/pool-party-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/for-managers/responsibilities-and-limits.md).

# Responsibilities & limits

This page sums up what you can and cannot do as a manager, and what is expected of your conduct.

#### **What you can do**

* Set the pool's mandate (once, at creation).
* Allocate and rebalance within the mandate, through adapters.
* Configure the performance fee (10% to 90%).
* Operate the pool yourself. (Operating with an AI agent is coming soon.)
* Choose to be publicly identified.

#### **What you cannot do**

* Hold or withdraw user assets. Custody always stays with them.
* Act outside the mandate. The contract prevents it.
* Change the mandate after it is created.

#### **Conduct**

* Do not promise returns, do not downplay risk, do not create artificial scarcity.
* Do not give investment advice. Present the strategy and the facts; the decision is each user's.

{% hint style="info" %}
Pool Party does not endorse any manager or strategy. Your identification, if any, comes from you and is not an endorsement by the platform.
{% endhint %}


---

# 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://pool-party-xyz.gitbook.io/pool-party-docs/pool-party-v2-docs/for-managers/responsibilities-and-limits.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.