> For the complete documentation index, see [llms.txt](https://open-carbon-protocol.gitbook.io/ocp-handbook/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-handbook/methodologies/uncertainty.md).

# Uncertainty

* Carbon Markets are still **inherently uncertain** - the majority of projects operate at the forefront of scientific understanding of the systems they operate in and the best technology for measuring the impact of specific interventions.
* The way we approach uncertainty at the OCP is to build processes to capture new developments and ensure they are integrated into past, present, and future credit calculations.

## Accounting for Uncertainty

#### OCP Level

* [Annual Audit](/ocp-handbook/governance/annual-audit-process.md): All methodologies and projects are audited every year to ensure they are still up-to-date. If they aren't, a [major update](/ocp-handbook/methodologies/methodology-updates.md) is triggered, including the formation of a new expert panel.
* We believe that companies should move to a '[Living Ledger](https://oneshot.earth/blog09/),' where carbon credits are treated as assets, recorded on a company's environmental balance sheet next to its environmental liabilities. This allows companies to ensure any carbon credits they buy are always matching their environmental liabilities, reducing the risk of uncertainty. Reach out to <info@oneshot.earth> if you're interested in piloting this approach.

#### Methodology Level

* [Section 2 (Conservativeness)](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/sections/2.-conservativeness) of every methodology outlines ares of uncertainties and describes how conservative quantifications techniques are applied to mitigate them.
* In [Section 7 (Quantification of GHG Emissions)](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/sections/7.1.-quantification-of-greenhouse-gas-emissions), we encourage methodology developers to think about **dynamic baselining** (i.e. including monitored variables in the baseline emission calculation) so that the baseline can be recalculated at every issuance event.
* In [Section 8 (Permanence)](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/sections/8.-permanence), uncertainty must be assessed and documented as part of the permanence & reversal risk assessment.

For more information, read our [**OCP Methodology Requirements**](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/):&#x20;

{% content-ref url="/spaces/J74f9z1HD7PVdEYWZTll" %}
[OCP Methodology Requirements](https://open-carbon-protocol.gitbook.io/ocp-methodology-requirements/)
{% endcontent-ref %}

#### Project Level

* In the case of a reversal event, credit owners will be compensated via the [OCP Buffer Pool or Project Insurance](/ocp-handbook/projects/mitigating-reversal-risk-insurance-and-buffer-pool.md).
* In the case of excess issuance or over crediting, the OCP will [cancel credits and compensate owners](/ocp-handbook/registry/credit-cancellation.md).
* If projects are found to be under-crediting, we work with the Project Developers and credit owners to [rightsize the credits](https://oneshot.earth/blog06/).


---

# 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:

```
GET https://open-carbon-protocol.gitbook.io/ocp-handbook/methodologies/uncertainty.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
