Chapter 17
GHOST
"This is everything he's distributed so far," I explained, displaying the files on my main monitor for Steel and Daisy to see.
Three days since the hospital confrontation, and I'd been tracking Brandon Mitchell's digital footprint with ruthless precision. What I'd found confirmed my worst security assessment.
Steel leaned closer, studying the screen with narrowed eyes. "How widely distributed?"
"Limited current circulation," I replied. "Dark web forums. Private messaging channels. Select individuals with known rival club connections."
Daisy stood silent beside me, face pale as she took in the collection of photos, location data, and club information Brandon had compiled from her content. Images I'd approved as security-compliant now displayed with red highlights showing vulnerable details I'd missed.
Security failure. My failure.
"It's my fault," Daisy said quietly. "My content. My photos."
"Negative," I countered immediately. "Security oversight was my responsibility. Vulnerability assessment incomplete."
Steel straightened, his expression grim but controlled. "Damage assessment?"
I pulled up my analysis matrix. "No immediate operational threats. No chapel images. No direct evidence of illegal activity. Primarily architectural details, member identification, business operations."
"Enough to facilitate surveillance," Steel noted.
"Affirmative," I acknowledged. "Particularly combined with Brandon's personal observations from following Daisy."
The knowledge sat like lead in my system. I'd implemented countless security protocols, monitored every digital channel, tracked physical movements—and still missed the vulnerabilities in content I'd personally approved.
Unacceptable failure.
I'd retreated to my tech cave the moment we'd returned from the hospital, diving into code, hunting digital traces with the focused intensity that had kept the club secure for years.
Three days with minimal sleep, maximum caffeine, running on operational necessity and simmering rage I refused to acknowledge.
Daisy had tried to draw me out—bringing food I didn't eat, asking questions I answered with minimal information, eventually giving up and leaving me to my digital hunt.
Distance was necessary. Focus required isolation. Emotional responses impaired analytical efficiency.
That's what I told myself as I pushed her away.
"This changes our security posture," Steel stated, pulling me back to the present briefing. "Club-wide protocols need updating."
I nodded, already three steps ahead. "Implementation underway. Perimeter systems reconfigured. Access codes changed. Movement patterns altered."
"And Mitchell?" Steel asked, the question carrying clear implications.
"Under continuous surveillance," I reported. "Currently at Riverdale Inn. Maintains regular communication with unknown contacts. Digital traces suggest preparation for content distribution to wider audience."
"He's going to release everything," Daisy said, speaking for the first time since her earlier self-blame. "Going nuclear because I wouldn't come back to Chicago with him."
The assessment was accurate, if incomplete. My surveillance suggested more calculated motivation—financial gain, potential leverage, targeted damage.
"Can we shut him down?" Steel asked. "Your usual digital countermeasures?"
I hesitated, weighing operational honesty against protective instinct. "Technically feasible. Legally problematic. Evidence trail would lead directly to club resources."
"Do it anyway," Daisy said suddenly, her voice stronger. "I'll take responsibility. Say I hired a security consultant. It was my content he stole."
"Negative," Steel and I responded simultaneously.
"Club handles its own problems," Steel added. "No civilian exposure."
I nodded agreement, though for different reasons than Steel likely assumed. My concern wasn't just club security but Daisy's protection—both physical and legal.
"Implementation of aggressive digital countermeasures remains available option," I stated. "Currently monitoring for optimal intervention timing."
Steel studied me for a moment. "Your call on timeline. You've got full operational authority on this."
The responsibility weighed heavily. Not just club security now, but Daisy's safety. Her father's recovery. The balance between neutralizing threats and avoiding escalation that might endanger civilians.
"Understood," I acknowledged.
Steel glanced between us, clearly sensing the tension, before nodding toward the door. "I'll update the brothers. Continue monitoring. Regular reports."
After he left, silence filled the tech cave. Daisy remained standing beside my chair, close enough that I could sense her presence without looking up.
"You should rest," she said quietly. "You've been at this for three days straight."
"Operational necessity," I replied, eyes fixed on my screens. "Security breach requires immediate containment."
"Ghost."
Something in her tone—soft but insistent—made me finally look up. The concern in her expression was unexpected. Unsettling.
"You can't fix this through sheer willpower and caffeine," she continued. "Even you need to sleep sometimes."
"Incorrect assessment," I countered, though my body's physical symptoms suggested otherwise. "Functionality maintained within acceptable parameters."
Daisy sighed, then did something completely unexpected. She pulled a chair beside mine and sat down, close enough that our arms nearly touched.
"Talk to me," she said simply. "What are you really doing down here?"
The question penetrated defenses weakened by exhaustion and self-recrimination.
"Correcting security failures," I answered, more honestly than intended. "Identifying vulnerabilities. Implementing countermeasures."
"You mean punishing yourself," she translated. "For not being perfect. For not anticipating every possible way Brandon might use my content."
Her perception was unsettling. Accurate in ways I wasn't prepared to acknowledge.
"My responsibility," I stated flatly. "Security oversight. Threat assessment. Protection implementation."
"No one could have predicted everything he'd do," Daisy argued. "Not even you, Ghost."
I turned back to my monitors, unwilling to accept the absolution she offered. "Prediction is precisely my function. Pattern analysis. Threat anticipation. Prevention before necessity of response."
Her hand settled lightly on my arm, the touch sending unexpected awareness through my system.
"You're not a machine," she said quietly. "You're human. Humans miss things sometimes."
The simple statement struck with surprising force. The fundamental flaw in my security systems exposed—not technological vulnerability but human limitation. My own.
"Unacceptable," I responded, the word coming out rougher than intended.
"Maybe," she acknowledged. "But it's reality. And now we deal with it. Together."
Together. The concept was foreign to my operational framework. Security was my domain. My responsibility. My failure to correct.
Yet something in her steady gaze suggested a different approach. An alternative to isolation and self-recrimination that had been my default response to failure since childhood.
"I have an idea," she said when I didn't immediately respond. "Something Brandon wouldn't expect. A different kind of countermeasure."
Interest stirred despite my exhaustion. "Explain."
"Instead of just trying to contain what he's already shared, we flood the zone," she suggested. "Create so much positive, controlled content about the club that his information gets buried. Make his 'exposé' look like old news compared to what we're intentionally sharing."
The strategy was unexpected. Counterintuitive to security protocols.
Yet tactically sound from an information warfare perspective.
"Controlled narrative overwhelming targeted leaks," I said slowly, considering the approach. "Digital dominance through volume rather than restriction."
Daisy nodded, watching my reaction carefully. "Exactly. We can't put the genie back in the bottle, but we can make sure our version of the story is what people see first."
It was the opposite of my instinctive response—to lock down, restrict, contain. Instead, she proposed expansion, visibility, controlled exposure.
"Viable counterstrategy," I acknowledged. "Requires precise implementation. Content coordination. Security review."
"That's where you come in," she said, a small smile forming. "We work together. Your security knowledge, my content expertise."
"Together," I repeated, the concept becoming less foreign with her proximity.
The exhaustion I'd been fighting crashed through my defenses suddenly, three days of minimal sleep and maximum stress demanding payment.
Daisy noticed immediately. "First, you sleep. Four hours minimum. Then we start planning."
I should have argued. Should have maintained operational focus. Should have insisted on continued monitoring.
Instead, I found myself nodding. "Four hours. Then implementation."
Her smile widened slightly. "Deal."
As I finally stood, muscles protesting the movement after days of stillness, Daisy stayed close—not touching, but present in a way that registered as support rather than intrusion.
"Ghost," she said as we reached the door. "This isn't your fault. None of it."
The absolution still felt unearned. Undeserved. Yet something in her steady gaze made me want to believe it could be true.
And that desire, more than anything else, warned me that my professional distance was compromised beyond any hope of recovery.