> For the complete documentation index, see [llms.txt](https://simprints.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://simprints.gitbook.io/docs/introduction/audience.md). # Audience Our open-source initiative at Simprints invites developers, partners, advocates, and all those passionate about addressing global challenges to join our collaborative community. * Developers keen on contributing code and expertise will find a welcoming environment, offering resources and platforms for seamless collaboration. * Our partners, whether from NGOs, healthcare, or government sectors, are encouraged to engage closely with us, tailoring our technology to suit their specific needs. * Advocates aligned with our mission to promote transparency and equity in global development are vital in amplifying our impact. * We also welcome everyone from researchers, policymakers, community leaders, and individuals dedicated to creating positive change. Together, we aim to foster a diverse ecosystem driving scalable solutions, ensuring vital resources reach those most in need. Join us in this transformative journey towards a more equitable and empowered world. --- # 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://simprints.gitbook.io/docs/introduction/audience.md?ask=&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.