> For the complete documentation index, see [llms.txt](https://docs.velvet.capital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velvet.capital/governance.md). # Governance We are a team of crypto-natives who’ve been in the space since 2016 and gone through all its ups and downs. We know first-hand what it takes to manage a 7+ figure crypto portfolio onchain and our experience ranges from launching digital investment & banking platforms in TradFi to running one of the first Web3 incubators to working on the core Solidity repo as a part of the Ethereum Foundation grant and to building web3 infrastructure for $1B+ crypto projects. We’ve built Velvet.Capital for ourselves & the community we’ve formed over the years and excited to share it with you all & make DeFi better together. As we believe in progressive decentralization, we’ve formed Velvet DAO, which will be the main driving force behind the protocol management and will be gradually onboarding new members using the token as the main governance mechanism. You can find more information about the protocol governance in this section. --- # 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.velvet.capital/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.