> For the complete documentation index, see [llms.txt](https://docs.scrt.network/secret-network-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scrt.network/secret-network-documentation/overview-ecosystem-and-technology/ecosystem-overview/contributors-and-entities/secret-committees/governance.md). # Governance The Governance Committee exists to promote transparent collaboration within the network and provide neutral discussions on proposals, voting, and governance issues. We work closely together with validators and other committees to ensure optimal support for the overarching Secret Network goals. It is vital to provide a space where thoughts and ideas can freely and respectfully be exchanged by anyone within the Secret Network to aid in reaching informed consensus on-chain. The Governance committee lead is Pmuecke | SecretSauce which you can contact via the #Governance discord channel. The Governance committee hosts a meeting every Monday at 1600 UTC and posts weekly meeting notes on the [forum](https://forum.scrt.network/t/governance-meeting-notes-mega-thread/3946/41). --- # 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.scrt.network/secret-network-documentation/overview-ecosystem-and-technology/ecosystem-overview/contributors-and-entities/secret-committees/governance.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.