> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-civics-committee/our-previous-work/governance-health-kpi-report.md). # Governance Health KPI report ### Governance Health KPI report Through 2025 the community argued about whether Cardano's governance was healthy, and had no shared way to settle it. The Civics Committee built one. #### The working group The Governance Health Working Group was created on 17 July 2025, to deliver the first objective of the committee's [H2 2025 roadmap](https://docs.google.com/document/d/1N5OAsKYL05U_ACKp1s2vmOQNAUzX2-LmLsgzjyMCzxQ/edit?usp=sharing). Its [charter](https://docs.google.com/document/d/1hbNAOGpjAODkKRxKIQAN6M0UEmvSgceFf13IY3DlRyk/edit?usp=sharing) set a deliberately narrow scope: define the metrics first, and only then judge what counts as good or bad. The aim was a measurement standard the community could agree on before anyone argued about the readings. #### The report The group published a **24-page report across six categories of key performance indicators** covering ADA holders, DReps, SPOs and the Constitutional Committee. The committee approved it for publication on 4 December 2025, and it was released in January 2026. [**Read the Governance Health KPI report**](https://docs.google.com/document/d/1EKH1ktkgu3ne7mta8o-ky7x3yMKcG4onjiFKZxCns24/edit?usp=sharing) #### The dashboard A report is a snapshot. To make governance health something the community can watch over time, a **Dune-based dashboard** built on the report's KPIs went live in April 2026. [**View the live dashboard**](https://gov-health.intersectmbo.org/) Having delivered the report and the dashboard, the working group paused. --- # 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://committees.docs.intersectmbo.org/intersect-civics-committee/our-previous-work/governance-health-kpi-report.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.