Chapter 7: Strategic Amnesia
Chapter 7: Strategic Amnesia
The storm of Rajesh’s fury had passed, leaving behind a tense, unnatural calm. The screaming matches had ceased, but the pressure in the office had only intensified, compressing into a dense, silent dread. The critical systems remained dark. The daily revenue reports were a string of mocking zeroes. OmniCorp was hemorrhaging money, and the source of the bleeding was a single, infuriatingly placid man sitting at desk 50-C12.
Management’s strategy, born of desperation and the frantic advice of their legal team, had shifted. Brute force had failed spectacularly, only serving to expose Rajesh’s volatility. Now, they would turn to procedure. They would try to dismantle Alex’s defense brick by logical brick.
The new offensive began not with a roar, but with a polite, calendar-invited meeting. Ms. Albright, her expression as neutral and unyielding as ever, sat across from Alex in The Prism. Rajesh was conspicuously absent.
"Alex," she began, her tone meticulously professional. "While we address the contractual discrepancies you've raised, the company has an urgent operational need. The knowledge you possess is a critical asset. Therefore, we will be assigning a junior analyst to shadow you for the remainder of your notice period to facilitate a complete and thorough knowledge transfer. This is a standard procedure and a mandatory part of your duties."
It was a clever move. They were no longer ordering him to work, which he could refuse. They were ordering him to teach, a subtle but crucial distinction that was almost certainly covered in his job description under a vague clause like 'assisting with team development.'
"Of course," Alex replied, his voice a perfect facsimile of cooperative spirit. "I'm happy to help in any way I can."
A few hours later, a young man named Leo appeared at his cubicle. He looked barely old enough to be out of college, with wide, earnest eyes and a palpable aura of terror. He clutched a fresh legal pad and a pen like a soldier holding a rifle on his first day of basic training.
"Uh, hi, Alex? I'm Leo. Ms. Albright said… she said I should, um, learn from you?"
"Leo," Alex said, offering a small, disarming smile. "Good to meet you. Pull up a chair. Where would you like to begin?"
The skill [Unflinching Poise]
was a passive miracle, allowing him to project an aura of serene helpfulness while his mind was methodically laying a minefield.
"The Kronos Reconciliation Engine," Leo said immediately, his voice a squeak. "They said that's priority one. We need to get the billing cycle running again. Can you just… walk me through the manual override sequence?"
"Ah, Kronos," Alex said, leaning back in his chair with a thoughtful expression. He swiveled to face one of his dark monitors. "The old beast. Of course."
He began to speak, his voice filled with the confident cadence of an expert. "So, the core of Kronos is built on a heavily modified COBOL framework from the late nineties. It was designed to run on hardware that was decommissioned a decade ago, so the first thing you have to understand is that it's all running in a virtualized environment that emulates the original architecture. The problem is, the emulation has a memory leak…"
He spoke for ten minutes, delivering a fascinating and entirely accurate lecture on the system's history and its foundational flaws. He detailed the shortcomings of the database connectors, the deprecated security protocols, and the unorthodox data-caching method he'd personally jury-rigged years ago to keep it from collapsing. Leo scribbled frantically, his notepad filling with intricate diagrams and acronyms.
Finally, Leo looked up, his eyes glazed over but hopeful. "Wow. Okay. So, given all that… what's the command for the override?"
Alex blinked, as if snapping out of a trance. He stared at the dark screen for a long moment, a faint frown creasing his brow. "The command… right. It's… you know, it's funny. I haven't actually thought about the specific command in years."
Leo’s pen froze. "What do you mean?"
"Well, it's muscle memory at this point," Alex said, tapping his temple. "For a decade, I'd come in, see the red flag, and my fingers would just… do the thing. It wasn't in my job description, you understand. I was never a 'Kronos Administrator.' I was just the guy who knew how to keep the ghost in the machine from having a seizure."
He turned back to Leo, his expression a perfect blend of apology and concern. "All those years of overwork, the constant stress… it does a number on your declarative memory. I can tell you how the system works, but the specific, rote commands? They're… fuzzy. It's like trying to explain how to tie your shoes. You don't think about the steps, you just do it."
Leo stared at him, his mouth slightly agape. He was being presented with a problem that had no solution. The man who knew everything was claiming he couldn't remember the one thing that mattered.
"But… could you try?" Leo pleaded, his desperation palpable. "Maybe if you just opened the terminal…"
"I can't do that, Leo," Alex said gently, his voice laced with regret. "My employment has been terminated. I'm not authorized to access active systems. That would be a serious compliance violation for both of us. My hands are tied."
It was a perfect, unassailable fortress of logic. He wasn't refusing. He was unable. He wasn't being insubordinate; he was being honest about the psychological toll the job had taken on him—a narrative HR itself championed during annual 'mental wellness' seminars. He was a brick wall, built and mortared with their own corporate doublespeak.
[+250 KP - Strategic Amnesia Executed Flawlessly]
The beautiful blue box shimmered, a private reward for his masterful performance.
They spent the rest of the day in the same torturous loop. Leo would ask about another system—the logistics router, the automated financial report script, the sales data aggregator. Each time, Alex would provide a dazzlingly brilliant, deeply technical, and utterly useless explanation of the system's architecture, only to cap it off with a regretful sigh and a claim that the actual 'how-to' was lost in a fog of stress-induced memory loss and muscle-memory automation.
By late afternoon, Leo's notepad was filled with incomprehensible notes. His face was pale, his shoulders slumped in defeat. He had been sent to extract the blueprints for the atomic bomb from the mind of its creator, only to be given a lecture on theoretical physics.
"I… I think that's enough for today," Leo finally mumbled, gathering his things. He looked at Alex, a flicker of something—awe, fear, perhaps even admiration—in his young eyes. He knew he'd been completely and utterly outplayed.
"Anytime, Leo," Alex said warmly. "Happy to help."
Leo fled. Alex watched him go, then swiveled his chair back to his dark monitors. He had turned his own exploitation into his greatest defense. They had overworked him to the point where his knowledge was instinctual, and now he claimed that very instinct was gone. They had created a master of the machine, and in their arrogance, they had forgotten they had never bothered to ask him to write down the user's manual. He was a brick wall they could not breach, and he had built it with the very stones they had thrown at him for years.
Characters

Alex Sterling

OmniCorp
