> For the complete documentation index, see [llms.txt](https://johnkazer.gitbook.io/future-proof/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://johnkazer.gitbook.io/future-proof/actions-for-future-proofing/mind-sets-for-tackling-the-future.md).

# Mindsets for tackling the future

This section is intended to highlight some reasoned ways in which you can develop a mindset which can make dealing with the 5 stages of engagement possible. My approach to change is not to provide tools by which the process might happen, but to enable you to think a bit differently in the first place and more naturally tackle the future yourself.

Implicit in the following are the personality dimensions Control/Uncertainty and Settled/Creative.

First-off, an introduction to the concept of [Becoming Future Proof](/future-proof/actions-for-future-proofing/avoiding-the-future.md).


---

# 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://johnkazer.gitbook.io/future-proof/actions-for-future-proofing/mind-sets-for-tackling-the-future.md?ask=<question>&goal=<endgoal>
```

`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.