> For the complete documentation index, see [llms.txt](https://docs.shadeprotocol.io/shade-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadeprotocol.io/shade-protocol/advanced-topics-apps/silk/governance.md). # Governance The SILK peg is governed by Shade Protocol general governance, as well as the SILK Assembly - a research team and elected multisig that is capable of triggering SILK peg migrations as well as SILK composition changes. Generally speaking, SILK is not intended to be a speculative tool. It is intended to be an index focused on stability in relation to other currencies versus being an intentional inflation hedge (although their are components of SILK that are an inflation hedge). As such, the SILK Assembly and general Shade Protocol governance must carefully manage expectations and composition changes to be done in as conservative of a manner as possible. These changes should be scheduled on plan on some sort of annual basis, with plenty of transparency about proposed changes. Any sort of change that is not given a multi-month heads up should be vetoed unless there are drastic required changes to a rapid and permanent change in the global economy that should impact SILK's long term thesis and composition. --- # 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.shadeprotocol.io/shade-protocol/advanced-topics-apps/silk/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.