> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/about-enzyme/governance.md). # Governance Enzyme is one of the oldest protocols on mainnet, with a track record of over six years. Originally developed for replicating fund management practices on chain whilst removing intermediaries, the protocol has evolved considerably and can now be described as a protocol providing digital asset management infrastructure for builders and managers. We have a variety of users, ranging from liquid staking protocols accelerating their projects through our vault structures to capture deposits, fund managers building regulated services on our infrastructure and blockchain banks building products for their customers with enzyme at their core. Enzyme’s use cases are continually evolving and our governance structure reflects this evolution where we have a framework of two committees tasked with building and maintaining enzyme. Our strategy & operations committee focuses on direction as the market evolves and our technical committee ensures that the protocol remains robust and secure through specific technical expertise and audits. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.enzyme.finance/about-enzyme/governance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.