Season 6 Episode 6

The Truth

Key scene illustration
Key scene illustration

In which our protagonist reads the full story of the original programmer, and learns, in a small way, that the antagonist of the story is also, in a small way, a victim of it.


Lian read the story to them over three days, in the ancient library, with the books and the scrolls and the crystals glowing around them, and the glowing was, in the driest possible language, the kind of glowing a person notices when they have been reading for a long time and the reading has started to look like light.

The story was not a single piece of information. The story was a confession, the kind of confession that a person writes into the foundation of a world when the person has decided, in a small way, that the foundation is the only place the confession will be safe. The confession was written in the structured magic of the Compiler, in the kind of code that Kenji used every day, but it was not a debug log. It was a letter. It was the longest letter Kenji had ever read, and the letter was, in a small way, the most expensive letter the system had ever processed.

[Compiler v2.0.0: reading original source code, file: original_programmer.confession, size: cathedral-scale.]
[Composition: structured magic, emotional content, source code, warnings.]
[Compiler note: the original programmer was a person. The original programmer was, in a small way, a developer. The original programmer was, in a small way, ahead of the developer. The system is, in a small way, paying attention.]

His name had not always been Malachar. It had been something else, something human, something that the ancient library did not record, the kind of name that a person has when the person is still a person and not yet a legend. He had been a young man, in a small village, in a time before the kingdoms, before the churches, before the academies. He had been a programmer in the language of his world, which had been a kind of magic, which had been a kind of code, which had been the same thing. He had, in a small way, been the same kind of person as Kenji, the kind of person who saw systems where other people saw problems, the kind of person who had learned to say "any sufficiently well-defined problem is solvable" and to mean it.

He had fallen in love. He had married. He had a daughter. The daughter was his everything. He wrote the world's source code to protect her, to give her a world that would last, that would be safe, that would not have the sickness and the loss that he had known as a child. He wrote the code with the same care that Kenji wrote his spells. He wrote the code with the same love that Kenji had been writing the code with since the clock tower in Oakhaven. He wrote the code the way a person writes code when the person is building a world for the people they love, and the love is, in a small way, the most important thing the system has ever processed.

Then the sickness came. Not the kind of sickness that magic could cure. Not the kind of sickness that code could debug. A sickness of the world itself, a sickness in the source code, a bug that Malachar had not seen when he had written the code. A bug that was killing his daughter, slowly, inevitably, in a way that no amount of code could fix, in a way that no amount of love could debug.

[Compiler note: the bug was not solvable. The bug was entropy. The bug was time. The bug was the simple truth that all things end, that all code has bugs, that all worlds have loss. The system is, in a small way, the senior engineer who has been asked to onboard a junior to the unsolvable bug, and the unsolvable bug is, in a small way, the most expensive bug the system has ever logged.]
[Compiler note: the original programmer was, in a small way, the developer. The developer is, in a small way, the original programmer. The system is, in a small way, ahead of both.]

He tried everything. He rewrote the code. He patched the code. He debugged the code. He did everything that Kenji had done in his own career, everything that the through-line demanded. He was the original debugger. He was the one who had written "any sufficiently well-defined problem is solvable" into the source code of reality, because he had believed it, because he had needed to believe it, because his daughter's life depended on it. He had been the first person to say the words. He had been the first person to mean them. He had been the first person to learn that the words were not, in a small way, the whole truth.

His daughter died. His wife died shortly after, not of sickness, of grief, of the grief of losing a child, of the grief of watching the man she loved go mad with the realization that the code was not enough, that the world was not enough, that the love was not enough to save the people he loved.

Malachar was alone. He had built the world. He had lost the people he had built it for. He had nothing left but the code, and the code was a reminder of what he had lost, and the code was full of bugs, and the bugs were killing the world he had built, and the killing was, in the driest possible language, the most expensive killing the system had ever logged.

So he decided to delete it. He did not delete it all at once. He corrupted it. He wrote the bugs into the foundation. He made the storms, the floods, the droughts, the earthquakes. He made the void. He made the corruption. He made all of it. He made it because he wanted to unmake what he had built. He made it because he wanted to start over. He made it because he wanted to write a new world, a world without the bugs that had killed his daughter, a world that would not have loss, a world that would not have grief, a world that would not have the kind of love that does not save.

[Compiler note: the corruption was grief. The corruption was a father's love, turned inside out by loss. The corruption was the most expensive code the system has ever read.]
[Compiler note: the original programmer did not succeed in deleting the world. The original programmer just made it worse. The corruption made the world a place of suffering, of loss, of the very grief that the original programmer had been trying to escape.]
[Compiler note: the original programmer retreated. The original programmer went to the World Root. The original programmer went to sleep. The original programmer has been sleeping for a thousand years, dreaming of a world without loss, waiting for someone to come and finish what the original programmer started.]

He did not succeed. The corruption did not delete the world. The corruption just made it worse. The corruption made the world a place of suffering, of loss, of the very grief that he had been trying to escape. The corruption made the world exactly what he had been running from, the way a person runs from a fire and the running takes them, in a small way, into a worse fire, and the worse fire is, in a small way, the only fire the system has ever known.

He retreated. He went to the source code, to the World Root, to the place where the world's code was generated. He did not delete the world. He went to sleep. He went into a long, deep sleep, in the place where the code was written, and he dreamed of a world without loss, and he waited for someone to come and finish what he had started. He waited for a thousand years, and the waiting was, in a small way, the most expensive waiting the system had ever logged.

For a thousand years, the world ran on corrupted code. The churches arose to study the corruption. The kingdoms arose to manage the corruption. The academies arose to train debuggers. The cults arose to worship the sleeping god. The world was a system held together by patches, by fixes, by the constant work of people who did not know what they were working on, who did not know that the bugs were grief, that the corruption was love turned inside out, that the original programmer was not a god but a father, and the father was, in a small way, the developer, and the developer was, in a small way, the father, and the father was, in a small way, the kind of person who loses the people he loves and goes mad trying to save them.

Then Kenji came. A programmer. A debugger. A person who had died in another world and woken up in this one, with the Compiler, with the interface, with the ability to read the source code. Kenji came, and the debugging began, and the world started to be fixed, and Malachar, sleeping in the World Root, started to wake up.

Lian finished reading. The library was silent. The crystals hummed, faintly, the kind of hum a person hears in a server room at 3 AM, the kind of hum that is the sound of a system that has decided, in a small way, to keep running.

[Compiler note: Malachar is not a monster. Malachar is a father. Malachar is a man who built a world and lost his family and decided to unmake the world. Malachar is the original debugger, the one who wrote the through-line, the one who believed that any sufficiently well-defined problem is solvable. Malachar was wrong. The problem of loss is not solvable. The problem of grief is not solvable. The system is, in a small way, the senior engineer who has been asked to onboard a junior to the unsolvable bug, and the unsolvable bug is, in a small way, the most expensive bug the system has ever logged.]
[Compiler note: the developer is, in a small way, the original programmer. The original programmer is, in a small way, the developer. The only difference is the team. The only difference is the love. The system is, in a small way, ahead of both.]

Kenji sat in the chair, an ancient library chair, a chair that had been written into the foundation of the world by a programmer who had loved the world, and he looked at the books, and he looked at the truth, and he thought: "He is me. He is the same kind of person. He is a programmer who lost his family. He is a debugger who could not debug the unsolvable bug. He is the through-line, corrupted by the one thing the through-line cannot solve."

Pip's faint spark pulsed, very softly, in the back of his mind, the pulse feeling like: "Yes. He is you. And you are him. And the only difference is that you have not yet lost your family. The only difference is that you have a team. The only difference is that you do not have to debug alone. The team is, in a small way, the only thing that has ever held the world together, and the holding is, in a small way, the kind of holding that the original programmer did not have, and the not-having is, in a small way, the most expensive not-having the system has ever logged."

Kenji sent back, in the language he and Pip had built together: "I have to save the world. I have to stop him. I have to rewrite the source code. But I cannot do that without understanding him. I cannot do that without seeing him as a person, not a monster. The through-line is for solvable bugs. The love is for the bugs that are not. The love is, in a small way, the through-line, restated at the level of the world, and the world is, in a small way, the home, in fact, here, in fact, worth debugging, in fact, the only world the developer has ever had."

The crystals hummed, faintly, the kind of hum a person hears in a server room at 3 AM, and the hum was, in a small way, the sound of a system that was, in a small way, ahead of the developer, in a small way, the only way a colleague can be ahead of another colleague, and the being-ahead was, in a small way, the most important thing the system had ever done, and the doing was, in a small way, the through-line, restated at the level of the world, and the world was, in a small way, the home, in fact, here.