> 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/code-of-sharing.md).

# Code of sharing

Societal Thinking was incubated at [EkStep Foundation](https://peopleplus.ekstep.org/) between 2016-2023 and was shared as a public good under the [Creative Commons License, CC BY SA 4.0 International](https://creativecommons.org/licenses/by-sa/4.0/). The Centre for Exponential Change (C4EC), established at C4EC Foundation in 2024, contributes to further the application and evolution of Societal Thinking as per this license.

Creative Commons licenses help build a more equitable, open, and innovative world that allows greater collaboration, creativity, and – most importantly – access. Users are permitted and encouraged to create and share derivative works such as a read-aloud, translation, or format adaptations, while adhering to the requirements of this license. 

More at [societalthinking.org](https://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 dynamically 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/code-of-sharing.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 `build a script that syncs our docs to a CMS` 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.