> 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/08/28.md). # 20260828 {% hint style="info" %} was drafting a message {% endhint %} (couple hours later) haven't slept yet but I *did* take an hour in a steam room here and I come back with a water+heat thought: locksmith: locks, keys, conditions; statically compiles to liquid, shakes out to a boolean yield-or-react at render-time mechanic: events, tasks (liquid templates), actions; a loop pulls due event runs from event queues, event runs are performed, event runs generate task runs, task runs generate action runs, some action runs submit events to be enqueued as event runs it occurs to me that counter is about routing optionality? a model of runtime loops *in general*. the perceiver is already running it; Counter is an overworld's minimap law of attraction: that which is like unto itself is drawn *but as a computational persistence optimization*, saving on complexity. needs with like needs run in the same need-centers? locksmith: returns logically, returns synchronously, runtime is opaque, no memory mechanic: forks logically, forks asynchronously, runtime is hosted, memory is manual counter: navigates opaquely, cycles ambiently, runtime is ~~baba~~ you, memory is *the map* --- # 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/08/28.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.