> 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/2026/01/27/typo.md). # typo from a three-body solution perspective, the moment of *noticing* a typo (as distinct from *making* one, which may or may not coincide) is the unknown making \[ room for itself / breathing holes / an articulated joint ] in the place where you're working. this is *always* generative. information under observation is auto-perforating, and that can happen with anyone and anything, anywhere, anytime. :) this is scale-invariant, as in: when you register the burning of the library of alexandria, you register the illegibility of its contents *in place*. that information has better places to be, for your purposes 🌱 or, maybe more precisely, for the evolutionary fitness of relationality from your perspective as a node in the network --- # 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/2026/01/27/typo.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.