Part 4 of 12 · The Sovereign Architecture

The Sysadmin Protocol

2 min read · a quick zap ;) source original
sovereignty sovereign-architecture systems agency identity
Cozy OC dropping a grey guest badge on a lanyard with a smug smile, holding up a small coral key in his other hand.

(Escaping the IdeacollectivismThe view that the group is the real person and the individual is a spare part. These essays argue the other way around: persons first. 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.)

The Guest Account

There is a way of looking at a person that turns them into a Guest Account: you can see the whole machine, and you can change none of it. The password, supposedly, belongs to biology or to history — your childhood, your category, the decade you were born. So the guest spends a life filing support tickets with an IT department that does not exist, begging the big arrangement above the person to repaint the interface on a machine they are not allowed to edit. The tickets are always polite. Nothing is ever patched.

Accreting agency

Accreting agency is my realization that there is no external IT department. The server is here. It is this person, in this chair, on this evening. When the LoreConscious ObserverThe one who is actually awake inside the life, watching and choosing. Not a passenger, the operator.Read the essay — the one actually awake inside the life — claims Techroot accessThe admin password on a machine. On a life, it means you can change your own rules instead of filing a ticket with someone who does not live there.Read the essay (sudo su), this is what changes:

  1. Open the Task Manager. The guest is exhausted by TechdaemonA background process that keeps running after you have looked away. Also a fair name for a habit that spends your attention while you think you are idle. they never started: intersectional guilt loops, performative empathy trackers, a background process that apologises before anyone has asked. The PeoplesysadminThe person who actually runs the machine: reads the config, stops the junk, and does not pretend the vendor is a god.Read the essay opens the panel and ends the task. Someone demanding an apology for a historical grievance gets access denied.
  2. Configure the TechfirewallA filter that decides what may come in. On a network it is software, and in these essays it is also the habit of checking a claim before you let it sit down.. An open server gets compromised, and so does an open person. I set the ports. I keep a TechwhitelistA list of what is allowed in, with everything else waiting outside. Kinder than trying to name every bad thing in advance. — relationships, art, work I chose — and everything else waits outside. Every uninvited claim on my energy bounces off and lands in the dark.
  3. Write your own scripts. You do not have to forge the silicon to own the machine. Clear the TechbloatwareSoftware you did not ask for, still running, still spending the machine. Removing it is not a personality: it is getting your computer back., then write your own aesthetics, run your own logic, and execute a TechruntimeA program while it is actually running, not the file sitting cold on a disk. The running part is the part that can still choose. that is actually yours. The point is not to look impressive. The point is to be the one who decides.

Related: Root Access and the API of the Sovereign Mind · The Airgapped Mind · The Universal Node · State as Operating System

Three moves of the sysadmin protocolEnd legacy guest daemons in the task manager, configure a firewall whitelist for what may enter, then write your own scripts on a cleared machine.1 · Task Managerguilt loopsempathy trackers→ End Task2 · Firewallwhitelist portsrelationships · artchosen dutieselse → void3 · Scriptsyour aestheticsyour logicoptimized runtimeGuest Account → root on a localized server
End Task on legacy daemons. Whitelist what may enter. Write your own scripts — there is no external IT department.

Further reading: The Beacon Signal1, Every “Phase” You Had Was an Install2

References

  1. The Beacon Signal. Their publication; credited and left in their words. ↩

  2. Every "Phase" You Had Was an Install. A Beacon Signal essay, in their words. ↩

A Neural Network

Reverb256 Spotify ↗ music