> For the complete documentation index, see [llms.txt](https://organic-1.gitbook.io/organic-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://organic-1.gitbook.io/organic-docs/treasury/reporting-policy.md).

# Reporting Policy

We’ll keep everything transparent through a public dashboard showing our sprint progress, achievements, rewards, engagement stats, and all treasury movements. \
\
Biweekly reports will track the treasury ledger, and monthly ones will show payout splits and task results. \
\
Every transaction will be verifiable on-chain, with CSV exports for anyone who wants to check the data themselves. Transparency isn’t just accountability it’s our best marketing.

**Report Policy**

* Biweekly treasury ledger with tags
* Monthly payout report with pools and splits
* CSV export for anyone to check
* Live Dashboard of our metrics (on our platform or Dune)


---

# 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://organic-1.gitbook.io/organic-docs/treasury/reporting-policy.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.