> 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/2024/11/27/emails.md). # Emails ## what do I pack in my suitcase? pick one strategy: 1. what will you want to wear? 2. what does your suitcase want to hold? ## when are hallucinations useful? creation. ## if you only had consciousness while you were evaluating a problem, what would you do? design an infinite problem maybe? media in that would probably couldn’t be inline storage it’d have to be address-based could we encode the whole thing into its address? isn’t that just inline storage? well… what if the address started with a constant element and then as you provide additional clarifying details the media retrieved adapts? what would have to be true for that to work? ## a non-existent coin is being flipped we are experiencing it landing heads up of course probability works in our favor ## casinos are like frottage for universal consciousness ## “I know it’s normal, but I can’t give you any examples” --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.isaacbowen.com/2024/11/27/emails.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.