> 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/ja/purojekutono/purojekuto.md).

# プロジェクト境界

時間および空間における生物多様性クレジット化プロジェクトの境界

プロジェクトには空間的及び時間的な制約があります。本方法論は、IP及びLCの内外における水平的拡大並びに波及的な行動変容を想定して設計されており、グループ化プロジェクトの活用が奨励されます。 

プロジェクト境界を特定するための主たる入力は、BCPに登録され、したがってクレジット付与の対象となる土地、及び当該登録の日付です。以下、順に説明します。 


---

# 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/ja/purojekutono/purojekuto.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.