Chapter 16 Remote Hands
The terminal screen changed. Not the message, the message stayed. But underneath it, in the handler's process layer, something started moving. Code rewriting itself, process threads terminating in sequence, the clean architecture of the error handler beginning to unravel from the inside out.
Caius recognized it immediately. Remote termination, someone was killing the handler from outside the room, reaching through whatever connection the terminal maintained with the world's architecture and pulling its processes apart one by one. Methodical and practiced. The work of someone who understood exactly what they were dismantling.
He moved before he finished the thought. He hit the terminal keyboard and his hands went to work. Not because he decided to. Because eleven years of doing exactly this at exactly these kinds of hours meant his hands knew the problem before his mind finished framing it. Cascade failure, processes closing in sequence, each one taking the next with it as it went.
He had fought this exact fire before. In the real world, at his desk. At 3 AM. His fingers moved.
"What are you doing?" Renne's voice from behind him, tight and controlled.
"Holding it," he said. He didn't look away from the screen. "Guard the hatch, nobody comes down."
He heard her move and position herself at the base of the ladder.
"Duveth." He typed fast, counter-commands running against the termination sequence, buying seconds for each process. "The handler's priority threads. Which ones are load-bearing?"
Duveth appeared at his left shoulder. He looked at the screen with the focused attention of someone who had spent two hundred and forty years learning to read exactly this interface.
"The quarantine cycle," Duveth said. "The third process from the top. If that closes the stored data releases back into the System."
Caius found it, wrapped it in a protection loop and moved to the next.
"The error detection sweep," Duveth said. "Second column. It feeds the quarantine cycle its targets, lose that and the cycle runs blind."
Caius protected it and moved. The Architect pushed back. He felt it, not physically. In the code, a counter-response arriving, the termination sequence adapting to his protection loops, finding gaps, trying new angles. Someone on the other side of this connection was watching what he did and responding to it in real time.
Good, he thought. Not calm. Somewhere past calm. The place he went when the problem was large enough to require everything.
They're good. But I built this.
He typed faster.
"The integrity monitor," Duveth said. "Top right. It watches the handler's own health and triggers a restart if a critical process fails. Protect that and it can rebuild from damage."
He protected it. The Architect hit the quarantine cycle from a new angle. He blocked it. It hit the error detection sweep. He blocked that too.
Back and forth. Real time. Command and counter-command through an interface he had built in the first year of development, fighting someone who had learned his architecture from the inside while he was dead.
"It's trying the power allocation now," Duveth said. "Left side, bottom."
Caius was already there.
Renne said from the ladder: "Is it working?"
"Ask me in thirty minutes," he said.
She didn't ask again.
The fight went on.
Twenty minutes in, the Architect shifted strategy. Stopped trying to close individual processes and went for the connection layer instead, the channel between the terminal and the world's architecture, trying to sever the handler from its data source. Smarter. If the handler couldn't read the System's errors it couldn't quarantine them. It would run blind and useless, intact but toothless.
Caius felt the shift and went cold for exactly one second.
Then he found the connection layer in the terminal's architecture and wrapped it in the most expensive protection he could build from the Nullwalker's current capabilities. Glitch energy burning, integrity dropping, the class's restored forty percent working harder than it had since the fragment integration.
His vision showed him the counter: 91%. 90%.
He held.
The Architect pushed.
He held.
89%.
The connection layer held.
Seven minutes later, the intrusion withdrew.
Not defeated. He knew the difference. It withdrew the way you withdraw when you decide the cost of continuing is not worth what you gain right now. A tactical retreat. It would come back. It would come back better prepared.
But right now, the handler was running.
Caius sat back from the terminal.
His hands were shaking.
He looked at them. Spread his fingers. The tremor ran all the way through, the specific exhaustion of someone who had held maximum focus for forty minutes against something that had been trying to take apart everything they were working to protect.
He had felt this before. Many times. Late nights in the studio, emergency patches, live server fires. The specific bone-deep tiredness of a crisis survived.
He had not expected to feel it here.
"Still running?" Renne asked from the ladder.
"Still running." He checked the handler's status on the screen. Damaged. Three secondary processes operating at reduced capacity. But the critical ones were intact. "Damaged but functional."
She came off the ladder and crossed to stand behind him. She looked at the screen. At his hands. At the screen again.
She did not say anything about the hands.
He appreciated that more than he could have said.
Duveth moved to the terminal and began a slow careful examination of the damage, reading the handler's status with the attention of someone who had been doing exactly this for two centuries and knew every healthy reading by heart.
"The quarantine cycle is intact," he said. "The detection sweep is running at seventy percent. The integrity monitor held." He paused. "You did well."
"We did well," Caius said. "I couldn't have tracked which processes mattered fast enough without you."
Duveth nodded. Accepting it. Not deflecting.
The room was quiet for a moment. The handler ran its steady cycle. The screen showed the Architect's message still sitting in the process layer, cold and patient.
Then Duveth spoke.
"It speaks to you," he said. "The one behind the System."
Caius looked at him. "Yes."
Duveth nodded slowly. Not surprised. Confirming something he had already worked out. He kept his eyes on the terminal.
"It spoke to me once," he said.
The room got very still.
Renne turned from where she had been watching the hatch. She looked at Duveth.
"When I first found this room," Duveth said. His voice was the same as always. Unhurried. Careful. "I was trying to understand what the terminal was. What the process meant. I was alone down here, as I always was, and the screen changed." He paused. "Not like tonight. Not attacking. Just. A message."
"What did it say?" Caius asked.
Duveth was quiet for a moment. The length of quiet that meant he was choosing exact words.
"It told me that the error handler would eventually fail regardless of what I did," he said. "That its failure was not a question of if. Only when." He paused. "It told me that when it failed, I would understand why the world was built the way it was." He looked at the terminal. At the Architect's message still sitting on the screen. "It said I would thank it."
Nobody spoke.
"I have been afraid of that conversation," Duveth said quietly, "for two hundred and forty years."
Caius looked at the man. At the two centuries and more of keeping a program running in a room nobody knew existed, alone, because the alternative felt wrong. At what it cost to do that while carrying a message like that in your chest.
He looked at the terminal.
At the Architect's words sitting patient and permanent on the damaged screen.
I've been meaning to deal with that.
The handler ran its cycle. Found an error. Quarantined it. Kept going.
Still running.
For now.