> 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/metrics/kpis.md). # KPIs We’re tracking a few key metrics to understand how Organic is growing and where we can improve. These KPIs help us measure community activity, task completion, engagement, and overall health of the project. By keeping these numbers transparent, we can spot what’s working, fix what’s not, and make smarter decisions together. It’s not about vanity metrics it’s about building a system that rewards real participation and keeps Organic moving in the right direction. **Our KPIs** * Weekly active contributors * Completed tasks per week * Weekly revenue and payout volume * Time to review a submission * Share going to top ten vs long tail * Organic growth on Twitter and Discord * Space listeners and replays --- # 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/metrics/kpis.md?ask=&goal= ``` `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.