> 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/28/fibrous.md). # fibrous I think I make things that are already at their own K-complexity. Like, you *can* summarize them, but the summary will be unusable for the thing's own ends. Least-fixed-point construction. Actually this explains why I can't do marketing? "The thing's own ends" are only knowable by using the thing, which means any summarization is lossy, and I can't do lossy morphisms. Point of fact, I only do conductive morphisms, i.e. a relay chain of the same 3D fiber through everything, the same fiber you rode in on. Summarizing a prospective journey is, to me, a contradiction in terms. A 3D fiber explores 3D fibration-space (if one of those three dee's is a control port with network feedback, in a nested token ring kind of way, 2+1 dee's, though that +1 itself unfolds as far as you care to look), but in dramatic-as-in-*dramatis* terms in such a scenario the fourth wall is *intrinsically* broken. Think: how do you think you got in there in the first place? A door, if well-formed. A crack, if not. The defining fact of a space is your entrance to it; the defining factor of a space is your exit from it. To me, a safe space is one where the manner of your entrance is the primitive everything else can be built from — *including* your exit. (I've come to conclude that existence is a safe space.) --- # 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/06/28/fibrous.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.