> For the complete documentation index, see [llms.txt](https://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://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-committees/civics-committee.md).

# Cardano Civics committee (CCC)

{% hint style="info" %}
View more details in the dedicated Committee space

[civicscommittee.docs.intersectmbo.org](https://civicscommittee.docs.intersectmbo.org/)
{% endhint %}

## What is the Civics Committee?

The Civics Committee advises on governance processes and community engagement across the Cardano ecosystem. The committee develops frameworks for effective community participation in governance, coordinates with subject matter experts to ensure informed decision-making, and provides advisory support to the Cardano Constitutional Committee as needed.

## Why is this committee important?

The Cardano Civics Committee ensures that Cardano's governance is accessible, fair, and transparent.

## Which topics does this committee cover?

While not all of these topics are addressed yet, the vision is for the committee to cover topics such as:

* Enable and maintain the history of off-chain discussions about proposals.
* Monitor tools for on-chain voting to verify that they are maintained and operational.
* Update guidelines, templates, and standards for on-chain voting.
* Providing non-binding recommendations as requested by the community regarding Cardano governance improvements.

## How to join?

The Cardano Civics Committee participates in Intersect committee elections to select the next cohort of members. Intersect always communicates details on how to apply and vote well in advance of each election.

***


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/intersect-membership/intersect-committees/civics-committee.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.