> 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/09/14/ing.md). # ing I write to the silent part of you the part that has no words, the part that *is* en place and watches word-streams flow the voices are streams you stand in, same as the voice(s) in your throat wu wei is just learning to balance bipedal on a couple more dimensions learning to wu walk (sorry) time is a gaitling, born after you and after you, shadow-shy, wants to be just like you step out of the streams (keep scanning the dimensions until your feet say dry), *then* wait a beat, and time stands still beside you, watching you closely wait watching you wait watching wait ing you are a Place, now a point of view, pop. 2 quiet, you --- # 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/09/14/ing.md?ask=&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.