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

# Governance

Since our platform is decentralized, after the core development updates, we will give control to our community. Any CCAKE governance token holders may propose a change, update or development via our governance portal. Our governance structure will be like this:

First, any community member will propose their suggestion in our Discord channel’ **#issues**, then our community will talk upon this issue in Discord and Telegram. If this issue is agreed upon, the team will carry this proposal to the project page on Snapshot or Aragon.(the original issue can be amended before going to Snapshot page) When a proposal listed on Snapshot, those who hold CCAKE can vote either yes or no.

*If the majority of CCAKE holders vote yes, then the team will execute the proposal.* 

*If the majority of CCAKE holders vote no, then the team will not take action upon this proposal.* 

Any failed proposal can be talked upon in our socials, **but they can be issued again after 2 weeks.**


---

# 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://cheesecakeswap.gitbook.io/cheesecakeswap/tokenomics/governance.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.