upstream causes of ordering errors:

[draft]

full title: some possible upstream causes of ordering errors

Things to keep on eye out for that can have a dramatic impact on suboptimal ordering choices (and also it's fine, it's structural, there's a sense in which there is no way to smooth things out and everything happens as it happens)!:

[note: some of these can be quite phenomenological and gathered and quite "p3-able"]

  • "would take infinite time" and "i have no time" [also not enough but need to check "conceptual extremes"]
  • don't have time for “this [like processing something or some direction]”]
  • don't have enough time for “this [like processing something or some direction]”
  • "will take infinity time [and so "must" be skipped]" --- false that “that [like processing something or some direction]” will take infinity time and so must be skipped [but skipping potentially leads to "disaster" until go back]
  • will take forever to do “that [like processing something or some direction]”
  • “it” needs to happen imminently and immediately in the next moment
  • "it" will happen any-second-now

downstream:

  • ...hast, rushing, hurrying, speed, out-of-ordering...
  • "so maybe look and see if X implies an ordering thing or don't/can't do some particular dimension, direction, patch of processing"
  • ... so not worth going over there

for all = patience, should be quiet and smooth as silk if slow trickle

consider:

  • exploring ordering directly
  • sort of object-level, object-level meta protocol, objtect-level meta meta protocol and
  • meta-level meta protocol [this one], meta-level meta meta protocol

*

You might ask, for maybe doing X, if not now, when? If the answer is never, this could indicate an ordering error or possibly an expectation that X is conceptually confused or will spontaneously be addressed, and so on. (This is also an auxiliary practice.)

messy comment from original notes:

look for not yet and make sure that the answer to when? isn't never sometimes turns out the thing dissolves and so when/never don't make sense. but other times this points to an ordering error if it's sort of a thing that one should sort of do eventually. if not never that doesn't necessarily mean "now" of course. maybe some other time. but if the never dissolves before that times comes, in that world where the thing is a thing, then that's probably net good.

383 words · main