> 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/governance/ocp-governance-structure.md).

# OCP Governance Structure

The Open Carbon Protocol (OCP) has been designed from inception to administer issued carbon credits, methodologies, and associated integrity obligations over a multi-decadal time horizon.

OCP governance is structured around three core objectives: **transparency**, **accountability** and **quality**. All governance decisions aim to uphold these principles and ensure the OCP platform operates with the highest level of integrity.

### **Key Principles**

1. Consistent, accurate carbon accounting across all types of projects
2. 'Quality' = consensus of relevant expertise (both academic, industry, and from within the market)
   1. High quality should be the baseline for the industry (confidence + accuracy). We reach this through an independent [methodology development process](/ocp-handbook/methodologies/methodology-development-process.md) modeled after the peer review process, and [industry-leading practices from ICVCM](/ocp-handbook/welcome-to-the-open-carbon-protocol.md#see-how-the-ocp-addresses-the-core-carbon-principles).
   2. We issue highly impactful credits that meet buyers' needs and drive environmental and social change globally.
3. Transparency drives accountability, openness, and education. We provide the most open and transparent source of documents, processes, and data in the VCM.
4. Governance should drive three objectives: transparency, accountability & quality.

### Governance Model

The OCP operates under a two-tier governance structure separating corporate fiduciary responsibility from program integrity oversight.

#### Oneshot.earth Inc. Board of Directors (OSE Board)

The OSE Board is the fiduciary governing body of oneshot.earth Inc., the Delaware corporation that operates OCP. It holds ultimate legal and financial responsibility for the organization: corporate strategy, financial management, and legal compliance. The OSE Bylaws govern its composition and operation. The current OSE Board consists of Thomas Annicq (Founder and CEO) and can be expanded at the appropriate time to include investor representation and at least one independent director. Full board composition will be publicly disclosed at that time.

#### OCP Advisory Board

The [OCP Advisory Board](/ocp-handbook/governance/ocp-governance-structure/ocp-board.md) is an independently constituted governance body with formally delegated authority over OCP program integrity matters, established by resolution of the OSE Board. It is not a committee of the OSE Board. Its authority and independence criteria are set out in the OCP Advisory Board Bylaws. The Advisory Board's decisions on program integrity matters are final and binding and cannot be overridden by OSE management or the OSE Board within the Advisory Board's delegated scope.&#x20;

See the [OCP Board](/ocp-handbook/governance/ocp-governance-structure/ocp-board.md) page for current membership, responsibilities, and decision-making procedures.

#### OSE and OCP Organizational Chart

<figure><img src="/files/XXwCCzmpxoTM9pWwQHXQ" alt=""><figcaption></figcaption></figure>

***

### OCP Key Function Responsibilities

<table><thead><tr><th width="233.81640625">Responsibility</th><th width="249.46875">Details</th><th>Person/Team Responsible</th></tr></thead><tbody><tr><td>Methodology Approval</td><td><ul><li>Feedback on Methodology Drafts</li><li>Voting to Approve or Reject based on OCP Methodology Requirements and Voting Criteria</li></ul></td><td><a href="/pages/4BvkD4XOEx2bXNZcnp7Q"><strong>Independent Expert Panel</strong></a>. <br><br>Methodology development and approval is completely independent of the OCP Registry and OCP team. </td></tr><tr><td>Methodology Process Administration</td><td><ul><li>Recruiting and onboarding Expert Panel</li><li><a href="/pages/LSZL9bdAiNBe9XBmhQ8u">Conflict of Interest</a> management</li></ul></td><td><strong>Rio Richardson (Chief Product Officer)</strong> + Policy &#x26; Procedures team</td></tr><tr><td>Project Approval</td><td><ul><li>Feedback on <a href="/pages/CGVk7mePuAltElOj62YV">Project Proposal</a></li><li><a href="/pages/4bR9kGbfi6m9UhbLApaD">Project Validation</a></li></ul></td><td><a href="/pages/4bR9kGbfi6m9UhbLApaD"><strong>Independent VVB</strong></a>.</td></tr><tr><td>Credit Issuance</td><td><ul><li><a href="/pages/4bR9kGbfi6m9UhbLApaD">Data Verification</a></li></ul></td><td><a href="/pages/4bR9kGbfi6m9UhbLApaD"><strong>Independent VVB</strong></a>.</td></tr><tr><td>Project and Registry Administration</td><td><ul><li><a href="/pages/4bR9kGbfi6m9UhbLApaD#ocp-review">OCP Validation and Verification Review</a></li></ul></td><td><strong>Rio Richardson (Chief Product Officer)</strong> + Policy &#x26; Procedures team</td></tr><tr><td>VVB Onboarding and Oversight</td><td><ul><li><a href="/pages/aC6mWZv4FfImLmuG02L2#application-requirements-including-accreditation">Accreditation and Experience checks</a> (on application and annually)</li><li><a href="/pages/aC6mWZv4FfImLmuG02L2#onboarding-and-training">Onboarding</a> and <a href="/pages/aC6mWZv4FfImLmuG02L2#oversight">Oversight</a> management</li><li><a href="/pages/YYV2EGk85ZqW6UPoG8sm">KYB, AML, ABC</a></li><li><a href="/pages/LSZL9bdAiNBe9XBmhQ8u">Conflict of Interest</a> management</li></ul></td><td><strong>Rio Richardson (Chief Product Officer)</strong> + Policy &#x26; Procedures team</td></tr><tr><td>Material Program Changes</td><td><ul><li>Updates to OCP Handbook and Decision Making</li></ul></td><td><strong>OCP Advisory Board</strong></td></tr><tr><td><a href="/pages/wSHVXaos9Bl310ZjOsEj">Grievances</a>, <a href="/pages/YYV2EGk85ZqW6UPoG8sm">COI, ABC, AML</a> Decisions</td><td></td><td><strong>OCP Advisory Board</strong></td></tr><tr><td>Financial Management</td><td><ul><li>Budgeting and accounts</li><li>Financial reporting</li></ul></td><td><strong>Chris Fort (Chief Operating Officer)</strong> + Operations &#x26; Finance team. <br><br>Subject to fiduciary oversight by OSE Board of Directors.</td></tr></tbody></table>

***

### Updates to the OCP Handbook and Decision Making&#x20;

The Open Carbon Protocol is constantly developing as market needs unfold and through feedback and improvements with our users. All changes are made with the guiding principles above, and we are always open to feedback at any time.&#x20;

Rio Richardson, Chief Product Officer, is responsible for the administration and development of the platform. Decisions are made in consultation with the CEO, COO, and other team members. The OCP Advisory Board reviews and approves all material Handbook updates.

After the Handbook versions are finalized, they undergo a public commentary period. Feedback is listed on '[Handbook Version History + Public Commentary](/ocp-handbook/handbook-version-history-+-public-commentary.md)' and gets incorporated as described under the [Stakeholder Engagement & Complaints](/ocp-handbook/governance/stakeholder-engagement-and-complaints.md) section.&#x20;


---

# 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-handbook/governance/ocp-governance-structure.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.
