> 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/2025/11/12/yours.md). # yours something in you is modeling the world I'm autistic enough to see my own process as it happens, as clearly as I see anything with my eyes; you might not be as lucky, in this specific way if I catch a song on the off-beat first, my structural model of the song is completely different than the artist's intent unless they're jacob collier probably "only murders in the building" - I had to *watch* that show to get the context I needed to clear the discomfort of syntactic ambiguity. does the building only have murders? are these particular murders the only ones in the building? these are all completely different stories, and none of them match the content - the *referent* (a thing which is restricting itself to only covering murders in the building, turns out) is not derivable from the title alone, and I'm autistic enough that the title created physical discomfort for me, haha. not an eigenprotocol, expensive to exit. anyway if you're uncomfortable for reasons that don't have a clear relief path, some part of you may have built a model that makes real predictions that really don't work yours.fyi is for figuring that out, among other things (syntactic ambiguity intentional, all parse trees valid) :) --- # 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/2025/11/12/yours.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.