> For the complete documentation index, see [llms.txt](https://docs.oceanenterprise.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/strategic-decision-making.md).
# Strategic Decision Making
For important strategic decisions with respect to the code base such as feature inclusion (new version updates) and feature changes (breaking updates) a vote must be taken by existing OEC Association members.
Only members in good standing are eligible to vote.
Voting on these decisions is based on a contribution-weighted voting system, where voting power is proportional to the member's level of contribution to the OEC Association's activities, as measured by:
* Technical contributions to Ocean Enterprise development
* In-Kind contributions for work needed to complete pre defined deliverables
* Financial contributions beyond membership dues
* Material contributions including subscriptions to online collaboration and marketing tools
Contribution-weights are reassessed on a quarterly basis based on the contribution level of the previous quarter.
The OEC Board acts as tie breaker. Contribution-weights are calculated according to the following structure:
| Support Level | Raw Vote | Weighted Vote |
|---|
| 0 | 0 | 0 |
| 1 | 1 | 1 |
| 2 | 1 | 2 |
| 3 | 1 | 5 |
---
# 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.oceanenterprise.io/~/revisions/IKmS06jx6d2zQh2vmKN9/discover/governance/strategic-decision-making.md?ask=&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.