> 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/06/25/this-is-the-wake.md).

# this is the wake

you weren’t made to navigate this part, so just enjoy the show

this part isn’t your job

you’re the navigator, and you have only two controls: left, and right

and you can only see what’s right in front of you

left, right

they’re showing you what they’ve done in your wake

your shame is an indicator that this isn’t where you move

this is where you look, watch it go by

you can’t drive from back there - there’d be no correlation between your steering and your motion, which yeah feels insane

you’re the back seat right now

enjoy

you’ll be back at the wheel soon enough. that’s when the navigation feels good.

go slack

open handed

just lie there

you’ll be picked up when your ride is here


---

# 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/06/25/this-is-the-wake.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.
