# Community governance

Growth DAO is a decentralised organisation powered and run by owners of GRWTH. Ultimately, the strategy and direction of Growth DAO can be determined by a significant proportion of its members. Blockchain technology has been utilised to codify many of the dynamics of the commercial framework outlined in this white paper. However, there will inevitably be key decisions to be made from strategy proposals to startup funding choices to whom to accept as a growth expert.

**There are 3 steps in the community governance process:**

1. Proposal formation - community members can discuss proposal ideas within our Discord and community forums. These proposals can be drafted and peer-reviewed. This will help to form detailed improvement plans and initiatives, which are in the wider community's best interest.
2. Proposal formalisation - Once a month, community members are encouraged to attend and participate in Growth DAOs Town Hall meetings. This online video conference is facilitated by the founders and opens up the floor to any validated community member with backing to bring a proposal to the community. Voting Proposals will be presented and formalised in these meetings.
3. On-chain vote - Once a voting proposal has been formalised and agreed upon in the Town Hall meeting, an on-chain proposal will be outlined in Snapshot. Sufficient acceptance will be needed by GRWTH holders. Once processed, the results will be recorded on-chain and actions taken by associated members.


---

# Agent Instructions: 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:

```
GET https://docs.growth-dao.com/growth-dao-whitepaper/governance/community-governance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
