> 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` 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 optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.