> 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/sdg-contributions.md).

# SDG contributions

Contribution to the United Nations Sustainable Development Goals

Projects may wish to report their contribution to the UNSDGs. This methodology is specifically designed to preserve the environment with a directive towards financial inclusion and the preservation of local cultures. As a result of the design of each project, different SDGs may be relevant, and it is up to each project to evaluate the need for reporting on the outcomes as they relate to the SDGs.

Any projects reporting on their UNSDG goals must choose a maximum of five SDG focus areas, and include the specific target area by number. For qualification with UNSDG accounting, sub-topics must be specified for every goal. For each target, projects are expected to provide specific metrics and report on the metrics on a regular basis. 

For example, SDG Goal 12 is "Responsible consumption and production." The project might focus on "12.a — Support developing countries to strengthen their scientific and technological capacities to move towards more sustainable patterns of consumption and production." The metric to accomplish the goal could be the number of camera traps installed to capture indicator species.

<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://isbm.savimbo.com/sdg-contributions.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.