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

# Community and Governance

## Channels

Clio DeFi maintains exactly two community channels. We have intentionally not opened a Discord server, a Mirror publication, or a Farcaster channel. Two channels is enough; more fragments the conversation.

* **X (Twitter):** <https://x.com/cliodefi> — announcements, milestone notes, audit updates
* **Telegram:** <https://t.me/cliodefi> — real-time community discussion, support, holder conversations

## Tone

The voice of Clio DeFi — across X, Telegram, the website, and this document — is intentionally restrained. We do not use emoji in announcements. We do not run countdown timers. We do not call our community "fam" or any equivalent. The product asks users to manage risk and execution with clarity; the community channels mirror that posture.

This is not a stylistic preference. It is a filtering decision. The community we want to build values clarity over velocity; the channels reflect that.

## Governance — Phase I & II

Through Phase II, all major decisions are made by the founding team and disclosed to the community within 14 days. Decisions affecting Treasury Reserve allocation require multi-sig signer consensus (3-of-5).

## Governance — Phase IV

Beginning in Phase IV (see [Roadmap](broken://pages/c1d5e87a71bf8aba5c652db0351031434fc9b7f7)), the Treasury Reserve transitions to onchain governance. The governance design is intentionally minimal at launch:

* One vote per token, with a per-wallet cap to discourage whale dominance
* Proposals require a 2% deposit (refunded on quorum)
* Quorum: 5% of circulating supply
* Voting window: 7 days; execution timelock: 48 hours

Detailed governance documentation will be published as a separate document at the start of Phase IV. The governance contract is deliberately not deployed today; we want it built against real operational learning rather than speculative best practices.

## Quarterly Transparency Report

Beginning at the end of Phase II, Clio DeFi publishes a quarterly transparency report covering:

* Treasury balances and movements
* Vault TVL by pool and net inflow / outflow
* Audit and security incident log (zero is the goal; we publish whatever is true)
* Roadmap progress against the milestones in [Roadmap](broken://pages/c1d5e87a71bf8aba5c652db0351031434fc9b7f7)

Reports are published on the Clio DeFi GitHub organization and announced on X. There is no paywall and no email gate.


---

# 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://clio-defi.gitbook.io/docs/community-and-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.
