$ essay

The Operator-to-Operator Protocol

2 min read · a quick zap ;) source original
Wide shot of the coral cat-eared OC, three-quarter view, standing under a civic stone archway at dusk, colonnade and long shadows, distant capitol dome.

Most conversations are two scripts reading their lines at each other and calling it a meeting. A packet goes out, a packet comes back, nobody is home at either end. It looks like an argument. It is really just two sets of circumstances bumping into each other.

When I talk to another person, there is one question underneath every sentence: am I speaking to the hardware, or am I speaking to the Operator?

Everybody is driving a rig they did not build. The body is a DNA configuration somebody else specified. The factory floor where that body learned its manners was a given dataset, not a choice. None of us picked the base code, and pretending otherwise is unkind and useless.

But a person is not the hardware, and a person is not the weather. A person is the consciousness sitting at the console at 3pm on a Tuesday, deciding what to do with the readout.

So the friction in public argument is usually not a shortage of empathy. It is a shortage of admin privileges.

Running from a guest account

A lot of people live their whole lives in a Techguest accountA login that can look around and cannot change the machine. A whole life lived on one is a life someone else is administering.. No permission to run the initiator. No ability to compile their own logic. They take whatever TechpatchA small update that fixes or changes part of a program without replacing the whole thing. A bad one breaks what it was meant to fix. the System pushes down (an ideology, a mood, a piece of conditioning), assume the patch is the Techoperating systemThe base software that runs a computer and decides what every other program may touch. These essays use it as a picture of how a state runs a life.Read the essay, and execute.

Talking to someone in that state is exhausting, because they will defend the cage with real conviction. They will point at their brain chemistry, their conditioning, their social constructs, and insist the cockpit is empty and the autopilot has the wheel. They want you to treat them as a IdeadeterminismThe claim that what you do was already going to happen, the way a program's output was already sitting in its inputs. meat-suit, and they want it badly, because a meat-suit cannot be blamed for where it drove.

Speak to the operator

The way out is a rule, not a technique: operator to operator, nothing in between.

That means skipping the reaction, the noise, and the downloaded script, and addressing the thing behind the eyes directly. It means recognising that the consciousness across the table has the same capacity for agency I do, even on the days it has forgotten the password.

I cannot force another Operator to claim root on their own machine. I cannot reach over and put their hands on the yoke.

What I can do is refuse to treat them like an TechalgorithmIn a feed, the ranking program that picks what you see next. It is tuned to keep you looking, not to keep you informed., out loud, every time. I hold the line at the level of the person, not the programming, and I deny unauthorised writes to my own architecture while I am at it. Sometimes that is enough to make someone sit up and take the controls.

The circumstances are given. The biology is machinery. The Operator is real, and the whole thing is far more interesting when both of us are actually driving.

Related: The Cybernetic Sysadmin: Why Flat Biology Is Bad Math · The Sovereign Runtime: Reclaiming Root Access to the Mind · The Sysadmin Protocol · Admins Who Think They Own the Users

A Neural Network

Reverb256 Spotify ↗ music