> For the complete documentation index, see [llms.txt](https://docs.data.ca.gov/california-open-data-publishers-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.data.ca.gov/california-open-data-publishers-handbook/reference/acknowledgements.md).

# Acknowledgements

We have had a number of people help with the creation and feedback on this handbook. This wouldn't be possible without their help.

First, many thanks to the student team that kickstarted user research through Stanford's CS184 (Bridging Policy and Tech Through Design) class: Emily Bunnapradist, Jenn Hu, and Sejal Jhawer. Thank you for bringing fresh eyes and design thinking to the open data publisher's journey and this resulting handbook.

And thank you to all those that provided their subject matter expertise and feedback as we developed the handbook (with apologies if we missed anyone): Benjamin Brezing, Colin Stevens, David Altare, David Harris, Jarma Bennett, Karen Henderson, Kate Spiess, Mahesh Gautam, Michael Tagupa, Ping Zhong, Rafael Maestu, Rodney Garcia, Sam Hayashi, Scott Fujimoto, MD, MPH, Tuba Demir Dagdas, Will Wheeler, and Yanyi Djamba.


---

# 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://docs.data.ca.gov/california-open-data-publishers-handbook/reference/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.