> For the complete documentation index, see [llms.txt](https://charity.childsafetyfund.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://charity.childsafetyfund.org/governance/leadership/partners.md).

# Partners

Specialists who lead child-safety strategies alongside the CSF team.

Child Safety Fund (CSF) brings experienced practitioners into its team as **Design Partners**. Each Partner leads a defined area of strategy and programming, contributing expertise, relationships, and program leadership.

## Working together

Design Partners identify child-safety needs, develop strategy, lead program design, cultivate funding relationships, and guide implementation. Their designation establishes the scope of their leadership within CSF.

CSF supports this work through research, design capacity, grant development and administration, implementation support, and outcome evaluation. Together, Partners and CSF develop approaches, test them in practice, and use the findings to improve the work.

## Mindfulness

[**Zana Williams, Design Partner, Mindfulness**](/governance/leadership/partners/zana-williams.md) is CSF's designated mindfulness program lead. She leads work on emotional awareness, self-regulation, communication, and constructive responses to conflict. The [Mindfulness strategy](/strategy/mindfulness.md) describes the purpose, initial pilot objectives, and intended impact.

Zana also leads **Mindful Resolutions**, the planned implementation partner for the initial curriculum pilots.

## Independent organizations

A Design Partner may also lead an independent business or organization. Their leadership role at CSF is separate from that organization's role in delivering activities. Services and funding are defined through separate agreements, with CSF responsible for its charitable resources and institutional oversight.

Mindful Resolutions retains its business, clients, and proprietary curriculum.


---

# 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://charity.childsafetyfund.org/governance/leadership/partners.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.
