> 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/zh-cn/xiang-mu-miao-shu/fu-jia-xing.md).

# 附加性

本方法学的一般附加性必须通过适用现行版本 Cercarbono 的决策树加以证明， [生物多样性认证计划议定书](https://www.cercarbono.com/biodiversity-certification-programme/) 该决策树涵盖财务、规范和监管方面的超额附加性情形，以证明生物多样性保护与项目活动直接相关，而非源自外部来源。

本方法学对通过方法学衡量的行动附加性作了简化处理，以便纳入 IP 和 LC。

本方法学从其他物种的视角评判结果。人类可能对退化生态系统作出边际改善，且对于严重退化生态系统，这种改善幅度当然可能达到 200％，甚至 300％。然而，恢复后的生态系统永远无法像未受扰动生态系统那样，为全部本地物种群落提供完全可获得的环境。&#x20;

因此，对于发生在高生物多样性、高威胁生态系统中的项目，附加性内在于 [生态系统特征界定](/methodology/zh-cn/ji-xian-ping-gu/ji-xian-sheng-tai-xi-tong-fen-lei.md) 与 [价值归一化](/methodology/zh-cn/ji-suan/jia-zhi-ji-suan.md)。例如，任何列入 IUCN 红色名录的完整生态系统，或生物多样性热点生态系统，均因其受威胁状态而天然具有附加性。&#x20;

BCP 区域的 [完整性计算](/methodology/zh-cn/ji-suan/wan-zheng-xing-ji-suan.md) 在本方法学中，旨在确立受保护生态系统的可接受证明。因此，与其为变化提供证据，不如为无变化提供合理证据，而在受威胁生态系统中，无变化本身即具有附加性。&#x20;

在保护情境下，外部来源已确认某一生态系统处于威胁之中，附加性仅需证明项目维持了生物多样性的存在，且相关活动未被其他来源重复实施。


---

# 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://isbm.savimbo.com/methodology/zh-cn/xiang-mu-miao-shu/fu-jia-xing.md?ask=<question>&goal=<endgoal>
```

`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.
