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

# Community governance

Progressive governance API and the distinction between community votes, application decisions, multisig execution and on-chain governance.

SONIC introduces governance progressively. The existence of proposal/voting APIs does not imply an on-chain DAO.

## Routes

```
GET  /api/v1/governance/proposals
POST /api/v1/governance/proposals
POST /api/v1/governance/proposals/:id/votes
```

## Phase 1 — Community coordination

Application-managed proposals and participation voting support creator/community coordination while execution remains governed by explicit application/service roles.

```
COMMUNITY → PROPOSAL → DISCUSSION → VOTE → DECISION
```

## Phase 2 — Verified participation

Eligibility can incorporate contribution history, challenge participation, creator reputation and verified wallet ownership. Token holdings are not automatically the sole creative influence metric.

## Phase 3 — On-chain governance

Only selected high-value decisions should move on-chain after the mechanism explicitly defines:

* who can propose;
* who can vote;
* voting power;
* quorum;
* approval threshold;
* execution authority;
* timelock;
* emergency controls.

The implementation distinguishes decision types such as `COMMUNITY_VOTE`, `APPLICATION_DECISION`, `MULTISIG_EXECUTION`, and `ON_CHAIN_GOVERNANCE`.

Phase 1 does not silently enable token-weighted/on-chain execution.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/api-reference/community-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.