Chapter 14: Tier Four

It took me forty-two minutes to navigate into his server.

I worked from a clean rig, borrowed from a contact who owed me favors—which meant I owed them future favors, which meant this arrangement was already accruing interest I'd have to pay back later. The access codes Ryker had given me were military-grade encryption, the kind that suggested either corporate training or a very thorough self-education in network security. Each code was a key to a different level of the architecture. Each level was compartmentalized, isolated, designed so that someone could access one area without being able to see or move through the rest.

Smart. Professional. Paranoid in exactly the right way.

The first level opened into something that looked like a standard server farm topology—nothing unusual. Nothing that explained why Ryker's network had been so difficult to breach. I moved deeper, using the second code. Then the third.

And then I stopped moving.

The architecture changed at the fourth level. Instead of the cold efficiency of corporate systems, where everything was optimized for speed and processing power, Ryker's servers were organized differently. Each data partition was separated not just by function but by purpose. Access paths were redundant, built for recovery. There were multiple routes to every critical system, which meant that if one pathway got compromised, the data wouldn't cascade down like dominoes.

More than secure, it was careful.

I sat back from the terminal. The rig's screen reflected in my eyes—green text on black, a visual representation of someone's mind laid out in code and architecture. Except it wasn't laid out like most people's security systems. Most network architects built firewalls because they didn't trust the outside world. Ryker's server was built like someone who didn't trust his own infrastructure. Like he was planning for the day when something inside the system itself would break.

The compartmentalization went deeper. Each section had its own backup protocols. Each backup had its own encryption. The redundancy was obsessive. It was the architecture of someone who'd seen critical data fail before and had decided that would never happen to him again.

I spent the next eighteen minutes mapping the structure. Tier One: core identity data, scrubbed profiles, the legal fiction that made him look clean to anyone who wasn't looking too hard. Tier Two: operational records, transaction logs, the real history of his work in the gray market. Tier Three: security systems, encryption keys, the technical infrastructure that kept everything running. Tier Four was locked.

I tried the access code. Nothing.

"There's a Tier Four," I said, without looking away from the screen. Ryker was somewhere in the building—I could hear him moving in the office above me, a faint weight on the floorboards. "You didn't give me a code for it."

He appeared in the doorway a moment later. "That's not part of the deal."

"I need to know what's in there before I retrieve the core."

"It's not connected to the core. It's not part of your network integration. You don't need access."

I turned to look at him. "You gave me master keys. Except you didn't. You gave me everything except the part of your infrastructure that actually matters."

"It doesn't matter for this operation."

"Doesn't matter to you or doesn't matter to me?"

He didn't answer immediately. I could see him working through the calculation, figuring out whether telling me the truth was worth the security risk. Ryker Vance was better at reading people than I'd thought. He was reading me right now—checking whether I was the kind of operator who needed to know everything for psychological security or whether I was the kind who just needed the operational knowledge to do the job.

"It matters to me," he finally said. "That's not part of what you're being paid for."

I turned back to the screen. There was something in his tone that made it clear this wasn't a negotiation. It was a boundary. And maybe because I understood the architecture well enough now, or maybe because something in that boundary felt honest in a way that made sense, I didn't push.

Instead, I navigated to Tier Two.

The neural core retrieval pathway was nested three levels down in the operational records. Every extraction point was documented—not the contents, but the signature. Seventeen cores pulled in the last three years, each one logged with a timestamp, a location marker, and a security flag status. The most recent entry was mine. The one with the SILKSCREEN wipe marker. The one with my encryption cipher locked inside it.

I pulled the retrieval pathway and started setting up the access tunnel. The system was designed for precision work—you could pull data in clean containers, isolated and protected, without letting the operating environment corrupt it. That was why Ryker was good at this work. He didn't just know how to move data. He knew how to protect it while it was in transit.

Within twenty minutes, I had a pathway established. Within another five, I had a clean containment file ready to receive the core's contents.

"It's ready," I said.

Ryker appeared in the doorway again, a small quantum drive in his hand. He set it on the desk next to the rig. The case was matte black, identical to a dozen others, but there was something about the weight of it that felt different. Maybe because I knew what was inside. My memory. My encryption signature. The technical structure that made me invisible in the gray market.

"The retrieval will take approximately thirty seconds," I said. "The system's going to run an integrity check automatically. If the data's corrupted, the whole thing fails."

"It won't be corrupted."

I didn't ask how he knew. Instead, I slotted the drive and executed the retrieval.

Thirty seconds. The screen cycled through status indicators—data flow rate, integrity percentage, error detection. Everything stayed green. Everything moved clean.

When it finished, the integrity check completed with a single line: VERIFIED.

I ejected the drive and held it for a moment. This was the neural core that had cost me two years of investigation, two years of exposure, two years of learning that someone in SILKSCREEN had my private encryption key. This was the thing I'd been hunting. And now it was sitting in my hand, the size and weight of a piece of candy.

"Thank you," I said, because there wasn't anything else to say.

"We're even until you move the data," Ryker said. "Once that happens, we're square."

I looked at his server architecture one more time before I stood up. The Tier Four section sat there, locked and inaccessible, a part of his mind that he'd decided I didn't need to see. That had bothered me five minutes ago. But sitting here now, holding the quantum drive with my own neural data inside it, I understood why he'd kept it sealed.

Some things weren't meant to be shared—not because they were dangerous, but because they were careful.

And Ryker Vance had built an entire infrastructure around the concept of being careful—about his data, about his operations, about the few people he'd decided to trust.

That told me something about him that I wasn't sure I wanted to know. Something about whether the walls he'd built around himself were walls to keep people out or walls to keep himself in.

I packed the quantum drive into an encryption pouch and sealed it against scanning. "I'll have your data moving by tomorrow night."

"Good," he said.

But he was still looking at the terminal, at the map of his own architecture laid out in green text and black space. Ryker Vance was the kind of operator who'd built his entire existence around having control. Control over his data, control over his infrastructure, control over the information that moved through the market around him.

And he'd given me access to that. Not all of it. Not the part locked behind Tier Four.

But enough to know that everything in his system, all the compartmentalization and redundancy and careful design—it wasn't built to be impenetrable. It was built to survive.