> For the complete documentation index, see [llms.txt](https://marsdd.gitbook.io/datatrust/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://marsdd.gitbook.io/datatrust/trusts/design-principles.md).

# Design Principles for a Civic Digital Trust

Establishing a civic data trust involves making many choices: Who should the trustees be? How are they selected or elected? How do they make decisions? What decisions do they have authority to make? How are decisions enforced? How are assets managed? What roles do governments and experts play? What laws apply? How can different laws that apply to different stakeholders be reconciled? How can citizens and stakeholders have their voices heard?

If aspirations provide a north star, design principles provide guidelines for making difficult choices. They can be useful for both establishing a civic data trust and for operating it. Design principles are most useful when they are specific and measurable. There should be no more than seven principles or they become too difficult to remember and to apply.

Based on a literature review, we provided participants in the civic digital trust workshop with a draft list of design principles. Participants added to the list and then voted on the principles they thought were most important. The top four principles identified by workshop participants were to:

1. Ensure transparency of the algorithms to understand their uses and impacts to users
2. Enable open dialogue and education around data sharing and uses
3. Ensure oversight and controls for data sharing
4. Provide open mechanisms for consent

Other principles that were considered by workshop participants, but not ranked as most important, included:

* Enable citizen participation and consultation in how their data is used
* Empower citizens to control access and use of their personal data 
* Protect the integrity and confidentiality of data against unauthorized and unlawful uses
* Minimize the collection of personal data
* Allow for user participation to enable the right to be forgotten, accuracy of information, and consented use of data.
* Improve accountability for uses of data
* Improve transparency
* Not sharing data is an equally viable and desirable choice 

## Have Your Say

What principles are most important to you? Complete this one survey question to have your say:

{% embed url="<https://www.surveymonkey.com/r/WT9WP6C>" %}

Here are the survey results:

{% embed url="<https://www.surveymonkey.com/stories/SM-J7BDBKJ8/>" %}


---

# 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://marsdd.gitbook.io/datatrust/trusts/design-principles.md?ask=<question>&goal=<endgoal>
```

`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.