> For the complete documentation index, see [llms.txt](https://docs.kleros.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kleros.io/products/governor.md). # Governor Kleros Governor is a smart contract that allows for the effecting of DAO governance decisions to be decentralized without compromising security. By designating Kleros Governor as the governor contract for your DAO, batches of transactions representing governance decisions can be submitted as lists to Kleros Governor. In case of disputes about the validity of the submitted transactions, Kleros's jury network will step in to arbitrate the dispute. ## How does it work? The first step to using Kleros Governor is to point to it as the governor contract for your DAO. Each Governor session enforces governance decisions that were passed prior to the start of the current session, which can be organised on a platform like [Snapshot](https://snapshot.org/). Once a decision has been reached, a (technically inclined) user then needs to translate the decision into a list of transactions and submit them for execution by the governor contract. If there is only one list submitted in the challenge period, it will be accepted and the deposit is returned to the submitter. If a competing list is submitted in the same session, a dispute will be automatically created in Kleros Court, and jurors will get to choose which list is correct. After dispute resolution concludes, the deposit from the losing list will be used to pay the jurors and reward the user that submitted the winning list. Lists that most completely enforce the greatest number of governance decisions will be accepted. The process for choosing between lists can be seen [here](https://cdn.kleros.link/ipfs/QmPt2oTHCYZYUShuLxiK4QWH6sXPHjvgXTqMDpCShKogQY/KlerosGovernorPrimaryDocument.pdf). 🏛 [Kleros Governor App](https://governor.kleros.io/) 🏛 --- # 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.kleros.io/products/governor.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.