A few declined to participate.
Hannah did not pressure them.
Trust could not be ordered into existence.
Meanwhile, the technical specialist began examining the software issue Aaron Mitchell had described.
The product in question was called Atlas Industrial Insight, one of Pinnacle's flagship platforms. It analyzed equipment data from manufacturing plants and used predictive models to identify potential failures before they interrupted production.
The system was sophisticated, valuable, and widely used.
The issue Aaron had raised concerned a specific class of sensor failure. Under certain conditions, the platform could continue displaying a prediction even after the underlying data had become unreliable. The interface did not always make the uncertainty sufficiently clear.
The technical team did not immediately conclude that the software was unsafe. It reproduced the behavior, documented the circumstances, and assessed the potential consequences.
The preliminary finding was troubling.
The defect did not affect every customer or every operating environment. In some applications, the consequences might be limited to unnecessary maintenance or downtime. In others, the system's output could influence decisions with greater operational significance.
The problem required a documented risk assessment before the company could confidently describe the release as complete.
The release-readiness report, however, contained no clear reference to the unresolved issue.
It stated that all critical defects had been resolved or accepted by customers.
The investigators could not find evidence that the relevant customer had accepted the defect.
Aaron had been right to ask questions.
That did not automatically prove that his manager had acted maliciously. It did mean that his concern deserved serious attention, and that his removal from the customer demonstration and delayed performance review needed to be examined in context.
When Victoria received the preliminary report, she read it twice.
Then she called the head of engineering, Samuel Ortiz.
Samuel arrived at her office carrying a laptop and a stack of technical notes. He was in his late forties, with dark hair and a careful, thoughtful manner.
“Ms. Matthews,” he said, taking a seat. “I understand you want to discuss Atlas.”
“I do. Tell me what you know.”
Samuel opened his laptop.
“The team identified a data-integrity issue during testing. The system's confidence indicator did not always reflect the reliability of the incoming sensor data. Engineering classified it as a defect requiring further assessment.”
“Was it resolved before release?”
“Not completely.”
“Was the release-readiness report accurate?”
Samuel hesitated.
“Not in the way it was written.”
“Why?”
“The reporting template combines several categories. A defect can be marked as accepted if the customer has formally accepted the risk. In this case, we could not locate that acceptance.”
“Who approved the report?”
“The product director.”
“Did you review it?”
“I reviewed the overall release status. I did not personally verify every line of the supporting documentation.”
“Did anyone tell you that the customer had accepted the issue?”
“I was told the team had discussed it with the customer.”
“Was that the same as formal acceptance?”
“No.”
Victoria leaned back.
“Why was the distinction not made clear?”
Samuel rubbed his forehead.
“We were under pressure to meet the release date. The customer had planned its deployment around the schedule, and our commercial team was concerned about the cost of delaying it.”
“Did anyone instruct engineering to conceal the defect?”
“I don't know.”
“Did anyone instruct the team to release the product regardless of the risk?”
“I don't know.”
“Then those are questions the review must answer.”
Samuel nodded.
“I agree.”
Victoria looked at the notes on the table.
“Did Aaron Mitchell raise the issue appropriately?”
“Yes. His written report was technically sound. He asked for a formal risk assessment and clarification of the customer acceptance.”
“What happened to him afterward?”
Samuel's expression changed.
“I heard there had been a disagreement between him and his manager.”
“Was his performance review delayed?”
“I believe so.”
“Was he removed from the customer demonstration?”
“Yes.”
“Were those decisions connected to his concerns?”
Samuel looked uncomfortable.
“I can't say.”
“Then we need the records that can.”
He closed his laptop.
“I want you to understand something,” he said. “Pinnacle's engineers are good people. They care about the work. They don't want to put customers at risk.”
“I believe that many of them do.”
“But the schedule pressure is real. If we miss a release, customers can lose confidence. Revenue can be affected. Contracts can be reviewed.”
“All true.”
“Sometimes leadership has to make difficult trade-offs.”
Victoria looked at him.
“Difficult trade-offs require accurate information. If a decision-maker is not told about a defect, they are not making an informed trade-off. They are making a decision based on a false picture.”
Samuel nodded slowly.
“You're right.”
“I'm not asking you to agree with me. I'm asking you to ensure that the technical assessment is independent of commercial pressure.”
“It will be.”
“And Aaron's performance review?”
“I'll provide the records to the investigators. I won't make any changes until they advise us on the proper process.”
“Good.”
After Samuel left, Victoria remained at her desk.
She thought about the phrase Richard had used in the restroom.
People like you.
The words had reduced her to a category before he knew her name.
In the engineering department, a different kind of reduction might have occurred. A technical concern had become an obstacle to the release schedule. The employee raising it had become a difficult person. The unresolved issue had become a line in a report that no one wanted to examine closely.
The details were different.
The underlying mechanism was familiar.
When a company rewarded people for protecting appearances, the truth became expensive.
By the end of the first week, the investigators had identified several employees willing to discuss the reporting system.
One was Natalie Brooks.
She arrived at the interview room carrying the same folder Victoria had seen outside human resources.
Hannah Price greeted her and explained the process.
Natalie listened carefully.
“Will my manager know what I say?”
“Not automatically,” Hannah replied. “We will share information only as necessary to investigate the issues fairly and take appropriate action. Some details may need to be disclosed to people who are asked to respond to specific allegations, but we will not circulate your account unnecessarily.”
“Can I be fired for participating?”
“Retaliation is prohibited. If you believe you experience retaliation, you can report it directly to our team or through the independent channel we have established for the review.”
Natalie looked at Michael Grant.
“Does that channel actually work?”
Michael did not take offense.
“It will be monitored by an external provider and overseen by the audit committee during the investigation. We will test it regularly.”
Natalie opened her folder.