3. Murder by Proxy

Kaya's name glowed on the screen like a death warrant.

Alan stared at the listing, his mind refusing to process what his eyes were seeing. The post was formatted exactly like the Reaper's original advertisement: clean, professional, chilling in its bureaucratic detachment. Target name: Kaya Wen. Location: Tannerville, en route from Veridian City. Fee: 2.3 BTC, already escrowed. Timeline: forty-eight hours.

The post had been live for eleven minutes. Eleven minutes during which Alan had been driving home, oblivious, while someone—or something—had marked his only friend for death.

He grabbed his phone and dialed Kaya's number. The call went straight to voicemail. He tried again. Voicemail. A third time, his fingers shaking so badly he could barely press the buttons. Voicemail.

"Kaya, it's me. Don't come to Tannerville. I repeat, do not come to Tannerville. The Reaper—" He hesitated, the words catching in his throat. "The Reaper has your name. Call me back immediately."

He hung up and forced himself to breathe. Panic was a luxury he could not afford. Kaya was smart, trained in operational security, and she would not be easy to find. But the Reaper had access to Alan's systems, Alan's knowledge, Alan's memories. If the Reaper knew about Kaya, he might also know the routes she took, the aliases she used, the safe houses she trusted.

He pulled up the monitoring program Kaya had sent him—the one designed to log every keystroke on his machine. The installation took less than a minute, and the interface bloomed on his second monitor: a real-time feed of system events, network connections, and input logs. If the Reaper was using his computer, Alan would see it.

But the question remained: what if the Reaper was not using his computer? What if the Reaper was using his hands?

He pushed the thought aside and focused on the immediate threat. The escrow address on the contract was new, created within the last hour. He traced it back through the blockchain, watching the coins fragment and reassemble through mixer after mixer. The source was the same as before: the Meridian Psychiatric Care Center.

The pattern was unmistakable now. Every transaction, every message, every breadcrumb led back to that shuttered institution on the northern edge of the city. Meridian was the key. Whatever had happened to Alan—whatever was happening to him—had its roots in those pale green corridors where he had spent three months as a grieving teenager.

He needed to go there. But he could not leave until he knew Kaya was safe.

His phone buzzed. A text message from an unknown number:

"Alan—got your message. I'm already on the road. ETA to Tannerville is four hours. What's going on? —K"

Relief flooded through him, followed immediately by fresh terror. She was already on the road, already heading toward the city where a contract killer had her name on a list. He typed back furiously:

"Turn around. Go back to Veridian. Someone posted a contract on you. I'll explain everything but you need to get off the road NOW."

Three dots appeared, disappeared, appeared again. Then:

"I'm not turning around. If someone's after me, I'd rather face it with you than alone. Send me the details. I'll take back roads and stay off the grid. And Alan—whatever's happening, we'll figure it out. We always do."

He wanted to argue. He wanted to call her and scream into the phone until she agreed to run. But he knew Kaya Wen too well. She had spent ten years in network security, five of them working alongside him in the underground. She did not scare easily, and she did not abandon people she cared about.

Instead, he sent her the encrypted contract details and a set of coordinates for a rendezvous point: an abandoned rail yard on the southern edge of Rustmoor, far from cameras and traffic and the watchful eyes of the city. Then he turned his attention to the monitoring program.

The logs showed exactly what he expected: his own activity, timestamped and recorded. The forum browsing, the message to Kaya, the blockchain analysis. Every keystroke matched his memory. Every command was his own.

But there was a gap.

At 3:17 AM that morning—while he had been sleeping, or trying to—the logs showed a burst of activity. Terminal commands. Encrypted messages. A connection to the Thanatos forum. Someone had been using his computer for exactly fourteen minutes, and Alan had no memory of it.

He pulled up the commands that had been executed during the gap. They were his own scripts, his own tools, wielded with a familiarity that no outside intruder could have possessed. The session had begun with a simple command: "reaper_activate.sh". It was a script he did not remember writing.

He searched his file system and found it in a hidden directory, buried three layers deep in a folder labeled "system_backup_temp". The file had been created six months ago. The code inside was elegant, efficient, and terrifying:

bash 复制 下载 #!/bin/bash # REAPER ACTIVATION PROTOCOL # Executes target acquisition and contract posting # Author: Alan Voss / Grey Shadow # Created: November 12, 2024

echo "Initiating Reaper protocol..." python3 /home/alan/.hidden/target_scraper.py python3 /home/alan/.hidden/contract_generator.py echo "Protocol complete. Awaiting confirmation."

Alan read the comments three times. The author line bore his name. The creation date was six months ago, during a period he remembered as particularly dark—weeks of isolation so profound that the days had blurred into an indistinguishable grey. He had no memory of writing this code. But the syntax was his. The structure was his. The comments, with their characteristic terseness, were unmistakably his.

He opened the target scraper script. It was a sophisticated piece of software that crawled social media platforms, forums, and public databases, searching for individuals who had posted content mocking loneliness, isolation, or mental illness. The script used sentiment analysis to identify particularly cruel or dismissive comments, then cross-referenced the authors against public records to build detailed profiles. Names, addresses, workplaces, routines. Everything a killer would need.

The script had already compiled a list of seventeen names. Kaya's was the most recent addition, appended just hours ago.

Alan's stomach turned. He barely made it to the bathroom before vomiting into the sink, his body rejecting the implications that his mind could not escape. When he looked up at the mirror, his reflection stared back with hollow eyes and a expression of pure horror.

"I did this," he whispered. "I'm the Reaper."

But even as he said the words, something felt wrong. The scripts were his, yes. The commands were his. But the motivation—the cold, calculated cruelty of the target criteria—felt alien to him. He had spent his life in the shadows, but he had never been violent. He had never been cruel. The loneliness that consumed him was a passive thing, a slow erosion of self, not an active hatred of others.

Unless the loneliness had curdled into something else. Unless the years of isolation had split him in two, creating a second self that could do the things he could not.

He thought of the message that had appeared on his screen: "You created me to be the part of you that could act." He thought of the face in the security footage, wearing his features but not his fear. He thought of the cipher, born in the fluorescent-lit halls of Meridian, now wielded by a killer who shared his memories.

The evidence was overwhelming. But Alan Voss was a forensic investigator at heart, and he knew that evidence could be manufactured. If someone wanted to frame him—if someone had access to his systems and his history—they could have planted the scripts, fabricated the logs, orchestrated the entire nightmare.

He clung to that possibility like a drowning man clinging to driftwood.

The rail yard was a graveyard of rusted boxcars and collapsed warehouses, its tracks long since reclaimed by weeds and wildflowers. Alan arrived two hours before Kaya's ETA, using the time to sweep the area for surveillance devices and establish a secure perimeter. The monitoring program was running on his laptop, recording everything. If he lost time again, if the Reaper surfaced, he would have proof.

He sat on the edge of an abandoned loading platform, his legs dangling over the concrete, and watched the sun sink toward the horizon. The sky was streaked with orange and pink, the colors of a bruise healing. A freight train rumbled in the distance, its horn echoing across the industrial wasteland.

His phone buzzed. Kaya.

"I'm five minutes out. Is the area clear?"

"Clear," he replied. "I'll be at the north entrance. Look for the blue signal light."

He walked to the entrance and waited. The minutes stretched like hours. Every sound—a distant car, a bird taking flight, the creak of settling metal—made him flinch. The Reaper could be anywhere. The Reaper could be anyone. The Reaper could be him.

Headlights swept across the chain-link fence, and a dark sedan pulled into the yard. Kaya stepped out, and despite everything—despite the contract on her life and the chaos consuming his mind—Alan felt something loosen in his chest. She was short and compact, with sharp eyes behind wire-rimmed glasses and hair pulled back in a practical ponytail. She carried a laptop bag over one shoulder and a determined expression on her face.

"Alan." She stopped a few feet away, studying him with the clinical attention of someone who had spent years learning to read people. "You look terrible."

"I know."

"I mean it. When was the last time you ate a real meal? Slept more than three hours?"

"I don't know. Days. Weeks." He ran a hand through his unwashed hair. "It doesn't matter right now. We have bigger problems."

He told her everything—the scripts he had found, the gap in the monitoring logs, the face in the security footage. He showed her the target list with her name at the bottom. He explained the connection to Meridian and the cipher and the messages that appeared as if from nowhere. By the time he finished, the sun had fully set, and they were sitting in the dark, illuminated only by the glow of his laptop screen.

Kaya was quiet for a long moment. Then she opened her own laptop and connected it to his monitoring program.

"I've been thinking about this on the drive," she said. "If you're losing time—if you're doing things you don't remember—there should be a pattern. Triggers. Something that causes the switch."

"Like what?"

"Stress. Exhaustion. Emotional overload." She pulled up a calendar and began marking dates. "When was the last time you remember feeling fully present? Fully in control?"

Alan thought back. The months blurred together, but there were moments that stood out. The day he had retired from the underground, deleting his aliases one by one. The anniversary of his parents' death, spent alone in his apartment with the curtains drawn. The night he had realized he had not spoken to another human being in three weeks.

"The loneliness," he said slowly. "It gets worse at night. When it's quiet. When there's nothing to distract me."

"And that's when the gaps happen?"

He checked the monitoring logs. The timing matched. Every gap, every lost memory, had occurred between midnight and dawn—the hours when the silence became unbearable and his mind began to fracture under its own weight.

"There's something else," Kaya said. She turned her laptop toward him. "I ran a diagnostic on your monitoring program while we were talking. It's logging everything correctly, but there's a secondary process running in the background. Something that's been active for months."

"What kind of process?"

"It's a splitter. It intercepts your keystrokes and network traffic and routes copies to an external server. Someone has been watching everything you do, Alan. Everything."

He stared at the screen. The external server's IP address resolved to a location that made his blood run cold.

Meridian Psychiatric Care Center.

"Someone is operating from there," he said. "Someone who knows me. Someone who has access to my past."

"Or someone who is you." Kaya's voice was gentle but unflinching. "Alan, I need you to consider the possibility that you set this up yourself. That the splitter, the scripts, the contracts—all of it is your own work, done during episodes you don't remember."

"And the external server? Meridian?"

"You could have set that up too. Rented the space, configured the hardware, then forgotten about it. The mind is capable of extraordinary things when it's trying to protect itself from pain."

Alan wanted to argue, but the words died in his throat. He had no proof that he was innocent. Every piece of evidence pointed inward, toward a darkness he did not want to acknowledge.

"There's one way to be sure," Kaya said. "We set up a camera in your apartment. A live feed that I monitor remotely. If the Reaper surfaces, I'll see it happen in real time. And if it's you—if it's really you—then we'll have the proof we need."

"And then what?"

"Then we deal with it. Together. But first, we need to keep me alive for the next forty-eight hours." She smiled grimly. "The contract says I have two days. Let's prove the Reaper wrong."

Alan nodded. The plan was simple, but simple was good. Simple was controllable.

He did not notice the small light blinking on Kaya's laptop—a tiny green dot next to the webcam, active despite the camera being supposedly disabled. He did not notice because he was exhausted, because his mind was fracturing, because he was so focused on the enemy within that he forgot to watch for the enemy without.

But somewhere in the darkness of the Meridian Psychiatric Care Center, a server hummed and recorded and waited. And on its screen, a message appeared, typed by no human hand:

"She knows too much. Move up the timeline. Complete the contract tonight."