> For the complete documentation index, see [llms.txt](https://isbm.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://isbm.savimbo.com/project-description/effective-participation/community-involvement.md). # Community involvement How the community benefits from a project, including data! In addition to the methodology for proof of biodiversity, projects need to show that they have a fair and equitable way of distributing project funds to the actual individuals on the ground. The technology for funds disbursement must have safeguards against corruption and eliminate middlemen and other potential diversions or dilutions of funds from the people who are actually preserving the ecosystem. The methodology is designed to preserve endemic biodiversity by enabling Indigenous communities to become stewards of the ecosystem and deploying small farmers relying on traditional hunter-gatherer lifestyles to conserve the jungle and monitor for indicator species. Finally, BCPs must show a plan for equitable distribution of access to, ownership of, and crediting for data from the project including promotional materials, project data about ecosystems and biodiversity, video and photographic data, and photographs of participants with IP and LC communities involved using FAIR and CARE guidelines [(Carroll et al., 2021)](https://sciwheel.com/work/citation?ids=10929355\&pre=\&suf=\&sa=0). Many projects are the collaboration of public and private parties with IP and LCs. For projects which have public funding (eg. a UNESCO World Heritage site) and a local community involved (i.e. fishing villages protecting and surrounding the site). All parties, their motivation, and funding sources must be clearly identified. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://isbm.savimbo.com/project-description/effective-participation/community-involvement.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.