> For the complete documentation index, see [llms.txt](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/context/version-history.md).

# Version History

The OCP Methodology Requirements are continuously iterated on, to ensure methodologies are working with the best practice in the carbon markets. Proposed changes are assessed and approved by the [OCP Advisory Board](https://open-carbon-protocol.gitbook.io/ocp-handbook/governance/ocp-governance-structure/ocp-board) before publication. Current OCP users will be notified of upcoming changes and will be allowed to submit comments and questions.

Updates will undergo at least [30 days of public commentary](https://open-carbon-protocol.gitbook.io/ocp-handbook/governance/stakeholder-engagement-and-complaints#open-carbon-protocol-public-commentary). Outside formal commentary periods, [we encourage anyone to contact us with thoughts or concerns](https://open-carbon-protocol.gitbook.io/ocp-handbook/governance/stakeholder-engagement-and-complaints#reporting-grievances) about the OCP platform or any of our partners.

## Current Version: <mark style="color:$primary;">**v2.0**</mark>

**Updated: April 2026**

**Public Commentary:&#x20;**<mark style="color:$success;">**Open (until 31 May 2026):**</mark> [<mark style="color:$success;">**Submit Comments Here**</mark>](https://form.jotform.com/251804696997376)

<details>

<summary>Updates in v2.0</summary>

* Converted 'OCP Methodology Requirements' from PDF to Gitbook to allow for better navigation, expanded information and dynamic links and diagrams.
* Added version history with links to previous versions of the methodology requirements document
* Moved 'OCP Sectors and Sub-Sectors' from separate Google Doc into OCP Methodology Requirements. Added information on Active Methodologies (Approved and In Development) and whether each sub-sector is in OCP Scope.
* Added sector risk levels of leakage and reversal risk
* Added additional requirement for 40 years of ongoing monitoring for Land Use methodologies
* Changed Section 9 title 'Monitoring Plan' to 'Monitoring'

</details>

### Previous Versions:

* [**v1.4**](https://docsend.com/view/a3aabda3vg8dz2jd) | January 2026
* [**v1.3**](https://docsend.com/view/2wbtua53tnjgh86j) | February 2025

{% hint style="info" %}
v1.1 and v1.2 are early versions of the OCP Methodology Requirements, when we only provided 'Guidelines' for methodology development instead of requirements. Since then, we have both upgraded our methodology tool to work in 17 sections (vs. PDF), and have worked with ICVCM to set mandatory requirements for parts of the methodology development process to ensure CCP compliance.
{% endhint %}

* [**v1.2**](https://docsend.com/view/ja8wpc7yeh6mysti) | September 2024
* [**v1.1**](https://docsend.com/view/6h4f7fnjfy5radga) | August 2023


---

# 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://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/context/version-history.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.