> For the complete documentation index, see [llms.txt](https://www.h3uni.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.h3uni.org/h3uni-foundation-archive/purpose/our-organism.md). # Ideas for a Third Horizon University Society and culture have been held back by over-specialisation and restriction by “divide and conquer the mind”. In contrast, transformative learning requires an integration and synthesis that enables the power of interacting insights. Our field for transformative learning is conceived in four organically interacting principal elements: An **Ideas Collegium** that gathers and stimulates creative thinking and research into issues and innovations of the Anthropocene, giving power to what is possible. A **Virtual Campus** for inclusive and supportive dialogue, discussion and dissemination of understanding. A **Resource Library**, the maintained Seedbank of active methods for transformative change. A **Learning Faculty** for study, transmission and application of methods in the many transformational journeys that are being contemplated and embarked upon. These four elements are in continuous interaction and inter-stimulation, as in this illustration: --- # 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://www.h3uni.org/h3uni-foundation-archive/purpose/our-organism.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.