> For the complete documentation index, see [llms.txt](https://sexytrees.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sexytrees.savimbo.com/appendices/appendix-x-peer-validator-checklist.md). # Appendix X: Peer validator checklist For the Trees component of the #SexyTrees protocol, the primary data is usually sufficient to establish proof of planting. Sattelite monitoring is evolving to the point that any numbe of providers cwe recommend community-level peer validators. Below is a checklist of characteristics of good community peer validators. ### IEP evaluation checklist A basic checklist for IEP validation includes: **Biology** * [ ] Are the Indicator species appropriately chosen for the ecosystems involved? * [ ] Are the Indicator species scores extrapolated from public data accurate? * [ ] Is a randomly selected subset of observations accurate to 90%? * [ ] (Optional) Have iNaturalist validators given observations a "Research grade" level of independent validation? **Topography** * [ ] Are maps accurate and internally consistent? Do segments, titles, or ecosystems overlap? **Compliance** * [ ] Are land titles valid in the jurisdiction in question? If full land title is not involved, has the BCP adequately demonstrated Land control? **Site visit** * Ground-truthing site verification of FPIC --- # 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://sexytrees.savimbo.com/appendices/appendix-x-peer-validator-checklist.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.