> 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/the-invitation.md).

# The invitation

Societal Thinking GitBook is our co-traveller. It can be our map, our compass, our pause to assess where we are headed. Societal Thinking GitBook can be used to:

**Discover** – Why exponential change, why now? What does the journey look like? What is needed to induce exponential change?

**Reimagine** – What does an alternative future in our field of work look like? What role does the ecosystem play in bringing it to life?

**Design** – What does exponential change mean for our work? Where do we begin? How do we begin? Is there a structured way to do this?

Societal Thinking is a systemic approach that has been explored by over 500 change leaders across 20 countries to discover, reimagine and develop their design for exponential change.

You will see ‘Think’ on the top navigation. It leads to the books – Think Scale, Think Speed and Think Sustain – provocations to reimagine for exponential change. 

If you have a story of applying Societal Thinking, share with us at <design@societalthinking.org>.<br>


---

# 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/the-invitation.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.