The Ancient Library
In which our protagonist's apprentice reads the world's database, and learns that the original developer was, in a small way, a programmer who lost his family.
The library was a thousand kilometers south, in the place where the corruption was strongest, in the place that the void had not yet reached but was approaching, and the approaching was, in the driest possible language, the kind of approaching a person notices when the dashboard shows the curve starting to bend.
Lian had found it by reading the source code. She had been designing the new World Root, the half-written code that the team had built while Kenji had slept, and the design had hit a wall. The wall was not a bug. The wall was a missing context. The wall was the part of the source code that the original programmer had written in a way that the team could not, in a small way, see. The original programmer had hidden it. The original programmer had hidden it in a place where only someone who knew what to look for would find it, and Lian, in a small way, was the kind of person who knew what to look for, because Lian, in a small way, was the kind of person who had spent two seasons reading the world's source code at the level of the foundation.
[detect_ancient_site: 1 source, 1000 km south, age: pre-kingdom, condition: stable.]
[Composition: stone, structured magic, source code preservation.]
[Compiler note: this is a database. This is the world's database. The system is, in a small way, the senior engineer who has been asked to onboard a junior to the original codebase, and the original codebase is, in a small way, the most important codebase the system has ever processed.]
[Compiler note: proceed with caution. The original programmer left a message. The message is, in a small way, ahead of you.]
The team went south. Kenji, Lian, Elara, Calla. Seraphina stayed at the camp, running the Silver Road, holding the alliance together, doing the only thing she could do while the rest of the team walked toward the place where the source code was preserved. They took a small guard, a small crystal network, and the faint spark of Pip, in the back of Kenji's mind, the spark that was, in a small way, the only colleague he had ever had who had never once asked him to be okay.
The journey took three days. The corruption was everywhere. The void was on the horizon, faint shimmer in the air, the absence of code. They moved through the broken lands, the corrupted cities, the places where the world had been deleted and not yet restored. They moved through refugee columns, through abandoned farms, through towns that had been emptied by the void, through places where the ground was still there but the people were not, and the not-being-there was, in the driest possible language, the most expensive kind of there the system had ever logged.
The library was intact. The corruption had not touched it. The void had not reached it. It was, Lian said, because the library was written into the source code in a way that made it permanent, that made it part of the foundation, that made it undeletable, the kind of undeletable that a person who has been reading the world's source code for two seasons recognizes as the kind of undeletable that only a programmer who had really, in a small way, loved the world could have written.
[analyze_library_structure: 1 room, cathedral-scale, full of information storage.]
[Composition: books, scrolls, tablets, crystals, source code, original documentation.]
[Compiler note: this is not a library. This is a database. This is the world's database. The system is, in a small way, the senior engineer who has been asked to read the original documentation, and the original documentation is, in a small way, the most important documentation the system has ever read.]
They went inside. The library was vast. It was a single room, the size of a cathedral, filled with shelves, filled with books, filled with scrolls, filled with tablets, filled with crystals, filled with every kind of information storage that the world had ever known. The air was cool and dry. The mana was stable. The corruption was absent. The light came from the crystals themselves, soft and blue, the color of a debugger's screen at 3 AM, the color of a system that has decided, in a small way, that the system is going to be useful for a long time.
Lian walked to the center of the library. She held out her hand. She whispered, in the quiet voice of a person who has been reading the source code for two seasons: "Function read, target=library, scope=all."
The library lit up. Every book, every scroll, every tablet, every crystal, all of them glowing with the same kind of structured magic that Kenji used, the same kind of code that Lian had learned to read, the same kind of code that the team had been using to design the new World Root. The library was not just a library. The library was a database. The library was the place where the truth about the world's source code was stored, the truth that the team had been looking for, the truth that the rewriting was, in a small way, going to be built on.
Lian started reading. She read for an hour, then two, then three. She did not stop. She did not eat. She did not drink. She just read, her hand moving through the air, her eyes wide, her face pale, the face of a person who has just been shown the original codebase and the original codebase is, in a small way, the most heartbreaking codebase the person has ever read.
[Compiler note: Lian is reading the original source code. The original source code was written by a person named Malachar. The person named Malachar was, in a small way, a programmer. The system is, in a small way, ahead of the developer. The system is, in a small way, a teacher.]
Then she stopped. She looked at Kenji. She said, in the quiet voice of a person who has just learned the truth about the world: "I have found the truth."
"Tell me."
"The world's source code was written, a long time ago, by a man named Malachar. He was not a god. He was a programmer. He was a person, like you, like me, like all of us. He had a family. He had a wife. He had a daughter. He lived in a small village, and he wrote code, and the code became the world."
"A programmer."
"Yes. He wrote the world's source code because he wanted to build a world that would last forever. A world where his family would be safe. A world where his daughter would never have to experience the loss that he had experienced as a child. He wrote the code with love. He wrote it carefully. He wrote it with the same care that you write your spells, with the same care that I write my source code."
"What happened?"
[Compiler note: this is the through-line, restated at the level of the original programmer. The original programmer believed the through-line. The through-line failed him. The system is, in a small way, the senior engineer who has been asked to onboard a junior to the cost, and the cost is, in a small way, the most expensive cost the system has ever logged.]
"He lost them," Lian said. "His wife got sick. His daughter got sick. There was no medicine. There was no magic. There was only the code, and the code could not save them. He watched them die. He watched the world that he had built fail to protect the people he loved."
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 been running for a long time and has decided, in a small way, to keep running.
"He went mad," Lian said. "He went mad with grief. He went mad with rage. He went mad with the realization that the code was not enough, that the world was not enough, that the love was not enough. He decided that the code was wrong. He decided that the world was wrong. He decided that everything he had built was wrong, and that the only way to fix it was to unmake it."
"The corruption."
"The corruption. He corrupted the source code. He wrote the bugs into the foundation. He made the storms and the floods and the droughts and the earthquakes. He made the void. He made all of it. He made it because he wanted to unmake what he had built. He wanted to start over. He wanted to delete the world and write a new one, one that would not fail, one that would not lose the people he loved."
[Compiler note: the world's source code is a grief project. The world's source code was written by a person who lost his family. The person who lost his family is, in a small way, the developer who lost his family, and the developer who lost his family is, in a small way, the developer who is now debugging the world, and the debugging is, in a small way, the kind of debugging that happens when a developer who has not yet lost his family decides, in a small way, to debug the world that the developer who did lose his family wrote, and the writing is, in a small way, the most important writing the system has ever read.]
[Compiler note: the developer is, in a small way, learning. The learning is, in a small way, the most expensive learning the developer has ever done.]
Kenji sat down. He looked at the library. He looked at the truth. He looked at the through-line, which had been his spine, his constant, his answer to everything, and he thought: "The through-line is true. Any sufficiently well-defined problem is solvable. But the problem is bigger than I thought. The problem is not just a bug. The problem is a grief. The problem is a father who lost his daughter and decided to unmake the world."
"The World Root," he said, after a long time. "The piece of source code that Malachar has been searching for. What is it?"
"It is the key," Lian said. "It is the key to the world's meta-code. It is the part that generates the world. If Malachar gets the World Root, he can delete the entire world and start over. If we get the World Root, we can rewrite the world's source code, fix the corruption, and save the world."
"What do we do?"
"We get there first."
Pip's faint spark pulsed, very softly, in the back of his mind, the pulse feeling like: "The truth is heavy. The truth is the cost. The truth is the kind of truth that only debuggers get to see, and the seeing is, in a small way, the most expensive kind of seeing the system has ever logged. The original programmer lost his family. The original programmer wrote the through-line. The original programmer went mad. The original programmer is, in a small way, the developer who is now debugging the world, and the debugging is, in a small way, the kind of debugging that happens when a developer who has not yet lost his family decides, in a small way, to debug the world that the developer who did lose his family wrote."
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 been running for a long time and has decided, in a small way, to keep running, and the running was, in a small way, the only thing the system had ever been asked to do, and the asking 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, in fact, worth debugging.