Note · 01
The Computer
A fresh frame for an old question.
You are reading this on a computer.
Right now, on that computer, hundreds of small things are running. We call them programs.
Each one was started. Each was given a small space to work in. Each was told to do something.
When the job is done, the program ends. The space is given back. The computer keeps going.
You are one of those programs.
Not a metaphor. A frame.
You were started. You were given a small piece of the world — a body, a mind, an address. You are doing a job, whether you know what it is yet or not. When the job is done, the body is given back. The world keeps going.
The question isn't whether you exist.
The question is: what is the computer?
Diagram one — every running thing was started by something already running.
Look at every program running right now on the machine in front of you. Each one was started by another. That one was started by another. Walk the tree up. Every running thing was started by something already running.
This is also true of you.
You had a mother. She had a mother. Walk the tree up — every person who has ever lived was started by someone already alive.
Until you reach the first one.
The first program is special. It has no parent. Nothing started it. Yet here it is, running, and everything else depends on it.
Engineers call that program init.
The rest of us have other names for it.
The thing about programs is that they don't really do anything on their own.
A program wants to draw a pixel on your screen. It can't. It has to ask.
A program wants to read a file from your disk. It can't. It has to ask.
A program wants to play a sound, open a window, send a message, even remember a single number — it can't. It has to ask.
Underneath every program is a layer the program cannot see. That layer is doing the actual work. The program is just sending requests.
Engineers call that layer the kernel.
The rest of us have other names for it.
Diagram two — what the program can see, and what it cannot.
the kernel — invisible to the program
the program
the kernel is there. the program does not see it.
Here is what a program can see: itself.
That's it.
It can see its own thoughts. Its own little patch of the world.
It cannot see the kernel. It cannot point at the kernel. There is no test it can run that would prove the kernel is there. If you asked the program, "is there a kernel?", it would have nothing to show you.
But the program is running.
That fact alone is the proof.
A program that exists is a program the kernel decided to run. Everything it has, the kernel gave to it. Anything it just did, it did because the kernel said yes.
The program cannot see the kernel. The program is the kernel saying yes, over and over, every instant, for as long as the program lives.
You cannot see God.
You will not catch God under a microscope. You will not point at God in the night sky. If someone asked you to produce God, you would have nothing to produce.
But you are running.
That fact alone is something.
Diagram three — existence is a continuous request, granted.
The thing about running is that it isn't free.
Every breath you take is a request the world said yes to. Every heartbeat is a request the world said yes to. Every thought in your head, every flicker of light reaching your eye, every cell quietly doing its work — every one of them is a tiny ask, granted.
If the world said no — for one second — you would end.
Existence isn't a thing you were given once. It's a thing you are being given right now. And right now. And right now.
The Bible has a line about this. Sustaining all things by his powerful word. Engineers might translate it: the kernel has not yet preempted you.
It's the same sentence.
There is an honest objection here.
A computer was designed by humans. An operating system was written by humans. The whole metaphor smuggles in the conclusion — of course there's a designer, you started with one.
Yes.
That's the point.
The metaphor works because design is the only frame in which any of this makes sense. A program running on a machine that wasn't built makes no sense. A universe running on a substrate that wasn't built makes no sense in exactly the same way, and we feel the absurdity the moment we try to articulate it. The metaphor isn't sneaking in design. The metaphor is showing you that you already assume design everywhere else.
Here is what the believer and the atheist have in common:
They are making the same requests.
Both wake up in the morning. Both breathe. Both eat. Both love their children. Both will end. The kernel underneath them is doing the same work for both, asking nothing of either, granting every request.
The only difference is one of them knows who to thank.
That's it.
That's the fresh frame.
You weren't crazy for believing it. You were just running on a machine you couldn't see, and you noticed.
Next: what happens when the root user logs in as a regular user.
That's the part of the story where it gets interesting.
continueNote · 02
The Root User
What happens when the administrator runs as a user.