Chapter 21
CHAPTER TWENTY-ONE
Bane
Soulless Sinners’ clubhouse, later that same night...
The clubhouse was a tomb at three in the morning.
The kind of silence that made me hyper-aware of every sound—the hum of the servers, the tick of the wall clock, my own heartbeat pounding in my ears.
I’d been staring at code for the past six hours, chasing ghosts through partitions that shouldn’t have existed, bypassing security protocols that shouldn’t have been possible to bypass.
But they were. Because someone had designed them to be.
My fingers flew across the keyboard, muscle memory and desperation driving me deeper into the system’s hidden architecture.
The corrupted sectors I’d found before were just the surface.
A distraction. A deliberate smokescreen meant to draw attention away from the real treasure buried at the root level of the database.
And I was finally, finally breaking through.
The partition opened like a digital flower blooming in fast-motion, layer after layer of encryption peeling back to reveal what lay underneath.
My breath caught as I stared at the code displayed before me.
It wasn’t new. The timestamps proved that.
This architecture had been there since the beginning—since the original system architecture was built.
Someone had embedded it during creation, when every keystroke would have been attributed to the primary user, when no one would have thought to look for unauthorized additions to already-authorized code.
Only one person could have had that kind of access. Only one person had been hands-on during the database’s initial setup.
“You son of a bitch,” I whispered, understanding crystallizing in my mind like ice forming over still water.
George Stone. It had to be. Our dead former president had built a system within the system, a surveillance architecture hidden beneath layers of legitimate function, waiting silently for its purpose to be activated.
The hidden data layer spread across my screen like a map to hell itself. I moved through it methodically, cataloging what I found:
Priority classes: L-A, L-B, L-C, L-D, L-E.
Not arbitrary—they stood for something.
Legacy, maybe? The classifications got more specific from there.
Priority hierarchy markers: H1, H2, H7.
Trigger markers: DORMANT, ACTIVE, PAIR, PREG, MONITOR.
Each one was a breadcrumb leading deeper into a design philosophy I barely recognized. This wasn’t paternity software. This wasn’t medical tracking. This was surveillance. Systematic, deliberate, designed to flag certain genetic combinations, inheritance markers, bloodline overlaps.
My stomach twisted as I started mapping the logic chains.
The system activated only when specific DNA combinations appeared in the database.
It scanned for bloodline overlap—genetic markers that indicated familial relationships.
It assessed pregnancy probability based on hormone levels and medical markers.
It tracked inheritance traits, the kind of genetic signatures that would matter if someone cared about—Jesus Christ.
If someone cared about tracking descendants. Bloodlines. Unborn children.
I pulled up the recent trigger events with trembling fingers. Most of them were old, flagged years ago when the system was first activated. But there were a few recent pings. I scrolled through them, my heart rate climbing with each entry, until—
There.
Brandy.
The name blazed across my screen, and beneath it, an output string that made my blood run cold: PRIORITY LINE DETECTED—OFFSPRING MONITORING ADVISED.
I leaned back in my chair, my mind reeling, my hands shaking. Why? Why would Brandy’s pregnancy trigger this system? What about her bloodline was significant enough to warrant priority monitoring of her unborn child?
Unless.
Unless George hadn’t just built this system to track random people. Unless he’d built it specifically to track certain bloodlines. Certain families. Certain lines of succession that mattered to him for reasons I couldn’t begin to fathom.
The implications crashed over me like a tsunami. This wasn’t about the pregnancy test. This wasn’t about confirming paternity. This was about something so much bigger, so much darker, that I could feel the weight of it pressing down on my chest, making it hard to breathe.
“George,” I whispered, staring at the code displayed before me, at the evidence of his machinations still active in the heart of our infrastructure, “what the fuck were you actually doing?”
But I already knew the answer. Or at least, I knew enough to understand that someone needed to find out—and they needed to find out fast. Before this mystery unraveled in ways none of us could control.
I closed the partition and sat in the darkness of my office, the server’s hum a constant reminder that somewhere in this digital architecture, George Stone’s legacy was still watching.
Still waiting.
Still monitoring.