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