> 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/universal-dpi-safeguards-framework/navigating-the-framework.md).

# Navigating the Framework

The Universal DPI Safeguards Framework can be accessed through an interactive knowledge library or this DPI Safeguards Resource Hub.&#x20;

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th data-type="content-ref"></th><th></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Interactive Knowledge Library</strong></mark></td><td><a href="https://www.dpi-safeguards.org/framework">https://www.dpi-safeguards.org/framework</a></td><td>Users can access the interactive knowledge library to explore different scenarios.</td></tr><tr><td>D<mark style="color:blue;"><strong>PI Safeguards Resource Hub</strong></mark>      </td><td><a href="/safeguards/universal-dpi-safeguards-framework.md">Universal DPI Safeguards Framework</a></td><td>Access the Framework through the DPI Safeguards Resource Hub to explore recommendations for each responsible authority at every stage of the DPI life cycle.</td></tr></tbody></table>

***

## Guidance to the..

<table><thead><tr><th width="318">Interactive Knowledge Library</th><th>Universal DPI Safeguards Resource Hub</th></tr></thead><tbody><tr><td>The modular and flexible design of the interactive knowledge library allows user queries to generate canvases (scenarios) for each of the five responsible authorities, across any of the 18 foundational and operational principles, at any of the five life cycle stages to mitigate any of the 13 key risks. The figure below gives a snapshot of the <a href="https://www.dpi-safeguards.org/framework">interactive knowledge library</a>.</td><td><p>The Framework can be explored by starting with the selection of a <a href="/safeguards/universal-dpi-safeguards-framework/responsible-authorities.md">Responsible Authority (R1-R5)</a>. </p><p></p><p>Each Responsible Authority has a specific role to play at every <a href="/safeguards/universal-dpi-safeguards-framework/life-cycle-stages.md">life cycle stage (L1-L5)</a> of the DPI. </p><p></p><p>You can explore what actions each Authority must take to advance the Universal DPI Safeguards <a href="/safeguards/universal-dpi-safeguards-framework/principles.md">Principles (F1-F9, O1-O9)</a>, through processes and practices so as to avoid and mitigate identified risks.</p></td></tr></tbody></table>

<figure><img src="https://2791960348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FM4qpfWbmGu30B3njFAAV%2Fuploads%2FgccMQQy7oWmhH5aPz7v8%2FGroup%20572.png?alt=media&amp;token=5b591c54-c658-41bf-880c-3ea13826e48b" alt=""><figcaption><p>Interactive Knowledge Library</p></figcaption></figure>


---

# 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/universal-dpi-safeguards-framework/navigating-the-framework.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.
