> For the complete documentation index, see [llms.txt](https://discover.theiofoundation.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://discover.theiofoundation.org/dcdr-advocacy/about/dcdr-principles/principle-iii-rights-by-design.md).
# Principle III - Rights By Design
{% hint style="info" %}
[**ShortURL**](https://TIOF.Click/DCDRPrinciple3) **| Playbook | Assistant**
{% endhint %}
  
> ## *Leave no policy uncoded behind.*
This DCDR Principle responds to the need for policies and tech to be designed and implemented as one: the former establishes what is to be respected and the latter ensures that the compliance is built in the infrastructure so that users are protected automatically and transparently.
On other words, any protection a citizen or its digital twins are subjected to under a specific jurisdiction should be transparently implemented inside the technology itself, by design.
{% hint style="warning" %}
**REMARK**
Do note that this is a concept that is evidently applicable beyond the domain of technology, which is highly
{% endhint %}
---
# 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://discover.theiofoundation.org/dcdr-advocacy/about/dcdr-principles/principle-iii-rights-by-design.md?ask=&goal=
```
`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.