> 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/03/19.md). # 20260319 it seems less like we're wired for narrative so much as persistence is probabilistic and narrative is a mnemonic device for navigation without decoherence. it's not the only navigation device though. narratives are examined in terms subject to physical intuition: a plot *twists*, has an arc or three, has holes. if you're a DM, you know that holes are where the interesting stuff happens later. Paddington 2 (2017) was a perfect film: it accommodated all entrance vectors, and landed everyone together with mutually copacetic satisfaction. not the only navigation device though. metafiction and surrealism and continental philosophy jump between projections, sifting for places where a mutation on a secondary or alternate projection does more or other work than possible in the projection of primary identification. (also, Dr Seuss.) foam modeling sticks with R³ as a standing bet that spatial reasoning *is* navigation of probability, and that it holds for any set of three from a pool of dimensions that have seen other navigators. English (though I prefer to think of it as "ing-lish", a place predicated on continued novel verbing of emerging nouns) isn't spoken so much as walked - like I have an English-based body (measure mine with yours) the same way I have a carbon-based body (measure mine with yours), and some expressions are a stretch for me and some things aren't. --- # 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/03/19.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.