> For the complete documentation index, see [llms.txt](https://wiki.societalthinking.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.societalthinking.org/what-is-st/the-design-principles.md).
# The design principles
Design principles ensure every design decision is intentional, consistent and aligned with the larger purpose of inducing positive exponential change. Designing for exponential change with the Societal Model is a co-creative process. It engages many ecosystem actors such as designers, architects, influencers and more. Design principles offer a shared language for these actors to harmonise their efforts and decisions.
Design principles are core propositions to help bring to life the key elements of the Societal Model such as societal networks, co-creation ecosystems and open infrastructure. These will be introduced and applied at relevant stages of the design journey.
---
# 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://wiki.societalthinking.org/what-is-st/the-design-principles.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.