> 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/06/19/flakey.md).

# flakey

> I like to have things rock solid so I can just leave them and relax, if something is flakey I can't really forget about it

makes sense. I think I'm used to my neurology being flakey as a baseline, so as long as the external flakey thing is something that I'm skin-to-skin with it's the same as baseline for me, doesn't cost me anything I haven't already optimized myself to pay

***

"skin-to-skin" is important. I only have so much skin, and I gotta be able to move, on account of the aforementioned flakey neurology. there's something like a fixed-point optimum here, for me, the place where my strange attractor of a self centers, and I think I'm there. I test every morphism I can find, and this one has held through all of them. and I'm gay and autistic and ex-religious and transconscious and accidentally a CEO and polyamorous and I didn't know any of those things until it was too late to brace for the knowing


---

# 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/2026/06/19/flakey.md?ask=<question>&goal=<endgoal>
```

`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.
