> 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/09/03.md).

# 20240903

Pick two to keep:

* Where you're from
* Where you're going
* Who you are

Only by looking away from one can you maintain the definition of the others:

* For any two states, any "before" and any "after", there is always a path. You can take that path, but who knows who you'll be on the other end. :D
* You can keep your current self-definition and your current concept of your origin. Those two you can keep. Gotta let go of where you think you're going, though.
* Or, you can keep your current self-definition *and the destination you have in mind*, and you'll get there, but you gotta let go of where you came from.

***

I perceive time to be slowing. Maybe. "Time slowing down" is how this is normally phrased, "slowing down" to the speed of those slow summer days people recall from childhood. "Slow" in the sense that the next day (or even the next hour) feels far, far away.

I'm not sure that "time slowing down" is at all accurate for what’s happening to "time" here, relative to "me", but it's what people say for this feeling. :)

Yesterday I had a specific moment where I felt everything — *everything* — in a sort of holding pattern. Like the entire universe showed itself to me as a simple-yet-adaptable-yet-unchanging-unless-prompted loop, in the way that a heartbeat is exactly such a loop. Or the touch of water on the sand in the sea: in, and out, as long as you please. Suspended, but animate.

To sample the vibe, please google "cinemagraph". It is exactly what I'm describing.

I feel very distinctly like there is nothing to do "next". Typically I'd at least have a small voice urging me toward code or something. But no, there's nothing. It's strange, and *comfortable*.

***

*You have adjusted the course of the ship. The rest is between the ship and the wind. :) Enjoy.*

*This is a curriculum for presence.*


---

# 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/09/03.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.
