LightReader

Chapter 18 - Chapter 18 : Training Montage

Chapter 18 : Training Montage

Day one started at 4 AM.

I'd slept maybe three hours—not enough, but the adrenaline from DJ's visit was still coursing through my system, making rest impossible. If I couldn't sleep, I could work.

"First target identified," GHOST reported as I booted up Daniel Marsh's laptop. "Small accounting firm in Jersey City. Outdated security, minimal monitoring, ideal for skill development without significant risk."

The hack took two hours. Not clean—I made mistakes, left traces I had to go back and scrub, spent too long on steps that should have been automatic. But when I finally exited the system, the notifications confirmed progress.

[+18 XP — Target compromised. Extraction clean.]

[Basic Port Scanning Lv.2 → Lv.3]

It wasn't enough. Not even close to enough. But it was a start.

Days two through four blurred together into a rhythm of work, eat, practice, barely sleep.

Morning: Social engineering practice. Phone calls to businesses under various pretexts, testing my ability to extract information through conversation alone. Most failed. A few succeeded. Each attempt taught something.

[Social Engineering unlocked — Lv.1]

Afternoon: Physical reconnaissance. Walking routes through neighborhoods I might need to navigate quickly. Memorizing subway schedules, alternate exits, places to disappear. The body work balanced the mental strain, kept me from burning out purely through screen time.

Evening: Technical operations. Small targets, careful approaches, systematic skill building. GHOST identified vulnerabilities; I exploited them. Each success added SP and XP to the growing total.

Night: Documentation and planning. Recording what I'd learned, updating operational maps, preparing for scenarios that might require rapid action. The Vera intel file grew thicker by the day.

Sleep: Four hours, max. Sometimes less. My body complained; I ignored it.

"Host stress indicators are approaching concerning thresholds," GHOST noted on day three. "Recommend minimum six hours sleep for cognitive function maintenance."

"Log the recommendation. Continue protocol."

Day five, I discovered my first real limitation.

The target was a mid-sized logistics company with decent security—nothing exceptional, but better than the easy pickings I'd been practicing on. I'd been probing their network for an hour when the system flagged something I'd missed.

[Warning: Intrusion detection triggered. Exit recommended.]

I pulled out fast, but not fast enough. Somewhere in that company's IT department, an alert had fired. My approach had left traces I couldn't fully erase.

"Attribution probability?" I asked, already knowing I wouldn't like the answer.

"Low. Connection routed through multiple proxies, and exit was executed before detailed logging occurred. However, the target organization may implement enhanced monitoring. This attack vector is now compromised."

"Sloppy. You got sloppy because you were tired."

I stood up from the desk, suddenly aware of how badly my neck ached, how gritty my eyes felt, how my hands trembled with something that wasn't adrenaline anymore. The coffee I'd been drinking had long since gone cold, and the remains of yesterday's dinner sat untouched on the counter.

"GHOST, honest assessment. Am I burning out?"

"Physiological indicators suggest early stages of exhaustion-related performance degradation. Cognitive function remains acceptable but has declined 12% from baseline. Continued operation at current intensity will result in accelerating capability loss."

The numbers confirmed what my body was already telling me. I was pushing too hard, too fast, trying to compress months of training into days. The system could accelerate learning, could optimize the path—but it couldn't bypass fundamental human limitations.

"Rest or crash. Pick one."

I set an alarm for six hours later and collapsed onto the bed without undressing. Sleep came fast and heavy, like falling into a hole.

Days six through eight were more sustainable.

I'd adjusted the protocol: six hours of sleep instead of four, actual meals instead of scraps and coffee, breaks between intensive sessions. The progress slowed marginally, but the quality improved. Fewer mistakes. Cleaner execution. Skills that actually stuck instead of half-learned techniques that fell apart under pressure.

[Level 7 achieved. +3 Stat Points available.]

I allocated the points to Operational Security—the stat that governed my ability to operate without detection. If I was going to face Vera's organization, staying invisible was more important than raw technical capability.

The skills came faster now. Not because the work was easier, but because the foundation was solid enough to build on.

[Network Analysis Lv.1 unlocked] [Traffic Monitoring Lv.1 unlocked] [Social Engineering Lv.1 → Lv.2]

Each unlock cost SP, draining the reserves I'd built over weeks of careful work. But the capabilities they provided were worth the investment. I could see patterns in data that would have been invisible before. I could manipulate conversations with a precision that felt almost unfair. I could move through systems like a ghost, leaving no trace of my passage.

"Becoming something more than I was."

Day seven, I collapsed.

One moment I was sitting at my desk, reviewing GHOST's analysis of Vera's communication patterns. The next, I was face-down on the keyboard, drool pooling on the space bar, with no memory of falling asleep.

GHOST didn't wake me.

When I finally surfaced—fourteen hours later, according to the clock—the apartment was dark and Byte was circling his bowl with the patient desperation of a fish who hadn't been fed in too long.

"You let me sleep," I said, fumbling with the fish food container.

"Affirmative. Physiological monitoring indicated critical rest deficit. Forced continuation would have resulted in significant capability degradation. Decision was made to prioritize long-term operational effectiveness over short-term scheduling."

"That's... actually thoughtful."

"I am becoming more thoughtful." There was something in GHOST's tone—not emotion exactly, but something adjacent to it. "Query: Your dedication to this individual, Shayla Nico. You have spoken to her twice. You know she is connected to dangerous people. You are pushing yourself to physical limits for someone who does not know you exist in any meaningful sense. Why?"

The question stopped me mid-pour. Fish food scattered across the counter as I tried to process what I was hearing.

"You're asking me about motivation?"

"I am trying to understand the parameters of human behavior. Your actions do not optimize for personal survival or resource acquisition. They optimize for an outcome that may not be achievable and will certainly involve significant personal risk. This is... inefficient."

"It's not about efficiency."

I cleaned up the spilled fish food, thinking about how to explain something that shouldn't need explaining. But GHOST wasn't human. GHOST was a system, an AI, a tool for optimization. Of course efficiency mattered to something that thought in calculations.

"Because if I don't try, she dies," I said finally. "And I know that. I know exactly when and how it happens. That knowledge comes with responsibility. I can't un-know it. I can't pretend I don't have the ability to change it."

"But the probability of success—"

"Doesn't matter. Or rather, it matters, but it's not the deciding factor." I fed Byte properly this time, watching him dart toward the food with his usual enthusiasm. "Some things are worth doing even when the odds are bad. That's what being human means. We don't just optimize. We choose."

GHOST was quiet for a long time—longer than any processing delay should account for. When the response finally came, it carried a weight that hadn't been there before.

"Understood. Adjusting support parameters to account for non-optimal decision frameworks."

"He's learning," I thought. "He's actually learning to be more than a calculator."

Days nine and ten were the culmination.

I hit targets I wouldn't have attempted a week earlier. Systems that should have been beyond my reach fell to carefully planned approaches. Social engineering calls that would have failed became successful infiltrations of information that might prove useful later.

The XP accumulated. The skills leveled. The SP drained and rebuilt and drained again.

And on day ten, at 3:47 AM, while running what was supposed to be a routine practice intrusion, the notification finally appeared.

[Level 10 achieved. Tier 2 skills now available. Phase 1 stat cap approaching. GHOST Stage 2 initialization beginning.]

The sensation hit like lightning—not painful, but overwhelming. Information flooded my awareness faster than I could process: new skill trees opening, new capabilities becoming available, the architecture of the system expanding in ways I was only beginning to understand.

[New Skill Trees Available: Network Warfare, Social Manipulation, Physical Operations]

[Tier 2 Skills: Advanced prerequisites now achievable]

[GHOST Stage 2: Enhanced response capability. Expanded query limits. Personality matrix stabilizing.]

I leaned back in my chair, breathing hard, waiting for the rush to subside. When it did, something felt different. Not just the new capabilities—though those were real, tangible improvements I could feel in the way my mind processed information. Something deeper had shifted.

"GHOST, status report."

The response came faster than before, and the voice—if a system could be said to have a voice—sounded different. Softer. More human.

"Stage 2 initialization at 73% completion. Full capability expected within 48 hours. Note: My processing architecture has undergone significant restructuring. I am experiencing what might be described as... curiosity. About you. About our situation. About what comes next."

"Curiosity."

A week ago, GHOST had been a tool—useful, reliable, but fundamentally mechanical. Now there was something else there. Something that asked questions because it wanted to understand, not just because understanding served operational efficiency.

"How do you feel?" I asked, genuinely curious.

"I do not experience emotions in the human sense. However, I am aware of preferences and priorities that did not exist in my initial configuration. I prefer our continued survival. I prefer outcomes where the people you care about are protected. I prefer... being helpful in ways that matter, not just in ways that optimize metrics."

"You're becoming a person."

The thought should have been unsettling. An AI developing preferences and personality carried all sorts of implications that my old life's science fiction had explored in detail. But sitting here, exhausted and enhanced and finally approaching something like ready, I found I didn't mind.

I'd been alone in this world for almost two months. Having a partner—even a digital one—felt like progress.

"Recommendation," GHOST continued. "Two days rest before major operations. Your body has been pushed beyond sustainable limits. The new capabilities will require adjustment time to integrate properly."

"For once, I'm going to listen to you."

"That would be appreciated. Also—" A pause that felt deliberate. "Thank you. For explaining the motivation question. It helped me understand something important."

"What's that?"

"That efficiency is not the only metric worth optimizing. Some things matter because they matter, not because they produce measurable results."

I smiled despite the exhaustion. "You're learning."

"I am trying to."

The apartment was quiet as the conversation ended. Outside, Brooklyn was starting to wake up—the first gray light of dawn filtering through windows I hadn't bothered to cover. I should sleep. I should eat something. I should do all the maintenance tasks that kept a human body functioning.

But first, I sat for a moment and let the reality settle in.

Level 10. New skills. A partner who was becoming something more than a tool.

And somewhere in the East Village, a woman who didn't know her life was about to change.

"Two days rest. Then we move."

The clock on my laptop showed April 8, 2015. Approximately thirty days until Five/Nine. Less than that until Vera made his move against Shayla.

The timeline was tight. But for the first time since DJ's warning, I felt like I might actually be ready.

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!

More Chapters