> 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/water-credits/calculation.md).

# Perhitungan air

CARA membagi karbon di lokasi restorasi.

Manfaat dari pendekatan ISBM:

* Kemampuan untuk segera diterapkan.
* Menjembatani komunikasi antara ilmu modern dan pemahaman Masyarakat Adat tentang ekosistem.
* Penerapan yang sederhana dan langsung.
* Protokol remunerasi yang jelas dan terpadu.
* Bukti keanekaragaman hayati yang dapat diverifikasi dan dapat dibuktikan secara ilmiah.
* Keterlibatan kelompok yang rentan dan belum pernah dapat memperoleh manfaat dari sistem keuangan.
* Pertimbangan atas kompleksitas hutan primer, berdasarkan pemahaman ilmiah tentang teori kompleksitas.
* Manfaat lanjutan bagi ekologi lain yang bergantung pada tetap terjaganya hutan hujan primer yang tangguh dan ekosistem primer lain.

Menjembatani pandangan modern dan pandangan Masyarakat Adat untuk menjaga planet adalah penggerak utama ISBM. Menyatukan kekuatan ini adalah harapan terbaik kami untuk segera melindungi kekayaan alam dan jasa ekosistem yang penting bagi kelangsungan hidup manusia dan planet ini.

<br>


---

# 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/water-credits/calculation.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.
