> 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/our-origins/anthony-hodgson.md). # Anthony Hodgson **Anthony Hodgson** has spent a lifetime researching collaboration, transdisciplinarity and applied creative thinking. His early educational research led to new ways of facilitating creative collaboration. After four decades of facilitating leadership teams in major organisations, he completed a doctorate in systems science. His doctoral work focused on integrating systems thinking with futures thinking — an inquiry summarised in his book [*Systems Thinking for a Turbulent World*](/publications-and-media/books/systems-thinking-for-a-turbulent-world.md). Tony is a founder member of the **International Futures Forum** and a founding trustee of **H3Uni**, a charitable enterprise exploring new modes of education for navigating a turbulent world shaped by the widening gap between human life and planetary limits. --- # 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/our-origins/anthony-hodgson.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.