> 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/09/29/air-plane-plein-air.md). # air plane, plein air my end of the project is fuel source management, I think? managing fuel sources the way a stage manager handles the stage? becoming fuel agnostic, that's the philosopher's stone in this line of work, and you can't tell it apart from fuel-blindness without the history of its construction my mind is fuel-blind, I was born that way; my body is *not*, I was born that way my life has been... clean-cut, I'll say that. it's a very specific kind of clean-room setup. the [A relief strategy](https://a-relief-strategy.com/) document is about incepting a new kind of engine, one that runs on .. on nothing, really. or, on nothing but one's own presence. as one develops one's presence with it, the engine's output develops. by gradually shifting one's presence away from other engines to *this* one, one effectively becomes one's own energy source. the *fact* of qualia is evidence of the engine running; indistinguishable from qualia being fuel-filtering information, without the history of the engine's construction. --- # 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/09/29/air-plane-plein-air.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.