> For the complete documentation index, see [llms.txt](https://4bcplaybook.clearglobal.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://4bcplaybook.clearglobal.org/1.-introduction/1.3-acknowledgements.md).

# 1.3 Acknowledgements

This playbook was created as part of the 4 Billion Conversations project. The project is being run by CLEAR Global and is funded by Deutsche Gesellschaft für Internationale Zusammenarbeit (GIZ).

We would like to say thank you to the many people who helped with this document, including:

* Natural Language Processing (NLP) researchers Dr. David Adelani, Dr. Duygu Ataman, and Dr. Mathias Müller for sharing their insights and giving feedback, and
* the many partners that shared their time, knowledge and feedback with us, including Malaica, Pattan (Pakistan), Families Fit for Children (Uganda), and Reach a Hand Uganda.

<br>


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://4bcplaybook.clearglobal.org/1.-introduction/1.3-acknowledgements.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
