> 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/introduction/how-to-join-organic.md). # How to join "Organic" #### How to join now We’re still in the early build phase. The backend is under development so users will soon be able to register, get their **Organic ID**, and start completing tasks directly on the platform in exchange for rewards. For now, everything happens in the **Discord,** where the community organizes, votes, and shares updates. It’s our temporary headquarters until the platform is live. The way it works is simple: the community decides which tasks matter, attributes value to each, and then a pool is created for that period. Contributors who complete and submit their work receive a proportional share of that pool. It’s transparent, traceable, and owned by the people doing the work. Once tasks are done, we vote again, deciding together what’s next, what needs fixing, and what feature deserves priority. That’s how we keep it organic: community-led from start to finish. --- # 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/introduction/how-to-join-organic.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.