> For the complete documentation index, see [llms.txt](https://docs.correlaid.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/wiki/hitchhikers-guide.md).

# How We work – Hitchhiker's Guide to CorrelAid

Some thoughts on how we work internally.

{% hint style="info" %}
**Visit our** [**monthly onboarding call**](https://pretix.eu/correlaid/open-onboarding/) **to learn about how CorrelAid activities look like, how the organization is structured, and how you can get involved.**
{% endhint %}

Our goal with CorrelAid is to democratize the potential of Data Science. In practice, we achieve this by supporting a network of over many data enthusiasts in Germany, by giving them the opportunity to grow, and by organizing pro-bono data science projects for civil society. But how do we work *internally*? This is an overview of how we organize ourselves at CorrelAid, how we work and which principles we follow.

## Our Code of Conduct and Code of Ethics

## Our Impact

* Empowering NPOs to use data in a critical and reflective way to achieve their goal. 
* Enabling effective engagement (self-effective for volunteers & effective for NPOs). 
* Participation of marginalised groups within data science.

## Our Organization

We are formed as an association ("Verein" in German). In practice, however, the official organs of the association only have a secondary role. Instead, most of the structures we work in are informal, always potentially changing and ad-hoc.

### Structure

#### *The Assocation*

[board](/~/revisions/hfepfFy5E9C1WpLCChmV/wiki/board.md), ethics committee, general assembly + members 

#### *The Remote Office Team*

full-/part-time employees 

#### *The Volunteer Community*

Core-Crew-Crowd

### Communication

#### *Slack Workspace*

All our online communication takes place in our Slack Workspace. We have a channel for all important topics in which we organize our work. In addition, there are channels for technical questions and a channel for interesting links and projects. Our work takes place almost exclusively in public Slack channels. If you want to join our Slack Workspace, just drop a short email to <info@correlaid.org> or visit our [monthly onboarding call](https://pretix.eu/correlaid/open-onboarding/).

{% content-ref url="/pages/-LvpqYZtOgbjTs0PwRep" %}
[Slack Workspace](/~/revisions/hfepfFy5E9C1WpLCChmV/wiki/communication/slack.md)
{% endcontent-ref %}

#### *Newsletter*

Volunteer Newsletter


---

# 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://docs.correlaid.org/~/revisions/hfepfFy5E9C1WpLCChmV/wiki/hitchhikers-guide.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.