> For the complete documentation index, see [llms.txt](https://docs.sylvera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sylvera.com/carbon-markets/carbon-markets/strategy.md).

# Strategy

Market-level research that sets the context for individual project decisions— how a crediting methodology behaves, and how a host country shapes risk.

Sylvera Strategy products cover the layer above the individual project. Where a Rating tells you about one project, Strategy research tells you about the systems that project sits inside: the crediting methodology it was developed under, and the country it operates in.

Use Strategy alongside Ratings to understand why projects of a given type or in a given jurisdiction tend to score the way they do, and to shape sourcing strategy before shortlisting specific projects.

## User Guides

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3>Methodology Profiles</h3></td><td>Assessments of the carbon crediting methodologies projects are developed under, and the quality risks characteristic of each.<br></td><td><a href="/carbon-markets/carbon-markets/strategy/methodology-profiles.md">Methodology Profiles</a></td></tr><tr><td><h3>Country Profiles</h3></td><td>Country-level analysis of the policy, regulatory and market conditions that shape carbon project activity in a jurisdiction.</td><td><a href="/carbon-markets/carbon-markets/strategy/country-profiles.md">Country Profiles</a></td></tr></tbody></table>


---

# 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://docs.sylvera.com/carbon-markets/carbon-markets/strategy.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.