> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2024/11/27/imagine.md).

# Imagine

You know how when you're skydiving through rain there are vertical streaks of water alongside you? (Don't worry about if that's true or not. Just imagine it.)

Imagine you had a little projector strapped to your forehead, and it was projecting onto the sheet of water-streams like they were a projection screen. (Don't worry about if that's plausible or not. Just imagine it.)

Imagine that the rain-screen projection in front of you, as you continue your dive, shows a moving image. You recognize it as a movie *about you*. You're doing something ordinary in the movie. It plays by quickly. Skip ahead a little bit and you've figured out that if you tilt to the left in your skydive, good-feeling things happen to the you-in-the-movie, and if you tilt to the *right* the you-in-the-movie has a bad-feeling time. (Thank you.)

Imagine getting so into it (this is an infinite rainy skydive, don't worry about it, maybe it's one of those indoor deals, anyway, ) that even though you only have the left/right good-feeling/bad-feeling controller mapped, you start to feel like the decisions you-in-the-movie was making and carrying out *are yours*. And some ownership is reasonable, but *most of it* came after your decision to roll left or roll right, andddddd the way it played out onscreen is whatever would make sense for it to be given that good-feeling/bad-feeling choice.

Neat, right?


---

# 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.isaacbowen.com/2024/11/27/imagine.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 `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.
