> For the complete documentation index, see [llms.txt](https://docs.deeep.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deeep.network/introduction/using-usddeeep/governance/deeep-committees.md). # DeEEP Committees DeEEP is designed to be run for the web3 community, by the web3 community. With that in mind the goal is to distribute the decision making to those with the right skillsets and interest that are supported by the community. ### Committee Frameworks All committees members are nominated by a member of the DeEEP community and voted into their position for a term of 12 months. Committees shall meet at least every quarter in a public web meeting. Committees may meet more often than quarterly and may meet in private, but should publish meeting minutes for the community. Security focused committee(s) may designate portions of their meetings as restricted from the public to discuss threats that are under embargo and withhold publishing minutes for those portions. Before the mainnet launch committees may be launched and members may be approved by a vote in Discord. ## Good Citizen Committee The Good Citizen Committee is in charge of proposing and setting rules and guidelines for participation of all members of the DeEEP Community. Their responsibilities include, but are not limited to: * Create rules preventing unfair gaming of rewards distributed to DeEEP members * Setting standards for acceptable services that can run on DeEEP * Setting community engagement rules and best practices to guide moderators (Discord, github, Telegram, etc) --- # 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://docs.deeep.network/introduction/using-usddeeep/governance/deeep-committees.md?ask=&goal= ``` `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.