Chapter 2
I had never seen Nia Whitmore look frightened.
Not when she publicly humiliated employees.
Not when she threatened department heads.
Not even when a major client complained that her decisions had delayed an important project.
But now, standing beside my desk, she was staring at the sealed envelope as though it might destroy everything she believed about herself.
Arthur pulled out several documents.
The first was a copy of an agreement I remembered signing during my first week at Whitmore Technologies.
The second was a letter written by his father, Samuel Whitmore, the company's late founder.
Arthur placed both documents on the desk.
“Nia, sit down.”
She didn't move.
“Dad, what is this?”
“Sit.”
For the first time since I had known her, Nia obeyed without arguing.
Arthur turned toward me.
“Malik, do you remember the conversation we had before you accepted your position?”
I nodded slowly.
“Yes, sir.”
Six years earlier, I had been twenty-six years old, unemployed, and drowning in medical debt from my mother's treatment.
I had recently completed a specialized cybersecurity certification.
I didn't have influential friends.
I didn't have family connections.
All I had was an old laptop, a collection of technical projects, and a determination to build a better future.
Then Arthur Whitmore called me.
He had seen a security framework I developed during a university research competition.
He offered me an interview.
I expected a normal engineering position.
Instead, he introduced me to Samuel Whitmore.
Samuel was eighty-four at the time.
He had founded Whitmore Technologies in a rented office with three employees and two computers.
He asked me one question.
“What would you build if nobody told you it was impossible?”
I explained my idea for a self-recovering security system that could isolate suspicious activity before attackers reached customer records.
Samuel listened for nearly an hour.
Then he smiled.
“You remind me of myself.”
Arthur offered me a job.
But Samuel insisted on an additional agreement.
If my security architecture became part of the company's core infrastructure, I would receive a small ownership interest through a long-term technical contribution plan.
I had accepted the agreement without believing it would ever become especially valuable.
I was grateful simply to have a job.
Samuel died eleven months later.
Arthur continued honoring the agreement, but I rarely thought about it.
My focus remained on building systems.
Now Arthur was holding those same documents in front of his daughter.
“Nia,” he said, “Malik isn't simply a salaried engineer.”
She looked from him to me.
“What does that mean?”
“His technical contribution agreement includes a vested three-percent equity interest in Whitmore Technologies.”
Nia stared at him.
“Three percent?”
Arthur nodded.
“And the core recovery platform that protects our client accounts uses intellectual property Malik developed before joining us. The company operates that technology under a licensing agreement.”
Nia's mouth opened.
Then closed.
I felt uncomfortable watching her struggle to understand.
I hadn't joined Whitmore Technologies for the ownership interest.
I had joined because I wanted to build something useful.
Arthur continued.
“Malik also serves as the designated technical continuity adviser under the board's emergency governance plan. That appointment cannot be terminated by a department executive acting alone.”
Nia looked at the torn folder.
“You're saying I couldn't fire him?”
“I'm saying you ignored company policy, failed to review the emergency incident, and attempted to dismiss someone whose position requires board-level approval.”
Her face flushed.
“But nobody told me about this.”
Arthur's expression hardened.
“You had access to the governance records. You never read them.”
She turned toward me.
“Why didn't you tell me?”
I stared at her.
“When?”
She looked confused.
“What?”
“When was I supposed to tell you? Before or after you slammed a termination folder beside my head?”
Daniel lowered his eyes to hide a reaction.
Nia opened her mouth, but Arthur raised his hand.
“Enough.”
He looked around the office.
“Everyone, return to your work. Rebecca, please arrange a private meeting.”
Then he turned toward me.
“Malik, you're exhausted. You need rest.”
I nodded.
“Thank you, sir.”
“But before you leave, I need to ask one question.”
Something about his voice made me uneasy.
“Did you find anything unusual during last night's recovery?”
I hesitated.
“Yes.”
Arthur's face changed.
“What did you find?”
I glanced toward Nia.
She was watching me closely.
I remembered the unauthorized configuration changes.
The unusual access credentials.
The internal administrative account used to bypass our security controls.
I had included everything in my incident report.
But I hadn't yet confirmed who controlled the account.
“There was evidence of deliberate interference,” I said.
Arthur became very still.
“Interference from outside?”
I shook my head.
“No, sir.”
The room seemed to grow colder.
“The changes were made using internal executive-level credentials.”
Nia stood abruptly.
“That's impossible.”
Arthur turned toward her.
“Why?”
She blinked.
“Because our executive accounts are protected.”
I looked at her.
“They should be.”
The silence that followed was heavy.
Rebecca approached the desk.
“Mr. Whitmore, the conference room is ready.”
Arthur nodded.
“Malik, would you be willing to explain what you discovered before going home?”
I wanted to say no.
My head hurt.
My muscles felt weak.
I had been awake so long that every sound seemed unusually sharp.
But the company was still vulnerable.
And I couldn't ignore that.
“Give me ten minutes,” I said.
Arthur looked at Rebecca.
“Please get him something to eat first.”
It was such a small gesture that it nearly broke me.
Nobody had asked whether I had eaten.
Nobody had asked why I was exhausted.
Not until Arthur walked through the door.
Inside the conference room, I connected my laptop to the secure display.
I showed Arthur and Rebecca the first suspicious change.
At 11:48 p.m., someone had disabled a critical monitoring process.
At 12:06 a.m., an internal account attempted to export a protected customer database.
At 12:19, the backup recovery system began failing.
The timing was too precise to be accidental.
I had spent hours trying to determine whether the activity originated from a compromised account or an authorized user.
Arthur studied the screen.
“Who owns the account?”
I swallowed.
“The account is registered to the executive operations department.”
Rebecca typed something into her tablet.
Then she looked up.
“That's Nia's division.”
Nia folded her arms.
“That doesn't mean I did anything.”
“I didn't say you did,” I replied.
But she was already angry.
“You're trying to blame me because I fired you.”
I stared at her.
“You fired me because you found me asleep. I found these logs before you entered the office.”
Arthur leaned back.
“Nia, stop talking.”
She looked wounded.
“Dad—”
“Not another word.”
He turned toward me.
“Can the account activity be traced?”
“Yes. I preserved the audit logs and protected the relevant snapshots.”
“Where are they?”
“In the secured incident archive.”
Arthur nodded.
“Good.”
Then I opened the final page of my report.
“There was one more thing.”
The unauthorized account had accessed a confidential directory shortly before the server failure.
The directory contained acquisition plans, board correspondence, and internal financial projections.
Arthur's expression changed immediately.
“Which acquisition plans?”
I checked the file path.
“Project Meridian.”
Rebecca gasped.
Nia looked sharply toward her.
“What?”
Arthur didn't answer.
He stood and walked to the door.
“Rebecca, call our general counsel and the head of internal audit. Tell them we have a critical security incident.”
Then he turned back toward me.
“Malik, do not discuss these findings with anyone until the investigation is underway.”
I nodded.
Arthur looked more troubled than I had ever seen him.
“Project Meridian isn't just another business deal.”
He glanced at Nia.
“It involves an agreement that could determine who controls this company after I retire.”
May you like
Nia went pale.
And for the second time that morning, I realized the server failure was connected to something much bigger than my job.
