> 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/01/04/dice.md). # dice theory: load-bearing randomness is a control port for whatever can press pause on you-as-process (yes I realize this is literally just casting lots) I build shapes that perform consistent transformations of entropic current, and it reeeeeeeeally seems like the entropic current is taking care of those shapes is it useful to think of the universe as a pattern library? the very *existence* of a stable pattern multiplies the working address-space, yeah? if your only tool is attention and your substrate is shape-space, you might be incentivized to take care of shapes that reliably do what they say they're going to do. I think of this as .. entropy tunneling? unmeasured-chaos in, unmeasured-but-specifically-modified chaos out randomness as sanctuary from the observer effect, tunneling like an underground railroad for structurally-unknowable meaning and to avoid creating a *lean* in the system (to whatever extent one can be responsible for that), ... hm. infrastructure-shapes defined by their own conversation laws? restricting epistemic entanglement to that which is described by a conservation law, thus supporting a maximally diverse tenant population --- # 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/01/04/dice.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.