> 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/methodology/savimbo-indicator-species-biodiversity-method-ko/appendices.md).

# 부록

프로젝트 사례, IPLC 의견 및 과학적 지원

이 절의 부록은 콜롬비아 푸투마요 주 빌라가르손의 특정 현장에 대한 적용 사례를 제시함으로써 ISBM의 정보를 맥락화하고, 이 방법론이 이 지역의 원주민(IP)과 지역 공동체(LC)를 위해 어떻게, 그리고 왜 개발되었는지에 관한 정보와 더불어, 전 세계 원주민(IP)과 지역 공동체(LC) 전반에 걸친 보다 광범위한 적용을 위한 과학적 근거를 제공하기 위하여 제시됩니다.  


---

# 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/methodology/savimbo-indicator-species-biodiversity-method-ko/appendices.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.