> For the complete documentation index, see [llms.txt](https://docs.tezos-homebase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tezos-homebase.io/dao-explorer-proposals-and-voting/registry.md). # Registry A registry is a list of key-value pairs of anything that a DAO chooses. Examples might include links to a constitution document, social media handles, a website URL, treasury policies, or any other metadata the DAO wants to store on-chain. The registry lives in a smart contract associated with the DAO, making it transparent, immutable (unless changed through governance), and publicly verifiable. Any member can view the registry to understand the DAO's official information and policies. Changes to the registry must go through the DAO's proposal and voting process. This means adding, updating, or removing registry entries requires community approval, ensuring that important DAO information remains under collective control rather than being editable by any single individual. For example, if a DAO wants to update its official website URL or add a link to new governance documentation, a member would submit a proposal specifying the key and new value, and the change only takes effect after the proposal passes and is executed. --- # 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.tezos-homebase.io/dao-explorer-proposals-and-voting/registry.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.