home

search

Chapter 50: The Blueprint

  David didn’t analyze the design documents immediately.

  For the first time since entering the Rules World, he allowed himself a period of non-productivity. He sat in the Engine Room’s command chair while Michael flew the Express through a series of randomized spatial jumps designed to shake any tracking, and he did nothing. He stared at the viewport. He breathed. He didn’t calculate, didn’t plan, didn’t run simulations.

  The summoner interface in the corner of his vision was still there: a slot that had held the Shadow Bear Spirit for what felt like a lifetime and now displayed the word VACANT in system-standard blue text. The system treated the loss as a status update. A cleared variable. An empty pointer where a living thing had been.

  David had classified the Bear as an asset. He’d told Michael as much. "It’s a summon. A combat asset." And he’d deployed it as one—sent it into a fight it couldn’t win, asked it to buy time with its life, and gotten exactly the result he’d planned for.

  The Bear had looked at him. In the moment before it dissolved. Those gold eyes, turning toward him, making the purring sound one last time. Not a sound of distress. A sound of—

  David didn’t finish the thought. He wasn’t ready to name what the sound had been, because naming it would require acknowledging that he’d asked something that trusted him to die for a download, and the download had better be worth it.

  Razor’s extraction was clean. Michael rendezvoused with him at a waypoint three dimensional layers removed from the gateway zone. The scarred veteran climbed aboard the Express with new scratches on his armor and an expression of grim satisfaction.

  "Nine patrols," Razor reported. "Lost three in the scaffolding collapse. Outran four. The last two gave up when I crossed into a destabilized zone they weren’t willing to enter." He sat down heavily. "I’m getting too old for this."

  "You’re the best survivor I’ve ever met," David said. It was the first thing he’d said in two hours.

  Razor looked at him oddly. "You okay?"

  "The Bear is gone."

  Razor’s expression changed. The tactical assessment dropped away, and what remained was the face of someone who’d lost companions before and understood that the loss didn’t get smaller with repetition.

  "I’m sorry," Razor said. Nothing else. He’d been in enough dungeons to know that elaboration didn’t help.

  David nodded once. Then he opened the design documents.

  The data flooded his system interface—terabytes of architectural specifications, energy flow calculations, dimensional alignment matrices, construction timelines, and the theoretical framework underlying the entire project. It was, in CS terms, the most comprehensive codebase David had ever encountered: the source code for a machine that punched holes between dimensions using harvested human consciousness as fuel.

  He read for six hours. Not the surface documentation—the deep architecture. The energy routing logic. The dimensional alignment algorithms. The safety interlocks that prevented the bridge from destabilizing during construction. The override protocols that the Board of Directors had installed to maintain exclusive control of the completed structure.

  This story is posted elsewhere by the author. Help them out by reading the authentic version.

  And he found what he was looking for.

  The bridge was bidirectional. The Consortium had designed it for ascension—to carry the Board from the Alpha server to the Beta-Tier. But the physical structure didn’t have an inherent direction. Energy could flow either way. The directionality was controlled by software—a routing parameter in the bridge’s core logic that specified the energy flow vector.

  Change the parameter, change the direction.

  But there was a problem. The routing parameter was protected by a lock that required simultaneous authentication from three of the Board’s five members. A multi-party verification system designed to prevent exactly the kind of unilateral override David was planning.

  Three of five. David couldn’t spoof Board-level credentials—they were maintained in the Beta-Tier itself, outside his access scope. And even his Warden permissions couldn’t override a lock that existed at a higher dimensional level.

  He needed three Board members’ credentials. Which meant he needed three Board members.

  David closed the documents and looked at the map. The Consortium’s crimson nodes pulsed across the Abyss. Regional Executors. Facility Overseers. Supply chains and communication relays and the vast, bureaucratic machinery of an organization that had been exploiting the Rules World for longer than David had been alive.

  Somewhere in that machinery, there were cracks. Power struggles. Dissent. Competing agendas among the Board members. In any organization of sufficient size, the biggest vulnerability wasn’t the firewall—it was the people behind it.

  "I need intelligence," David said. "Not on the Consortium’s infrastructure. On its politics. Who on the Board disagrees with whom. Who has ambitions that conflict with the current plan. Who might be willing to authenticate a parameter change if they thought it served their interests."

  Michael and Razor exchanged a look.

  "You’re going to hack the Consortium’s leadership structure," Michael said.

  "I’m going to social-engineer it. The bridge’s lock requires three out of five Board members. I don’t need all five. I don’t need any of them to agree with what I’m doing. I just need three of them to authenticate at the same time, for reasons they each believe serve their own goals."

  "A man-in-the-middle attack," Michael said slowly, "on the most powerful people in the Abyss."

  "Exactly."

  Razor cracked his knuckles. "So we’re going from dungeon-running to corporate espionage."

  "We were always doing corporate espionage. The corporations were just wearing monster costumes." David turned back to the console. "Archivist, are you still on the channel?"

  A pause. Then: "I’m here. My account reactivated. I’m in the Hub."

  "I need you to build me a dossier on the Genesis Consortium’s Board of Directors. Five members. Everything: names, operational history, known disagreements, personal objectives, political alliances. Use the scavenger networks. Use whatever contacts you’ve accumulated in 2,847 cycles. Money is not an issue—I have points to burn."

  "How long do I have?"

  David looked at the bridge completion percentage on the map. 68.4%. Still climbing.

  "As long as it takes to do it right. But not a second longer."

  He closed the channel and sat in the command chair, the empty summoner slot glowing VACANT in his peripheral vision, the bridge’s blueprints burning in his memory, and the shape of the next phase crystallizing in his mind.

  The first volume of his story had been about survival—learning the rules, exploiting the bugs, staying alive long enough to understand the system he’d been trapped in.

  The second volume would be about something larger. Not breaking the rules. Not even rewriting them.

  Building new ones.

  David pulled up the navigation console and began planning the most complicated social engineering operation in the history of the Abyss.

Recommended Popular Novels