Chapter 21 : The Vera Problem
[Plan Exodus: Day 1 — Intelligence Phase]
Phase One of the operation was simple in concept, difficult in execution: know your enemy better than he knows himself.
Fernando Vera had survived in the drug trade for years—not through brute force alone, but through a combination of charisma, unpredictability, and a network of loyal soldiers who would kill or die at his command. Taking him on directly was suicide. But every organization had weak points, and finding them required the kind of deep intelligence work I'd spent two months preparing for.
"GHOST, initiate comprehensive target analysis. I want everything: communication patterns, financial flows, personnel movements, security protocols. All of it."
"Acknowledged. Beginning multi-vector intelligence gathering. Note: some methods will require social engineering of external parties. Others will require direct system intrusion. Risk assessment for each approach will be provided before execution."
I cracked my knuckles and pulled up the first terminal window. Time to go to work.
The phone records came first.
Vera himself was careful—multiple burner phones, irregular usage patterns, minimal digital footprint. But his crew was sloppier. DJ used the same device for calling his mother and coordinating drug deals. Two street-level dealers had Instagram accounts where they posted pictures that, with careful analysis, revealed regular locations and schedules.
I spent six hours on day one just building the communication map. Who called whom, how often, at what times. The patterns revealed hierarchy: DJ was the hub, connecting Vera to the lower ranks. Remove DJ, and the communication network fractured. But removing DJ would immediately alert Vera that someone was targeting his organization.
"Not an option. Not yet."
The financial flows were harder to trace. Vera wasn't stupid enough to use banks for drug money, but some of his crew had legitimate jobs—cover employment that showed up in public records. Cross-referencing those records with known addresses and phone data let me build a map of safe houses and stash locations.
[+8 XP — Intelligence gathering: communication network mapped]
"GHOST, analysis on the girlfriend."
"Vera maintains a relationship with Elena Ruiz, age 24, employed as a waitress at a restaurant in the Bronx. Social media indicates genuine emotional attachment on both sides. Vera visits her apartment approximately three times per week, typically staying overnight. Security at her location is minimal compared to his primary residences."
A vulnerability. Vera was human, which meant he had human weaknesses—people he cared about, places he felt safe, routines that made him predictable.
I filed the information away. Not for use against Elena—she was an innocent in all this—but as data about Vera's psychology. He wasn't a machine. He had blind spots.
Day two and three were physical surveillance.
I'd rented a car using Daniel Marsh's identity—a forgettable sedan that would blend into any neighborhood. The first night, I parked three blocks from Vera's primary location and watched through binoculars as his crew went about their business.
The operation ran like clockwork. Dealers rotated in four-hour shifts. Money collections happened at predictable intervals. DJ made rounds every evening, checking on personnel and collecting reports.
"Routines. Predictable routines."
The second night, I followed DJ's car from a safe distance. He made five stops over three hours, each one logged and mapped. The route never varied—same locations, same times, same pattern.
"GHOST, calculate optimal intercept points if we needed to isolate DJ from support."
"Three locations identified where DJ is alone for periods exceeding five minutes. All are within areas of reduced camera coverage. However, direct action against DJ would trigger immediate organizational response. Recommend alternative approaches."
I wasn't planning to hurt DJ. But knowing where he was vulnerable told me something about the organization's structure—where the weak points were, how information flowed, what would happen if those flows were disrupted.
The third night, I found the basement.
It was in a building that looked abandoned from the outside—boarded windows, graffiti-covered walls, the kind of place nobody would look twice at. But the basement lights were on at 2 AM, and the stream of visitors told a different story.
"GHOST, cross-reference address with known Vera properties."
"No direct connection found. However, property records show ownership by a shell company with ties to individuals in Vera's extended network. Probability this is a operational location: 87%."
This was where Vera did his real business. Not the street deals or the money collections, but the meetings, the planning, the conversations that never happened on phones that might be tapped.
I photographed everything I could from my position three blocks away. Faces, license plates, arrival times. The intel file was growing by the hour.
By day four, I had a comprehensive picture of Vera's operation—and a problem I hadn't fully anticipated.
"GHOST, summarize Shayla Nico's role in the organization."
"Based on accumulated intelligence: Shayla Nico is not a standard street-level dealer. She provides access to prescription medication sources—likely through connections in healthcare or pharmacy sectors. This makes her uniquely valuable to Vera's operation. Replacement would require significant effort and expose the organization to new risks."
"She's not just useful. She's essential."
The implication was clear: when Shayla disappeared, Vera wouldn't just accept the loss. He would hunt. He would use every resource at his disposal to find her, because losing her meant losing a supply chain that couldn't be easily replaced.
The extraction plan needed another layer. Something that would neutralize Vera's ability to search, or at least slow him down long enough for Shayla to disappear completely.
"Options analysis," I said, staring at the web of photos and notes covering my wall.
"Three primary approaches identified. First: misdirection. Create false trail suggesting Shayla fled to another city or was taken by a rival organization. Requires fabricated evidence and significant operational security."
"Risky. If he sees through it, we're worse off than before."
"Second: distraction. Time extraction to coincide with major disruption to Vera's operation—law enforcement action, rival conflict, or organizational crisis. Vera's attention would be divided, reducing resources available for pursuit."
"Depends on external factors we can't control."
"Third: neutralization. Take direct action against Vera's ability to pursue—damage to communication infrastructure, exposure of operations to law enforcement, or physical incapacitation of key personnel."
"That's war."
"Yes. That is why it was listed third."
I rubbed my eyes, exhaustion starting to catch up with me despite the adrenaline. The surveillance had taken its toll—three nights of minimal sleep, hours of careful observation, the constant low-level stress of operating in enemy territory.
The burger I'd eaten at 3 AM on night two sat heavy in my stomach. Cold fries, melted shake, the taste of desperation. But it had been the best meal of the week, because I'd been doing something that mattered instead of just preparing to do something.
"GHOST, there has to be another option. Something that protects Shayla without starting a war I can't win."
"One additional possibility exists, though it introduces significant complexity. Vera's organization is built on loyalty and fear. If that loyalty could be undermined—if key members could be turned or convinced that Vera is a liability—the organization's ability to pursue would be significantly reduced."
Turn someone. Flip one of Vera's people and use them to create chaos from the inside.
"Who's the weakest link?"
"Insufficient data for confident assessment. However, analysis suggests DJ may have motivations beyond simple loyalty. His communication patterns indicate regular contact with individuals outside the organization, including what appears to be a family in Queens. Vera's lifestyle is incompatible with stable family relationships. DJ may be experiencing conflict between organizational loyalty and personal desires."
The enforcer who'd warned me off weeks ago. The lieutenant who held Vera's operation together.
If I could flip him—or even create doubt in his mind—the entire structure could wobble at a critical moment.
"That's not a two-week plan. That's months of work."
"GHOST, is there any way to accelerate that timeline?"
"Potentially. However, approaching DJ directly carries extreme risk. He is loyal to Vera and has already identified you as a potential threat. Any contact would be interpreted as hostile action."
Another dead end. Another path that led nowhere useful.
I stood up from the desk and walked to the window, looking out at Brooklyn in the predawn darkness. The city was quiet except for the distant sound of traffic and the occasional car passing below.
Somewhere in that darkness, Vera was sleeping peacefully in his girlfriend's apartment, unaware that someone was building a map of his weaknesses. Somewhere else, Shayla was probably lying awake, wondering if her life would ever be her own again.
"There has to be a way."
I turned back to the wall of photos and notes—my conspiracy board, dedicated to one woman's freedom. The answer was in there somewhere. I just had to find it.
[+12 XP — Intelligence gathering: organizational structure mapped]
"GHOST, compile everything into a single encrypted file. I want to be able to access it from any location."
"Compiling. File designation: VERA_INTEL_COMPLETE. Recommend multiple backup locations."
The file would be my weapon. Not a gun or a knife, but information—the currency that could unlock doors no amount of force could open.
I sat back down and started reviewing everything again, looking for the angle I'd missed. The weak point that would let me solve the Vera problem without starting a war.
The clock on my laptop read 4:47 AM. Dawn was coming. Another day closer to the execution window.
"Somewhere in this mess is the answer."
I had ten days left to find it.
The next morning, I woke up with the ghost of an idea.
It came from something I'd noticed in the phone records—a pattern I'd dismissed as insignificant but which now seemed pregnant with possibility. Vera's crew communicated in predictable ways, but one thread stood out: calls to a number that didn't match any known associate, made at irregular intervals, always from Vera himself.
"GHOST, can you trace that number?"
"Attempting. Initial results suggest the number is associated with a prepaid device, location data unavailable. However, call timing correlates with periods of organizational stress—after arrests, during territory disputes, following significant events."
Someone Vera called when things got complicated. A lawyer? A fixer? Someone with enough pull to help when problems arose?
If I could find out who was on the other end of that line, I might have the leverage I needed.
"Add it to the priority list. That number could be the key to everything."
The investigation wasn't over. It was just getting started.
But for the first time since beginning Plan Exodus, I could see a shape forming in the darkness—the outline of a solution that might actually work.
Ten days. I had ten days to turn that outline into reality.
The clock was ticking. And I was finally ready to race against it.
To supporting Me in Pateron .
with exclusive access to more chapters (based on tiers more chapters for each tiers) on my Patreon, you get more chapters if you ask for more (in few days), plus new fanfic every week! Your support starting at just $6/month helps me keep crafting the stories you love across epic universes.
By joining, you're not just getting more chapters—you're helping me bring new worlds, twists, and adventures to life. Every pledge makes a huge difference!
👉 Join now at patreon.com/TheFinex5 and start reading today!