> For the complete documentation index, see [llms.txt](https://stellar.gitbook.io/module-library/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellar.gitbook.io/module-library/governance-modules-library-overview.md). # Governance Modules Library Overview {% hint style="info" %} *Please note that this Governance Modules Library is created by BlockScience and is currently under ongoing development. You acknowledge and understand that any implementations you make of the specifications from this Governance Modules Library is solely at your own risk.* {% endhint %}

A artist illustration on the Governance Modules Library by Viola Sellerino

> ### What is the Governance Modules Library The Governance Modules Library (GML) is a curation of both new and classic modules for governance in dApps and DAOs. Its stated goal is to spread best practices and innovation as well as to accelerate adoption of Soroban as an ecosystem by providing a batteries-included experience for enhancing DAOs and dApps governance.

A visual depiction of what are (non-exhaustively) Governance Modules. They are spread across categories of typical outputs and use cases.

Governance Modules are templates that can be readily implemented and tuned to specific applications which depend on or require governance solutions. As Governance is a wide topic, we've opted to categorize those templates across typical Web3 use cases, such as 1) how to attribute numerical power to a user (Power Attribution), 2) how to funnel that power through specific signals (Signaling Forms), 3) how to associate identity and/or rights with a user (Identity / Rights Management), and 4) how to generate representative signals from behavioral and/or reputational components (Reputation Metrics). Those use cases are by no means exhaustive, and further categorizations may arise as inspired by efforts such as distilling [Metagov's Govbase](https://airtable.com/appx3e9Przn9iprkU/shrgnUrj0dqzZDsOd/tblXLaQeoKygb4ais/viw3rNQQfK1S6ipfe). ### What should a Governance Module contain in order to be published? * A parent page with its title as the name of the module, containing the following sections: * Summary * Use Cases * User Journey * Module-specific Adjustments * The following sub-pages: * Specification * Implementation Instructions * Tuning Guidelines * Simulations * Each page should indicate its primary authors (individuals and/or organizations) and a date. * Any further modifications / contributions can be acknowledged and/or listed as authors. Dates must be indicated. --- # 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://stellar.gitbook.io/module-library/governance-modules-library-overview.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.