He wanted the work to be done properly.
For the first time, Victoria wondered how many capable people she had overlooked because she had mistaken deference for competence.
The meeting continued for another hour.
By the time it ended, the company had authorized a full validation program, an independent review of the procurement record, and a broader audit of critical component substitutions.
Jamal returned to the laboratory.
His maintenance cart was still parked outside the service elevator.
He pushed it toward the corridor, intending to complete the work assigned to him that day.
Priya caught up with him.
"You're going back to your regular shift?"
"That's what my schedule says."
She looked at him as if he had made an absurd statement.
"You helped identify a problem that stopped a multimillion-dollar development program."
"I helped identify a possible cause. The team verified it."
"You're impossible."
"People keep telling me that."
Priya laughed.
Then her expression became serious.
"You know this is going to change things."
Jamal glanced at the corridor ahead.
"I hope it changes the process."
"I meant for you."
He considered the question.
"I don't know what happens to me. I know what happens if we pretend the approval process is fine."
Priya watched him push the cart away.
It was the first time she had seen someone walk away from a victory without trying to own the room.
She found herself respecting him more for it.
The Contract, the Threat, and the Missing Records
By noon, the story had spread throughout Tech Vanguard.
The janitor had identified the sensor problem.
The prototype had passed its first controlled tests.
The CEO had apologized.
And the board had ordered an investigation into the procurement process.
Employees shared versions of the story in break rooms, private messages, and conversations held just outside executive offices. Some embellished the details. Others insisted that Jamal had repaired the engine himself. One rumor claimed Victoria had already offered him a senior engineering position.
None of those versions was entirely accurate.
Jamal continued his normal duties while the company determined what would happen next.
He cleaned the executive corridor. He replaced a faulty light fixture in the west stairwell. He helped a facilities technician repair a malfunctioning ventilation damper.
But people looked at him differently.
Some greeted him with sudden enthusiasm. Others watched him with suspicion. A few employees who had barely acknowledged him the previous day now stopped to ask how he had discovered the problem.
Jamal answered politely, without exaggerating his role.
The attention made him uncomfortable.
He had spent years learning how to remain unnoticed in a building where nearly every conversation seemed to involve status, influence, or money.
Now he was becoming a subject of conversation.
At 1:30 p.m., his phone vibrated.
It was a message from the hospital.
His mother's next treatment appointment had been moved forward because a cancellation had opened a slot. The appointment would require a payment he had not yet arranged.
Jamal read the message twice.
He had saved what he could. He had taken additional shifts when available. He had sold his old car and used public transportation. Still, every unexpected expense seemed to push the goal farther away.
He typed a response confirming the appointment.
Then he placed the phone in his pocket and returned to work.
He did not tell anyone at Tech Vanguard.
Not because he was ashamed of his circumstances, but because he did not want his mother's illness to become another story for people to trade in the corridors.
At 2:15 p.m., Victoria received a call from the company's largest prospective customer.
The client was the North American Mobility Consortium, a group of manufacturers that had been considering a multiyear agreement to integrate Tech Vanguard's engine technology into a new generation of industrial transport systems.
The contract was worth approximately fifty million dollars in its first phase, with the possibility of substantial expansion.
Its representatives had been promised a demonstration within days.
The repeated failures had already made them nervous.
Now they wanted answers.
Victoria entered the conference room with Arthur Whitmore, Ethan Cole, Priya Raman, and the head of commercial operations.
The client's lead negotiator, Martin Hale, appeared on the screen.
"We have received several reports that the prototype has experienced a critical stability issue," Hale said.
"That is correct," Victoria replied. "We have identified a sensor response discrepancy that contributed to the repeated shutdowns. The component has been replaced with a calibrated reference unit, and the prototype has completed two controlled verification runs."
"Two?"
"We are conducting a full validation program."
"Your original demonstration was supposed to prove the system was commercially ready."
"It was intended to demonstrate the technology under defined operating conditions. We will not represent it as commercially ready until validation is complete."
Hale's expression remained skeptical.
"How can we be confident that this was the only problem?"
"You cannot be confident yet," Victoria said. "Neither can we. That's why we're conducting additional tests."
Arthur glanced at her.
It was a difficult answer, but an honest one.
Hale leaned toward the camera.
"Your team has been telling us for weeks that the issue was almost resolved."
"I understand the frustration. The previous updates were based on the information available at the time. We have changed the investigation process to include a broader review of the sensor response, controller behavior, and component approval records."
"Are you suggesting that the wrong part was installed?"
"We are investigating whether the replacement component met the prototype's dynamic requirements. We have not yet reached a conclusion about how the discrepancy entered the system."
Hale paused.
"Our technical committee wants access to the validation results before we consider moving forward."
"That is reasonable."
"And we want an independent review of the component substitution."
Victoria nodded.
"We will discuss the scope with your technical team."
The call ended without a commitment.
The room remained quiet.
The head of commercial operations rubbed his temples.
"We may lose the contract."
"We may," Victoria said.
"Fifty million dollars."
"I know what the contract is worth."
"We have investors expecting a launch."
"And I will not ask the engineering team to certify a system that hasn't completed validation."
The executive looked as if he wanted to argue, but Arthur Whitmore spoke first.