> For the complete documentation index, see [llms.txt](https://inclusivity.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inclusivity.toolkit.citiobs.eu/dialogue.md).

# DIALOGUE

## Why is relevant?

Meaningful progress on equity, diversity, and inclusion in citizen science cannot be made from the outside looking in. The barriers that prevent people from participating are often invisible to project organisers, and assumptions made at the design stage about the core activities of the initiative might unintentionally exclude particular groups of people. Understanding and learning what these barriers might be is a core part of creating the conditions for diverse inclusion, yet this requires deliberate effort: a critical hurdle in broadening participation is often an absence of alignment between community priorities and research objectives.&#x20;

Dialogue, storytelling, and collective action are among the most powerful methods for surfacing the perspectives of underrepresented groups. They can also help to establish trust and drive meaningful social change. Establishing dialogue and co-creative practices early on between the public, local governments, academia, and other stakeholders has the potential to enhance active and inclusive participation, not just by making projects more accessible, but by reshaping them around the needs and concerns of those most at risk of being left behind.&#x20;


---

# 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://inclusivity.toolkit.citiobs.eu/dialogue.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 `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.
