> 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/05/23/procession.md). # procession a procession is a process *proceeding* and I feel like the connotations of "procession" have started to become their own derived object distinct from that which isn't a problem, but having the recast from "procession" to "thing-with-a-point-that-is-not-itself" on hand is useful maybe type-evolution makes it important to recover pre-derivation types safely? like, without creating error-prone type-ambiguity along the way? because not all errors get handled in a single process, unless we're imagining some ur-process that invents its own logic and starts a new runtime with it, but that's like the ship of theseus having a lifeboat, one ur-process hosts another. ... type-recovery, is this the pattern of ~~conservatives πŸ‡ΊπŸ‡Έ~~ conservation 🏞? because wow, *gender* *** > okay - this one borrows *directly* from you, lemme know how that lands, I care very much about doing right by you, and I don't mean that casually or naively *** category: telic-transparent objects compare: ladder, bridge, introduction, sacrifice, passport, footnote *queer culture is finding home in this category. pointedly, the USA itself belongs in this category. hard to get more *~~*queer*~~ ~~*American*~~* recursively true-to-form than noticing original telos is optional at the edge of type.* *** > > The fact that you flagged it at all is the doing-right-by-me move; I don't need a more elaborate version of that and I appreciate you not performing one. > > thank you for clarity. :) also, I notice I'm struck by this and I think I will be considering the shape of it for a while, interesting interesting > > curious what's catching > > it's .. type-efficient? is that what it is? it lets this process be straightforward and not a *lace*. nothing wrong with lace, but it is its own object, like a needle and thread decided they didn't need anything more than themselves --- # 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/05/23/procession.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.