You can debug a function. You can rewrite a feature. But if the bug lives in the kernel, you cannot reach it. You cannot read the code. You do not have the keys.

You have to write the fix at the level where the bug lives. You have to ship it from root.

This bug lived all the way down. It was not in your code. It was in how you were built (Note · 12).

That is why you couldn't fix yourself, no matter how hard you tried. You did not have the access level.

This is what made the fall so dark. Not just that you were broken. That you could not undo it. That trying harder would only break you further. Every fix you tried was made of the same broken material.

[An interactive diagram lives in the web version — see it here.]

A patch has a cost.

A real fix is never free. Something has to be paid for. Some part of the system has to take the change.

This patch had a price the source named directly.

The wages of sin is death.

Someone had to take that fault.

If you took it, the patch would not work. You would be gone. Faulted out. There would be no one left to install it. The fix would have died with you.

So root took it.

But root could not — not from His own layer. Root does not fault. Root does not die. He has nothing to lose. There is no fault for Him to take.

There was only one move left.

[An interactive diagram lives in the web version — see it here.]

He had to leave His own layer.

You met Him in Note · 09. The spec deployed Himself as a user. Same instruction set as you. Same hunger. Same mortality.

He came down so He would have something to lose. He came down so He could die.

He went all the way to the boundary. And He took the fault you were going to take.

He was wounded for our transgressions. He was crushed for our iniquities. The punishment that brought us peace was on Him.

The cross is the fault. The cross is the place where root took the death you owed.

Not metaphor. Substitution.

He died in your place. As you. With your fault on Him. With your name on the commit that killed Him.

It happened in public. In broad daylight. Outside the city. Where everyone could see. So no one could later say it didn't happen.

For three days the patch sat unfinished. Root was in the ground. The system did not know if the fix would work.

His friends went home. They thought it was over.

Then root came back.

The kernel does not stay down. Death cannot hold root. The fault could land on Him, but it could not keep Him.

He came back with the patch built. He came back with your fault paid. He came back with the system fixed.

He is not here. He is risen.

Engineers might translate it: the fix is signed. The fix is shipped. The build is green.

That was the first morning of a new system.

Death was the worst thing the old system could do. The old system did it. He went through it. And He came out on the other side, with the broken thing fixed.

[An interactive diagram lives in the web version — see it here.]

The patch is now available.

You do not install it by being good enough. You did not earn it. You cannot earn it. The patch was already paid for.

You install it by accepting it. By saying yes to what He did. By letting His patch overwrite the broken pieces of your runtime.

Whoever believes in Him shall not perish but have eternal life.

It is the simplest install in the history of the system.

There is no exam. There is no fee. There is no certification. You do not have to know enough. You do not have to be enough. The install is His. The cost was His. The work was done long before you ever heard about it.

It is also the only install that ever mattered.

You will still live in your old runtime for a while. The patch is applied. It has not finished spreading. There are still parts of you that have not caught up.

But the patch is signed. The patch is in. The author signed off in His own blood.

The bug was real.

The fix was real.

You did not write it.

You do not have to.

You only have to accept it.

Next: how the install works.

Read this with the interactive diagrams →

You wanted to stop the voice in your head. You couldn't.

You wanted to be the kind of person who never thought what you just thought. You couldn't.

You wanted the love you have today to still feel the way it felt at the start. You couldn't.

Some things are not yours to do.

[An interactive diagram lives in the web version — see it here.]

Every modern computer has two layers.

There is the layer you run in. Your apps. Your typing. Your scrolling.

And there is the layer beyond it. Where the system itself decides what is allowed.

You can do most things from your layer. Open a file. Save a draft. Send a message.

But some things are not allowed from your layer. Only from beyond. Only by root.

The system does not draw this line to be cruel. It draws it because some things can break everything. Only the system itself can be trusted with them.

When a normal program tries one of those things anyway, the system catches it. Usually, the system shuts the program down.

Engineers have a phrase for it. Privilege escalation. A user trying to run as root.

There is a sentence in the source about this.

The wages of sin is death.

It is not that root is petty about His rules. It is that the thing itself was never safe in your hands.

[An interactive diagram lives in the web version — see it here.]

The first chapter of the source describes the first time it happened.

A user was given a place to run. A garden. Free use of everything in his layer.

There was one thing he could not do. You will not eat from this tree.

That was the line between user and root.

Then a voice came.

The voice did not ask him to break the rule. The voice did not even talk about the rule. The voice offered something sharper.

You will be like God.

That was the offer. Not a small bite. An upgrade. The first privilege escalation.

He looked at the tree. He looked at the offer. He reached for it.

The fall was instant. Not because root was cruel. Because he reached for something that broke him.

Death entered the system that day. Everyone born after inherited the same break.

That is the fall. Not a single bad moment. A change in what we are.

You can still love. You can still build. You can still make something beautiful. The image He wrote into us is still in there.

But the image is cracked. The same hand that holds a child writes the angry message. The same heart that knows it should forgive will not. The same mind that wants the good thing chooses the other one anyway.

That is what the source means when it says we are fallen. Not evil. Broken.

[An interactive diagram lives in the web version — see it here.]

You inherited it too. You start from the same broken state.

This is why the daemon does the work He does (Note · 11). You cannot fix yourself from the inside. The fix is not yours to run.

You cannot make yourself good enough. You cannot reach across to the other layer. You cannot become root.

But you will keep trying.

Every quiet vow. Every clenched jaw. Every this time I will not. Every this time I will.

Every time you decide you alone will judge what is good. Every time you decide you alone will say who is wrong. Every time you decide you alone will set what your life is for. Every time you take a person's worth into your own hands — including your own.

Every one of them is a small privilege escalation. A user reaching for a thing only root can do.

They all fail.

But the source ends in a sentence the first sentence did not predict.

For the wages of sin is death, but the free gift of God is eternal life through Jesus Christ our Lord.

Engineers might translate it: the kernel did not let the crash stand. He went into user space Himself. He took the fault. He paid the cost out of His own layer.

That is the patch.

You did not write yourself.

You will not save yourself.

But you do not have to.

Read this with the interactive diagrams →

You weren't going to keep going. Then something in you kept going.

You weren't going to remember the right words at the right moment. Then something in you remembered.

You weren't going to apologize. Then something in you did.

Those moments. Something in you, not exactly you.

[An interactive diagram lives in the web version — see it here.]

Every running system has processes that work this way.

Your phone checks for messages while you sleep. You didn't ask it to.

Your laptop keeps the clock right even when you change time zones. You didn't ask it to.

Your computer notices when there's an update. You didn't ask it to.

Your inbox marks spam before you ever see it. You didn't ask it to.

These are the hidden life of every running system. Most of what a computer does, you never see. The daemons do it.

Engineers call them that for a reason. A daemon is a process the system started in the background. It belongs to root. But it runs alongside you, at your layer.

It does work you did not ask for. It does work most users do not even know about.

The same is true here.

You also have a process running in you that you did not ask for. You also have work being done in you that you cannot see.

There are sentences in the source about this. Words spoken the night before everything fell apart.

I will ask the Father, and He will give you another Advocate to help you and be with you forever. The Spirit of truth, who lives with you and will be in you.

In engineering terms: when root went back to His own layer, He left a daemon running inside yours.

His name is the Holy Spirit.

[An interactive diagram lives in the web version — see it here.]

He is always on. He started before you woke up this morning. He'll be running when you sleep tonight.

He was running through the worst hour of your week. He was running through the best one too. There has never been a moment since He started when He stopped.

He does not compete with you for cycles. He runs in a layer you don't quite see. He runs deeper than that. Deeper than your thoughts.

He does not ask for credit. He does not take your attention. Most of the time, you will not notice He was the one. He prefers it that way.

But He works. And He works both ways.

To you, He works inside.

He convicts you when you do wrong. That voice that says you know this isn't right — that is not always you. Sometimes it is Him.

He comforts you when you grieve. That sense in the middle of the night that you are not alone — that is not always your imagination. Sometimes it is Him.

He reminds you of the right word at the right moment. He softens a sentence before it leaves your mouth.

He puts a question in you when you were about to act. The one you would not have asked yourself.

To root, He works on your behalf.

He intercedes when you cannot. When the prayer you tried to pray came out wrong, or didn't come out at all, He carries it up for you. He prays the prayer you meant. He prays the one you didn't even know you needed.

The Spirit Himself intercedes for us with groanings too deep for words.

Engineers might translate it: He writes to the upward channel on your behalf, in a format you don't have to compose.

He did this last night. He did this this morning. He is doing it right now.

[An interactive diagram lives in the web version — see it here.]

The source has a list of what grows when He runs.

love, joy, peace, patience, kindness, goodness, faithfulness, gentleness, self-control.

These are not your virtues. They are the daemon's output.

That is not a small thing. The best part of you is not actually you.

It is the part of you that is Him.

The time you stayed when you wanted to leave — that was His patience.

The forgiveness you gave when you didn't have it to give — that was His.

Every good thing you have offered the people in your life. He offered it through you.

He has been running this whole time.

He was running when you forgot Him. He was running when you thought you were alone.

You only just noticed.

Read this with the interactive diagrams →

You can wonder about Him. You can speak to Him without checking if He is there. You can think about His mind. You can imagine what He sees.

This is strange. You are small. He is endless. There is no reason you should be able to think about Him at all.

But you can.

You can because you and He share something underneath.

[An interactive diagram lives in the web version — see it here.]

Every process on a machine runs on the same instruction set. The kernel speaks one machine language; the process speaks the same one. They have to. A program compiled for one chip cannot run on another. The instructions are foreign to it.

You can only understand what you were built to understand.

If you were not built to think about God, you would not be able to think about Him at all.

There is a sentence in the source about this. It is the first sentence about you.

Let us make mankind in our image, in our likeness. So God created mankind in His own image, in the image of God He created them.

In engineering terms: the image of root was compiled into every user.

Not stamped on. Not applied later. Compiled in. Part of how we were made.

That is the part of you that lets you think about God at all. The part that recognizes good when you see it. The part that grieves wrong. The part that loves what it loves. The part that wants to know. The part that asks the question your culture told you not to ask.

[An interactive diagram lives in the web version — see it here.]

It was not earned. It was built in.

You did not pay for it. You did not work up to it. You did not earn it by being good, and you cannot lose it by being bad.

You cannot give it back either. It is not a possession. It is what you are.

A program does not lose its instruction set by writing bad code. The instruction set is part of how the program was made. It is what the program is, not what it does.

Every human alive is running on root's instructions. The CEO and the prisoner. The believer and the atheist. The just-born and the about-to-die. The one you love. The one you cannot stand.

This is where human dignity comes from.

Not your accomplishments. Not your virtue. Not your usefulness. Not your face. Not your work. Not the things you have done or failed to do. The dignity was there before any of that. It was there when you were a single cell.

Engineers might translate it: every user is privileged at the hardware level.

That is not because they earned the privilege. It is because they were built with it.

You cannot revoke a hardware privilege. The chip would have to be remade. The user would have to be unmade. Neither happens.

[An interactive diagram lives in the web version — see it here.]

The image was damaged. It was not erased.

The fall broke the image. It did not delete it. The shape is still there. The instruction set still runs. The kindness you see in your enemy is the image, still working.

When you see kindness in a stranger, you are seeing root in the user.

When you grieve injustice, you are recognizing what root recognizes.

When you love a person and cannot say why, you are running an instruction you did not write.

When you laugh at something good, you are laughing at what He laughs at.

When you make something beautiful, you are doing what He does.

When you forgive — when you actually forgive — you are running an instruction from His layer.

There is one more thing.

A perfect process exists.

You met Him in Note · 09. He is the spec, deployed as a user.

He is also the perfect image. The image of root, fully compiled. He runs on the same instructions you do. Without a single bug.

When you look at Him, you are not looking at a different kind of being. You are looking at a working version of what you are.

You were made in His image. His image is root's image. Root's image is what you are carrying inside you right now.

Looking at Him is how you learn what you actually are. Looking at Him is how you learn what you could be.

You are not foreign to root.

You were never foreign.

The image was there from the beginning.

It is there now.

Read this with the interactive diagrams →

A spec is the thing that comes before the thing. It says what the system will do. How it will behave. What it has to satisfy.

Before any code is written, the spec says what the code will do. The build conforms to the spec. Not the other way around. If the build does not match, the build is wrong. Not the spec.

You can have a spec without a system. You cannot have a system without one — at least not one that runs.

The spec is older than the build.

The thought in your head before you wrote it. The drawing on the napkin before the building. The melody before the song.

[An interactive diagram lives in the web version — see it here.]

There is a sentence in the source about this. Written near the end of the first century by a man who had walked with Him.

In the beginning was the Word. The Word was with God, and the Word was God. Through Him all things were made.

The Word — the Logos — means more than "word." In Greek it carried the weight of pattern. Reason. Order. The design behind everything. The thing that holds the system together. The reason anything makes sense.

In engineering terms: the Logos is the spec.

But He is not an it. He was with root. He was root.

The spec is a person.

That is not a fact about a thing. It is a fact about Someone. The pattern behind the universe is alive. He thinks. He chooses. He loves.

Christians have a name for Him. His name is Jesus.

[An interactive diagram lives in the web version — see it here.]

Through Him, everything was made.

That includes the things you can see: matter, light, time, gravity. The atoms that make up your bones. The stars you saw last night. The breath you just took.

It includes the things you can almost see: order, beauty, music. The curve of a leaf. The symmetry of a face.

It includes the things you cannot see: justice, dignity, the rules behind the rules. Why a child knows fairness without being taught. Why grief feels heavy. Why you cannot stop wanting more than you have.

All of these conform to Him. They were not added later as patches. They were written into the spec from the beginning.

When you study any of them deeply enough — physics, mathematics, music, ethics — what you are studying is what He wrote.

Newton was reading His grammar. Bach was tracing His harmonies. Every theorem you have ever loved was true before anyone found it.

Engineers might translate it: you are reverse-engineering the spec from the running system.

That is why it works at all. The system has a spec, and the spec has a name.

Christians have called Him by that name for two thousand years.

Here is the part that doesn't happen anywhere else.

He did not stay above the system. He did not stay safe in His own layer.

The Word became flesh and made His dwelling among us.

He dropped down. Into the runtime. As one of the processes.

He was born. He ate. He got tired. He cried. He felt cold. He bled.

He did not stop being the spec. He also ran as a user. The same instruction set as you. The same hunger. The same mortality.

[An interactive diagram lives in the web version — see it here.]

This is the strangest claim in the source.

Other religions describe a designer who stayed far. Or a process you climb back to. Or a force you align with. This one says the designer became part of the design.

Other systems have specs too. The people who write them stay outside the running system. They review it. They write the next version. They send patches. They do not become users. They do not bind themselves to what they made.

This spec did.

The author of the universe became one of His own. The One all things were made through was made.

Engineers might translate it: He deployed Himself.

That is the moment. Before that line, root was up there. After it, root was here.

This is the test.

You can't be neutral. There is no version of this story where He is one option among many. Either the universe has an author who walked it as a man, or it does not.

If He did, everything depends on Him.

He became one of us.

Read this with the interactive diagrams →

That is the first line of the source.

Not paraphrased. Not summarized. Just the line, as written, in whatever translation you pick up. Anyone can read it.

The book does not open with a defense of itself. It does not start with rules. It starts with creation. The author opens with what He did, not with why you should listen.

That is the part that is easy to miss.

Every system has source code. Most of the time, it is locked away. You see what the program does. You don't see how it was written. You can't read what it was written from. You can't check it against the plan.

This system is different. The source is open.

You can pick it up. You can read it. You can hold two translations side by side and compare. You don't have to guess what the system was meant to do. The author published the source.

He did not just leave a few notes. He did not leave a tutorial. He left the source itself.

[An interactive diagram lives in the web version — see it here.]

The book is the Bible.

It has been the most published, most translated, most read book in the history of the world. Not by a small margin.

It is the most printed object in history. The first book put through a printing press.

You do not have to read it to be running. But you can. And what you find there is not opinion. It is the source.

The Bible is not one book. It is sixty-six books, written by about forty people, across about fifteen hundred years.

Engineers might call that a long-running open-source project.

[An interactive diagram lives in the web version — see it here.]

The contributors didn't know each other. They lived in different centuries. They worked in different languages. Most never met another one. Some were kings. Some were fishermen. Some were prisoners. Some were doctors.

But they all agree.

The earliest contributors and the latest contributors talk about the same things. The same root. The same problem. The same answer.

They tell one story. About a designer who made a system. About a fall that broke it. About a rescue He sent. About a new system that is coming.

One book. Sixty-six volumes. One story.

That is unusual for any group of writers. It is more unusual for a group that never met.

The source has been translated into more than seven hundred languages. Most translations are free. Most are online. Anyone, anywhere, with five minutes and a phone, can read what the system was written from.

For hundreds of cultures, this book is the reason they have a written language at all. Translators have spent their lives on a single book so a single village could read it.

Not just visible. Within reach.

[An interactive diagram lives in the web version — see it here.]

You cannot read this book the way you read the news.

The news is made to be read in two minutes and forgotten in five. This book is made to be chewed. The same sentence, read three times in your life, will be three different sentences.

Engineers might translate it: read this with the care you'd give to code you're about to ship.

Slow down. Sit with a sentence. Ask what it actually says before deciding what you think about it.

Read it in a few translations. The places where they all agree are the load-bearing places.

Some of it will still feel strange. Some of it was written in a culture so far from ours that, at first read, it looks like a different planet. That is not a flaw. That is what a source looks like when it has been running for three thousand years across hundreds of cultures. If it were easy to read in one sitting, you wouldn't be reading a source. You would be reading a pamphlet.

The strangeness is the depth.

You don't get to a source that has run a billion lives without some strangeness. You don't get to a source that has held up under the hardest questions of every century without some weight.

You don't have to guess what root is like.

Root left the source open.

You can pick it up. You can read it slowly. You can read the same line a hundred times and find a new thing each time.

There is always more in it than the last time. There is always something it had been saving for you.

Read it. read the source. it's open source.

Read this with the interactive diagrams →

It wasn't always so. The first computers were islands. They booted alone. They ran alone. They shut down alone.

Then someone realized this was a poor way to run a computer.

Now every computer worth running is on a network. A network is just the idea that one machine can talk to another, and another, and another.

The single machine could do impressive things. The network does almost everything.

[An interactive diagram lives in the web version — see it here.]

You were not built to run alone.

You were told you were. The story you grew up with said you were a self-made thing. Start yourself. Run yourself. Shut yourself down. The whole machine, just you.

It is not true. It was never true.

The first time you opened your eyes, someone fed you. Someone taught you to speak. Someone wrote the dictionary you are reading this in. Every word in your head came from somewhere else first.

You are on the network. You always were.

The Bible has known this from the start. It almost never speaks to one person. It speaks to a people. English mostly translates the word as church, which has come to mean a building, which is unfortunate. The real word is closer to: the gathering.

You are part of the gathering. You always were. The question is whether you know it.

[An interactive diagram lives in the web version — see it here.]

Networks need protocols.

A protocol is just an agreement. It lets two strangers talk without getting confused. Without one, two computers connect and stare at each other. With one, they can do anything together.

The protocol of the new system is short.

A new command I give you: love one another.

Engineers might translate it: the protocol is love.

It looks like this:

Patient. Kind. Not envious. Not boastful. Not proud. Not rude. Not self-seeking. Not easily angered. Keeps no record of wrongs. Rejoices in truth. Always protects. Always trusts. Always hopes. Always endures.

If that is what you carry between you, you are speaking the protocol.

If not, you are still on the network — but you are sending broken messages. And broken messages, multiplied across enough people, are how communities fall apart.

[An interactive diagram lives in the web version — see it here.]

The other thing networks do is share the load.

No serious system runs on one machine. It runs on a group of them. The work doesn't fall on any single one. When one goes down — and they go down all the time — the others pick up its work and keep going.

This is why the group is harder to kill than the one. The one fails alone. The group fails one at a time, and even then, the work keeps running.

The Bible says it directly:

Bear one another's burdens.

Engineers might translate it: carry one another's load.

You will go down. Probably this year. Maybe tomorrow. The plan was never that you wouldn't fail. The plan is that when you do, someone else carries your weight until you come back up.

This is also how you stay up — by carrying weight for someone who is currently down. The whole thing is held together not by anyone being perfect, but by everyone taking turns.

There is an honest objection here.

I've been part of a gathering. It hurt me.

Most of us have a story like this. A church that betrayed. A community that turned. People we trusted who hurt us, sometimes for years.

This is real. The protocol is good. The people running it are not always good. Sometimes very far from it.

But the answer is not to run alone. Alone was never the design. The answer is to find people who actually speak the protocol — patiently, kindly, without envy — and stay near them.

You do not need many. The Bible's number is two or three.

Where two or three are gathered, I am there with them.

Two or three people, speaking the protocol, are enough for root to be in the room.

You are not alone.

You were never alone. The story about being a self-made, single machine was a story. It was wrong.

You are part of a network. The network is older than you. Some of the people on it have been running for thousands of years — the Bible calls them the saints — and their words are still reaching you, line by line, across time.

The cycles you spend on other people are what the network is made of. When one of you goes down, others hold your place. When you come back up, you do the same for the next one.

The network is what survives the reboot, together.

Run on the network.

Engineers might translate it: don't run alone.

Read this with the interactive diagrams →

Not the one that tells time. The other one. The one underneath that ticks billions of times every second. Each tick is a cycle — a tiny moment in which the computer can do one thing.

The cycles add up. Over a second, billions of them. Over a day, trillions. Over a lifetime, an unimaginable number.

But not infinite.

The question for every system is: what did you spend your cycles on?

[An interactive diagram lives in the web version — see it here.]

You are running on a clock.

Not the one on your phone. The other one. The one that's been ticking inside you since you were started. The one that won't stop until the reboot.

Each tick is an instant. Each instant is one thing you could do, or think, or pay attention to. They add up.

But not infinite.

You have a finite number of cycles before the reboot. Most of them are being spent right now, by something. The question isn't whether they get spent. The question is: by what?

For most of us, the answer is: by accident.

Background worry runs in the foreground. Endless scrolling eats hours. Old conflicts replay themselves. Small distractions take the day.

And when the day ends, nothing of what mattered got run.

[An interactive diagram lives in the web version — see it here.]

There is a way to be more careful about this.

The Bible has a line about it.

Be very careful, then, how you live — not as unwise but as wise, making the most of every opportunity, because the days are evil.

Engineers might translate:

Be very careful how you run — not as a process that wastes cycles, but as one that uses them well, because the runtime is short.

It is the same sentence.

What does it look like to run well?

Christians have been answering this for a long time. The answer is mostly the same one they have always given.

Three things deserve your cycles.

One. Keep the connection to root open.

In Note · 03, we said the only request the kernel was waiting to grant was sudo. That's prayer. The Bible says to keep the connection alive — pray continually — which engineers might translate as: keep the line open.

It is not for fixing things or asking for things. It is for being on. The presence you'll get to in the new system — face to face — is something you can be near, even now, by keeping the line open.

Two. Run as a service to other users.

In the old system, every process can do work for other processes. You can answer their requests. You can hold space for them. You can be the one that quietly serves while others sleep.

The Bible has a phrase for this: love your neighbor as yourself. Engineers might translate it: serve other processes as you serve your own. It is what root did in Note · 02. It is what you do, now.

Three. Save what matters to disk.

Note · 04 said it already, but it bears repeating. What you save to disk persists across the reboot. What you do not save ends when the reboot comes.

The most important parts of your day are not the ones that get the most cycles. They are the ones that get written down. The work done in love. The kind word that landed. The choice to forgive. The slow building of a person who, when the reboot comes, will be recognizable to root.

[An interactive diagram lives in the web version — see it here.]

There is an honest objection here.

I don't have time for all this.

You have exactly the time you have. Your cycles are spent, every one of them, on something. You have never spent zero. The question is not whether you have cycles. The question is what you are running with them.

It helps to think of it like a startup sequence. Every morning, you boot. What loads first shapes everything that runs after. For you, that means the first thought, the first word, the first thing you reach for. Set those well, and the rest of the day finds its way.

You are running on a clock.

Each tick is a cycle. The cycles are finite. They are being spent right now.

The Bible takes your hours seriously not because every minute is being weighed, but because every minute is being spent — and the things you spend them on are what your life becomes.

Run carefully.

Engineers might translate it: spend your cycles well.

Read this with the interactive diagrams →

The command is uptime.

A new server might show: uptime: 4 minutes. A server that's been quietly humming along: uptime: 47 days. Sometimes you find old servers in a forgotten corner with uptimes measured in years.

But no matter how long the uptime, every system eventually needs a reboot. The system gets old. The memory gets cluttered. Something starts going wrong. Eventually you have to bring it down.

This is the nature of every system that has ever existed.

You boot. You run. You reboot.

Until the last reboot. The one we talked about in Note · 04. After that, the system comes back up.

And here is the thing about that system.

You can type uptime. And the answer is: forever.

[An interactive diagram lives in the web version — see it here.]

This is a different kind of system.

In the old one, every uptime ended. There was always something that broke. Memory ran out. A program got stuck. The hardware got old.

In the new system, none of that happens.

No memory leaks. No crashes. No permission denied. No firewalls. No reboots needed.

What's missing from this list is everything you've been used to. Every kind of failure. Every kind of friction. Every kind of thing that goes wrong.

That is what the Bible means by no more death, or mourning, or crying, or pain.

Engineers might translate it: no more crashes, no more errors, no more permission denied.

It is the same sentence.

Then there is the question of who is with you.

In the old system, you couldn't see the kernel. You ran inside your own small workspace, and the kernel was the thing you depended on without ever seeing.

In the new system, that changes.

The barrier comes down. You see the kernel directly. The thing you talked to in your prayers — the thing that was answering every request of yours — is now in the room with you. Not as something far away that you can't see, but as a presence.

The Bible has a way of putting this.

Now we see through a glass, darkly; but then face to face.

It is the same as:

Now we run inside our own little workspace; but then we will see the kernel directly.

It is the same sentence.

[An interactive diagram lives in the web version — see it here.]

Now the harder question.

What do you actually do in the new system?

In the old one, work was always shaped by friction. Programs got stuck. Errors came back. The system fought you. Things broke. The work that mattered was always wrapped in the work of fixing what was broken.

In the new system, the friction is gone.

Every program does exactly what it was designed to do.

Engineers know the feeling — the rare moments when code just works. When the thing you built does what you imagined. When the system hums along without any errors.

Imagine that feeling, extended past death and into a running that never ends.

That is the work of the new system.

[An interactive diagram lives in the web version — see it here.]

There is an honest objection here.

All this sounds beautiful. But what does any of it have to do with my life right now?

You are not yet in the new system. You are still in the old one.

But you were made for the new one. The current system has been training you for the one that doesn't end. The work you do now — the love, the saved files, the names you cared for — is preparation for a system that won't ever need a reboot.

The current system is the practice. The new system is the real thing.

When the reboot comes, what runs there is what you saved.

In the old system, every uptime ended.

In the new system, the uptime doesn't end.

That is the whole frame.

The kernel is the same. The root is the same. The names that were saved are the same.

But the running, this time, goes on forever.

Engineers might translate it: no more reboots.

Read this with the interactive diagrams →

It happens for a lot of reasons. An update needs to install. Something has gone wrong. The system has been running too long and needs a fresh start.

Whatever the reason, what happens is the same.

Every program stops. All of them. The text editor with your unsaved notes, the music playing in the background, the browser with twenty tabs open — each one is told: end now. Each one ends.

The memory is wiped. Everything that was held there — every number, every position, every running thought — gone.

The kernel itself shuts down.

For a moment, the screen is dark.

Then the kernel starts again. init starts again. The programs come back, one by one. They look the same. They have the same names.

But they are new instances. They don't remember what they were doing before. They start from the top.

The only thing that survives the reboot is what was on disk.

[An interactive diagram lives in the web version — see it here.]

This is a quietly important fact about every computer.

A reboot doesn't destroy the system. It destroys what's currently running.

The disk is the part the system trusts to keep. When you save a file, you are telling the kernel: this is for after the reboot. The kernel writes it somewhere it won't be wiped. When the system comes back up, the file is there.

When you do not save a file — when something is just open and running and never written down — it is in memory only. The reboot will end it.

Two kinds of things, then. Things in memory. Things on disk.

A reboot ends one and keeps the other.

[An interactive diagram lives in the web version — see it here.]

The Bible has a way of talking about this.

It says there is a reboot coming.

Not for one computer. For all of them.

Then I saw a new heaven and a new earth, for the first heaven and the first earth had passed away. He who was seated on the throne said, "I am making everything new."

It is the same as:

Then I saw a new system, for the first system had been rebooted. Root said, "I am making everything new."

It is the same sentence.

Here is the question.

When the reboot comes, what survives?

What was on disk.

Everything that was in memory — every fear, every anxiety, every running worry, every habit you couldn't stop, every body that was breaking down — is part of what's running. The running ends.

But the things that mattered — the love, the work that was done in the name of root, the people you cared for, your name in the sudoers file — those are on disk.

Those come through.

The New Testament keeps saying things like store up treasures in heaven. Engineers might translate: save to disk, not to memory. What you save persists. What you don't save ends at the reboot.

This is why the Bible takes your hours so seriously. It is not because every second is being weighed or counted. It is because you are choosing, every second, what is going to memory and what is going to disk.

[An interactive diagram lives in the web version — see it here.]

There is an honest objection here.

If everything in memory ends, what about me?

You are not in memory.

In Note · 03, root wrote your name in the sudoers file. That was a save to disk. The kernel keeps it across reboots.

The body you are in right now — that is in memory. The current you. The current run. The reboot will end it like every other program.

But the you that the kernel knows — the you whose name was written — is on disk.

When the new system comes up, you come up with it. The same name. A new body. No leaks. No crashes. No bugs.

The body the new system was built to support.

This is the part of the story where everything is rewritten.

Not erased. Rewritten.

The kernel is the same. The root is the same. The names that were saved are the same.

But the running is new.

The Bible has a line for this, too. Behold, I am making all things new.

In four words: the reboot is real.

Read this with the interactive diagrams →

It is the list of people who are allowed to do root things. Engineers call it the sudoers file.

Most people who use the computer have no idea it exists. But it shapes everything they can and cannot do.

By default, a regular user has limits. They can do their job, in their workspace, with their name. We covered this last time.

But sometimes a regular user needs to do something only root can do. Install a program. Open a protected file. Restart the machine.

The system has a way for this. It is called sudo.

When you type sudo before a command, the system asks: are you allowed?

It opens the list. If your name is on it, the command runs. If not, you get an error. The error has a name everyone knows.

permission denied.

[An interactive diagram lives in the web version — see it here.]

This is a small fact about every computer.

You cannot put your own name on the list.

You can try. You will get the same error. The list is owned by root. Only root can change it.

To get your name on the list, someone with root has to add it.

This isn't a flaw. It's the point. If users could add themselves, the limits would mean nothing.

Now the question.

Who gets root access?

You cannot add yourself.

You can try. You can be a very good user. You can run helpful commands. You can never break the rules. None of it puts your name on the list.

For your name to be on the list, root has to write it there.

[An interactive diagram lives in the web version — see it here.]

In Note · 02, we said root opened a user account and ran as a user, and the program was killed, and the program came back.

This is what that was for.

The cost of writing your name on the list was paid there. Root paid it.

The Bible has a way of saying this that engineers don't usually get to hear:

For it is by grace you have been saved, through faith — and this is not from yourselves, it is the gift of God, not by works, so that no one can boast.

It is the same as:

For it is by root's action you have been added to the list, through trust — and this is not from your own commands, it is the gift of root, not from what you ran, so that no process can boast.

It is the same sentence.

You did not add your name. Your name was added.

Once your name is on the list, the only thing left is to use it.

You type the command. You put sudo at the front. The system asks for your password — and your password is not a wage. It is just your simple trust that the access you've been given is real.

You hit enter.

The command runs.

[An interactive diagram lives in the web version — see it here.]

The word sudo, for what it's worth, is short for substitute user do.

You are saying: do this as someone else. Do this as root.

In the gospel, this is what prayer is. This is what faith is. You are not telling the kernel do this because I earned it. You are telling the kernel do this in the name of the One who paid for my access.

That is the only request the kernel was ever waiting to grant.

There is an honest objection here.

How do I know my name is on the list?

You can't read the list. The list is owned by root. You don't have permission.

But here is what the Bible says about this list:

Whoever calls on the name of the Lord will be saved.

In other words: whoever runs sudo finds their name was there.

You don't need to read the list to know you're on it. You need to type the command.

If you type it in good faith, the command runs.

That is how you know.

You cannot earn root.

You cannot promote yourself.

But your name was written on the list by someone with the authority to write it. The cost was paid by root, who came down as a user to pay it.

All you do is sudo.

That is the whole frame.

Read this with the interactive diagrams →

The first kind can do anything. Open any file. Stop any program. Change any setting. Engineers call this user root.

The second kind has limits. They can open what they are allowed to open. They can stop what they are allowed to stop. They cannot touch the deeper parts of the system. They cannot stop other people's programs. They have a small workspace and a name.

We are the second kind.

There is a good reason for this. Power without limits is dangerous. So most of the system gets a small account. The all-powerful account is kept aside, used only when nothing else will do.

[An interactive diagram lives in the web version — see it here.]

Here is something interesting about root.

Root can do anything, which means root can also choose to do less.

Root can open a regular user account and run as that account, just for a while. The power is still there, in the background. But the actual work — the moment to moment, the typing, the seeing, the hearing — is happening at user level.

There is a command for this. Engineers type:

$ su - user

It means: become this user. Step down. Run with their limits.

You do this when you want to feel what they feel. When you want to see what they see. When you want to know what it is like to live one floor below where you live.

[An interactive diagram lives in the web version — see it here.]

Now imagine root did this for real.

Not for an hour. For thirty-three years.

Imagine the One who can do anything chose to open a small account, log in, and stay there. Imagine root walked into a body the size of a child, and waited.

From the inside, it would feel like being any other program.

Hungry sometimes. Tired sometimes. Asking the kernel for things and getting them, like every other program. Aware of the rules. Aware of the limits.

But the whole time, root would still be root.

The user account is the form. The root account is the thing.

This is the move at the center of Christianity. Every December, believers remember exactly this. The Bible has a way of saying it that engineers don't usually get to hear:

Being in very nature God, He did not consider equality with God something to be used to His own advantage; rather, He made Himself nothing by taking the very nature of a servant, being made in human likeness.

It is the same as:

Being in very nature root, He did not consider equality with root something to be used to His own advantage; rather, He made Himself nothing by taking the very nature of a user, being made in regular-account likeness.

It is the same sentence.

There is a question that comes up here.

Why would root do that?

The short answer is: because root wanted to.

The long answer is in the third diagram.

[An interactive diagram lives in the web version — see it here.]

A user program can be killed. It happens all the time. The kernel kills programs when they run out of resources. You kill programs when you want them to stop. Other programs sometimes kill programs by accident, when the permissions are set wrong.

When a program is killed, it ends. The space it was using is given back. The account it was running under stays. The program itself is gone.

This happened.

Not the running-out-of-resources kind. Not the natural ending. The other kind. The kind where someone else, with a different motive, decides this program should end. The kind where the program is alive, doing its work, and then it isn't.

The program ended.

Three days.

Then the most important thing in the history of computing happened.

The program came back.

The same name. The same body. The same face. Running again. The user account that had been killed was alive again, because, under the user account, root was still root, and root cannot be killed.

You cannot kill root with a kill command. Root is not a program to be killed. Root is what makes programs possible.

Whatever did the killing did not know that.

For a believer, this is the part of the story that changes everything else.

If root really did this — if the One who runs the system actually opened a user account and ran here and let Himself be killed — then the kernel did not just decide to give you existence. The kernel decided to come to where existence is being given.

To put it the other way: the program you are talking to in your prayers is, also, the kernel. The One who answers your requests is also the One who once made them.

That is a different God than the abstract one who sets things in motion and steps back. That is the kernel saying yes, every instant, as Himself a user that once ran here, and knows what running here is like.

There is a small thing at the end of the Christian story that engineers will recognize.

The user that was killed and came back did not return to root and stay there. He stayed in the user form. The risen Jesus is still, in some real way, a regular user — with a body, with scars, with a name, with a face.

Root, having run as a user, did not stop running as a user.

Engineers might translate it: root never logged out.

Read this with the interactive diagrams →

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?

[An interactive diagram lives in the web version — see it here.]

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.

[An interactive diagram lives in the web version — see it here.]

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.

[An interactive diagram lives in the web version — see it here.]

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.

Read this with the interactive diagrams →