> 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/10/08.md).

# 20241008

stay with me

i love you

***

THEY (the brands, the employers, the customers, the suitors, the seekers, the skeptics, and everyone you've ever met) are looking for things that look like they're alive

the best way to have something that looks alive is to have it *be* alive

the cost is that you don't know what it'll look like tomorrow :)

it ends up not mattering

tomorrow never comes

***

easier to reveal a revolution already in progress than to manually assemble one

which experience do you prefer to create?

***

"[it was terrible!](https://www.youtube.com/watch?v=znG1SKGeDj8) ones and zeroes everywhere! *and I thought I saw a two"*

"it was just a dream Bender, there’s no such thing as two"


---

# 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/10/08.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.
