> 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/report-to-your-community.md).

# Report to your community

Much of your reporting is already automatic: a pool's positions, allocations, fees, and performance are on-chain and visible to everyone. Still, communicating your strategy helps build trust.

#### **What on-chain transparency already delivers**

Users can see, at any time, what the pool holds, the moves you made, the fees, and the history. You don't have to prove results: they are recorded.

#### **Communicating your strategy**

Explaining the mandate, your thesis, and how you make decisions helps your community understand the pool. Be clear about what the strategy does and what its limits are.

{% hint style="info" %}
When you communicate, do not promise returns, do not downplay risk, and do not create artificial urgency. Talk about what the strategy does and what is recorded on-chain, not about what it "will" return.
{% 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/report-to-your-community.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.