"Then we agree on the next step. We finish the investigation, provide the client with verified results, and accept the consequences of the delay."
After the meeting, Victoria returned to her office and asked the compliance department for an update on the procurement audit.
The answer came twenty minutes later.
The original approval file was missing from the standard archive.
A copy existed in the procurement system, but its metadata indicated that it had been uploaded after the replacement sensor had already been installed.
The electronic signature belonged to a former vice president of engineering.
The document itself listed the sensor as approved for the prototype's operating range, but the supporting test report referenced a different component model.
Victoria read the summary slowly.
"Who discovered the discrepancy?" she asked.
"An internal auditor reviewing the transaction," the compliance director replied. "The audit trail also shows that several related records were moved to a restricted archive shortly before the former vice president resigned."
"Was the archive access authorized?"
"We're checking."
"Check faster."
The compliance director nodded.
Victoria leaned back.
"Could this be deliberate?"
"It's possible, but we don't have enough evidence to say that. The records may have been moved during a legitimate restructuring. We need to establish who initiated the transfer and why."
"Then establish it."
The compliance director left.
Victoria stared at the document.
The sensor issue had seemed like a technical mistake. Now it was becoming a governance problem.
That afternoon, Jamal was summoned to the laboratory.
Ethan Cole had discovered another detail in the historical test records. A subtle oscillation had appeared in an early test conducted two days after the replacement sensor was installed.
At the time, the deviation had been attributed to normal measurement variation.
The data had not triggered an alert because the system's thresholds had been configured to tolerate a wider range of sensor variation during initial testing.
The pattern had grown gradually over subsequent tests.
Jamal studied the graphs.
"Was the same sensor installed in all these runs?"
"Yes," Cole replied.
"And were the test conditions identical?"
"Not exactly. The load profile changed slightly between runs."
"Then we should compare the data by operating condition, not simply by elapsed time."
Priya nodded.
"That may explain why the earlier deviations weren't obvious."
They spent two hours reviewing the historical data.
The results strengthened the hypothesis that the replacement sensor had introduced a mismatch into the control loop. But the review also revealed that several test runs had been repeated without a formal note explaining why the operating parameters had changed.
The records were incomplete.
Not necessarily falsified.
Incomplete.
That distinction mattered.
At 5:40 p.m., Jamal left the laboratory to return to his regular assignment.
He was crossing the service corridor when a man stepped out from an office doorway.
The man wore an expensive navy suit and carried a leather briefcase. Jamal recognized him from the procurement department: Daniel Price, senior director of strategic sourcing.
Price had been present at one of the earlier board meetings.
"Washington, isn't it?"
"Yes, sir."
"I hear you've become quite important."
"I'm assisting with the engine investigation."
Price smiled without warmth.
"An interesting development for a man who cleans floors."
Jamal said nothing.
Price glanced down the corridor to make sure no one was nearby.
"Let me offer you a piece of advice. Technical investigations can become political very quickly. People who don't understand the full picture sometimes draw conclusions that hurt others."
"That's why we need the complete record."
"Exactly. So you should be careful about what you put in writing."
Jamal met his eyes.
"Are you asking me to leave something out?"
Price's smile disappeared.
"I'm telling you not to make accusations you can't prove."
"I haven't made any accusations."
"Good."
Price stepped closer.
"Keep it that way."
Jamal held his gaze for a moment, then moved past him.
He did not report the encounter immediately. There was no direct threat, no explicit demand, and no evidence that Price had violated company policy.
But he remembered the words.
Be careful about what you put in writing.
That evening, Jamal documented the conversation in a private incident note and sent it to the compliance director, describing exactly what had been said without speculating about Price's intentions.
He attached no dramatic interpretation.
He made no accusation.
He simply preserved the facts.
The next morning, Price discovered that the compliance department had requested his records.
For the first time, the procurement director realized that the janitor he had tried to intimidate understood something important about evidence.
It did not need to be loud.
It needed to be preserved.
The Price of Telling the Truth
The following three days were among the most difficult in Tech Vanguard's recent history.
The engine continued through its validation program, but the company had suspended all claims that the prototype was ready for commercial deployment. Engineers ran extended operating cycles, tested alternative loads, and examined the control system for any additional instability.
The calibrated reference sensor performed as expected.
The original failure pattern did not return.
That was encouraging, but the team refused to declare victory prematurely.
A reliable machine had to perform consistently under more than one carefully selected test condition. It had to survive changes in temperature, load, vibration, and operating duration. It had to fail safely when conditions exceeded its limits.
The team therefore expanded the validation schedule.
Meanwhile, the procurement investigation widened.
Auditors discovered that the replacement sensor had been purchased through an expedited contract with Meridian Instruments, a supplier that had recently received several unusually large orders from Tech Vanguard.
The orders had been approved by Daniel Price's division.
Price maintained that the purchases were legitimate and that all required approvals had been obtained. He argued that the sensor was listed as an approved equivalent in the supplier's catalog and that the engineering team had accepted it.
The records, however, did not fully support his explanation.
The catalog listing covered the sensor's electrical characteristics and standard operating range. It did not establish that the component had been validated for the prototype's specific dynamic response requirements.
The distinction was technical, but its consequences were substantial.
A component could meet every general specification and still be unsuitable for a particular system.