> For the complete documentation index, see [llms.txt](https://handbook.opencoreventures.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.opencoreventures.com/ocv-employees/vc-ops/company-formation-process/internal-approvals-and-conflict-checks.md).

# Internal Approvals & Conflict Checks

New company approval process consists of two parts: GP approval and a GitLab conflict check.

## **GP Approval**

OCV team prepares project summary and intended business plan (in the internal research doc) for GP review.

Founder (CTO) compensation sign off proposal to the GP should include:

1. Founder Name (with LinkedIn profile)
2. Title
3. Cash Compensation (in USD equivalent; provide justification)
4. Equity (following framework from [Equity Guidelines](/ocv-employees/vc-ops/company-formation-process/founder-offer-and-equity.md) and provide support around experience level)
5. [Options Pool Size](/ocv-employees/vc-ops/company-formation-process/issue-equity-and-options-pool.md) (and intended allocation reserves)
6. Start Date / Timeframe (if known)
7. Any additional offer details

## **GitLab Conflict Check**

New companies need to pass a conflict check with GitLab prior to an offer being sent. The conflict check requires that an email be sent to the GitLab team with the following information:

* The name of the OS project
* A link to the project
* A one sentence description of what the new company will do


---

# 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://handbook.opencoreventures.com/ocv-employees/vc-ops/company-formation-process/internal-approvals-and-conflict-checks.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.