> 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/projects/project-team.md).

# For the project team

{% hint style="warning" %}
This section is currently under construction. Come back to it in the future if something is missing that you're looking for and let Leo know what you are missing the most so that we can prioritize!
{% endhint %}

In this section, you'll find information for project team members about what participating in a CorrelAid Datat4Good Project means and what your concrete tasks are throughout the project. In addition, this includes some thoughts about your self-image and role as Data4Good data scientists, best practices for projects with regards to code quality, collaboration, deployment etc.

Always coordinate with the other project team members and remember: your project team lead and project coordinator are there to help and support you!


---

# 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/projects/project-team.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.