> 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/05/30.md). # 20260530 type-based reasoning feels weirdly hollow, and I'm putting it on file because I've never seen this discussed. or described. type-based reasoning is like reasoning with pipe, which is .. not unusual in the worlds I come from, building *relays* is a normal part of playing host-to-hosts, but it bears reminding the self that it *is* substantive. the felt sense of substantiveness is deferred to the guest. to apply it *here* is a manual operation, like checking into a room in your own hotel. deferral of the experience means you gotta elect it to experience it personally. doable. :) --- # 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/05/30.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.