> For the complete documentation index, see [llms.txt](https://docs.ozean.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozean.finance/governance.md).

# Governance

## OIP Template

<table data-header-hidden><thead><tr><th width="172"></th><th width="530"></th><th data-hidden></th></tr></thead><tbody><tr><td>Author</td><td>Name, Discord ID</td><td></td></tr><tr><td>Status</td><td>Draft, Review, Vote Pending, Approved, Rejected, Implemented</td><td></td></tr><tr><td>Type</td><td>Governance, Grant</td><td></td></tr><tr><td>Network</td><td>Ozean</td><td></td></tr><tr><td>Release</td><td>Date</td><td></td></tr><tr><td>Created</td><td>Date</td><td></td></tr></tbody></table>

**OIP** **Title** - Short and Concise Title

**Summary** - If you can't explain it simply, you don't understand it well enough. Provide a simplified and layman-accessible explanation of the OIP.

**Overview** - A brief overview of the key information in the proposal, including:

1. Task
2. Motivation / business case. Detail on how the proposal supports the goals of the Ozean ecosystem.

**Specification** - The technical specification should describe the syntax and semantics of any new feature.

**Rationale** - The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.

**Configurable Values -** (Managed by council / risk committee)

<br>