> 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/methodology/id/lampiran/lampiran-x-daftar-periksa-validator-sejawat.md).

# Lampiran X: Daftar periksa validator sejawat

Pedoman pemilihan validator sejawat yang dinominasikan komunitas

Untuk komponen Trees dalam protokol #SexyTrees, data utama biasanya cukup untuk menetapkan bukti penanaman. Pemantauan satelit berkembang sampai pada titik bahwa, berapa pun jumlah penyedia yang digunakan, kami merekomendasikan validator sejawat tingkat komunitas.&#x20;

Di bawah ini ada daftar periksa ciri-ciri validator sejawat komunitas yang baik.&#x20;

### Daftar periksa evaluasi IEP

Daftar periksa dasar untuk validasi IEP meliputi:&#x20;

**Biologi**

* [ ] Apakah spesies indikator dipilih dengan tepat untuk ekosistem yang terlibat?&#x20;
* [ ] Apakah skor spesies indikator yang diekstrapolasi dari data publik akurat?&#x20;
* [ ] Apakah subset pengamatan yang dipilih secara acak akurat sampai 90%?
* [ ] (Opsional) Apakah validator iNaturalist telah memberi pengamatan tingkat validasi independen "Research grade"?

**Topografi**

* [ ] Apakah peta akurat dan konsisten di dalamnya? Apakah segmen, judul, atau ekosistem saling tumpang tindih?&#x20;

**Kepatuhan**

* [ ] Apakah hak atas tanah valid di yurisdiksi yang dimaksud? Jika hak milik tanah penuh tidak terlibat, apakah BCP sudah menunjukkan penguasaan lahan dengan cukup?&#x20;

**Kunjungan lokasi**

* Verifikasi lokasi ground-truthing FPIC (Persetujuan Atas Dasar Informasi Awal Tanpa Paksaan, PADIATAPA)


---

# 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://sexytrees.savimbo.com/methodology/id/lampiran/lampiran-x-daftar-periksa-validator-sejawat.md?ask=<question>&goal=<user_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.
