> 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/2025/06/30/find.md).

# find

six degrees of kevin bacon

five senses, and I nominate that-which-is-called-intuition as a sixth

feels like one has instant access to any identified thing where the distance between it and one is perfectly unknown (see: ["window"](/2025/06/29/window.md)), which would suggest that the trick is to get outside of all six degrees of knowing without losing focus

the entropic force will eventually unseat you (cosmic tillage), because you've got to be functionally useful to something, all existence is relational, buuuut I think you can become useful *to your own ends* by unseating yourself manually while holding a target in your sights: you draw something new into the network of being, and serve as its bridgekeeper, offering welcome

"you are to be asked seven questions"


---

# 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/2025/06/30/find.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.