> For the complete documentation index, see [llms.txt](https://safedpi.gitbook.io/safeguards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://safedpi.gitbook.io/safeguards/ecosystem-engagement.md). # Ecosystem Engagement The initiative will continue to curate feedback to build additional processes and practices, KPIs and lessons learned through expert and practitioner contributions.The initiative will continue to engage the ecosystem by creating awareness through campaigns (success stories, testimonials, and case studies), workshops and contribution calls. Public feedback will be sought through online forums and open webinars. Special emphasis will be laid on under represented groups. This feedback will be systematically reviewed and integrated to ensure the Framework addresses diverse perspectives and needs. * To read and provide comments on the latest guide, please [click here](/safeguards/about-the-universal-dpi-safeguards-initiative/key-outputs/a-guide-to-building-safe-and-inclusive-dpi-for-societies.md#access-the-guide)​ * Contribute to the framework through our [submission form](https://forms.office.com/pages/responsepage.aspx?id=2zWeD09UYE-9zF6kFubccFvkMg6d0A1KvHKOXEBlk31UQ0JEQ05LWjZGUk0zUTFBOUxXNkRaQ0cxQi4u\&route=shorturl). * Join the community by [sharing your stories, experiences, or case studies](/safeguards/ecosystem-engagement/share-your-story.md) that highlight progress toward safety and inclusion goals. * Participate in community [convenings](/safeguards/ecosystem-engagement/events-calendar.md) to provide feedback, share insights, and engage with others working on advancing DPI safeguards. * Use the [convening toolkit](/safeguards/ecosystem-engagement/convening-toolkit.md) to organize your own events around these themes. --- # 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://safedpi.gitbook.io/safeguards/ecosystem-engagement.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.