“$500M If You Can Open This Safe” the Billionaire Mocked — Then Black Cleaning Lady’s Son Stunned Him

Chapter 13

Theme:
Font Size:
24px

For several seconds, Evelyn could not speak.

Then she asked, “What happens to Darius's drawings?”

Natalie opened a folder.

“The company has preserved a copy of the page he showed Dr. Shaw. We want to make sure any use of his observations is properly documented.”

“Will you pay him?”

Natalie nodded.

“We're discussing an appropriate recognition award, subject to legal review and the company's policies regarding minors. We also want to offer him an opportunity to participate in an educational program.”

Evelyn stared at her.

“What kind of program?”

“Engineering mentorship. Supervised laboratory visits, educational materials, and meetings with engineers who can help him develop his interest safely.”

Evelyn was cautious.

“Is this because the vault opened?”

“Partly. But it's also because several people recognized that Darius demonstrated unusual observational skills. We want to support that ability without placing pressure on him to solve company problems.”

Evelyn let out a slow breath.

For the first time since the boardroom incident, she felt that something good might come from it.

But Natalie had not finished.

“There is another matter. The vault recovery has raised questions about the configuration change made before the storm. The audit committee is investigating whether the approval process was followed.”

Evelyn frowned.

“What does that have to do with Darius?”

“His observation helped direct the diagnostic team toward the sensor discrepancy. That means his account is part of the incident record.”

“Are you saying someone caused the vault to fail?”

“Not necessarily. We don't know that. We are still reviewing the evidence.”

Evelyn appreciated the honesty.

She did not want her son drawn into an accusation he could not understand.

“Please don't make him responsible for investigating adults,” she said.

“We won't.”

“He's a child. He likes machines. He isn't trying to expose anyone.”

Natalie nodded.

“I understand. The investigation will be conducted by qualified professionals. Darius's role is limited to what he observed and the drawing he created.”

Evelyn left the office feeling cautiously hopeful.

She had no idea that the investigation was about to reveal a second problem.

The vault's mechanical failure had been caused by an incorrect reference value in the emergency locking system. But the configuration history contained several irregularities.

The change had been approved without final calibration.

The implementation log showed that a warning had been acknowledged but not resolved.

And the recovery reports had repeatedly focused on possible motor damage, even after tests showed that the motor was functioning normally.

None of those facts proved that anyone had intentionally sabotaged the vault.

Together, however, they suggested that the company had failed to investigate its own systems properly.

The audit committee requested the original software contractor's records.

The contractor responded with a set of technical documents and an email chain.

One message, written six weeks before the storm, was particularly important.

The contractor had warned that the secondary position sensor needed to be recalibrated after the emergency protocol was changed.

The message had been sent to Victor Sloane and copied to two members of the security engineering team.

Victor had replied:

Proceed with the approved deployment. The final validation can be completed during the scheduled maintenance window.

The maintenance window had been postponed twice.

The validation had never occurred.

The committee now had evidence of a procedural failure.

It did not yet have evidence of deliberate sabotage.

But the investigation continued.

Then an accountant reviewing the vault recovery expenses noticed something strange.

Several invoices had been submitted by a specialist consulting company that had performed no identifiable work on the mechanical recovery.

The invoices described “emergency protocol optimization,” “secure-state architecture review,” and “advanced system validation.”

The amounts were substantial.

The consulting company had been paid through a technology services subsidiary controlled by TechNova.

The accountant requested supporting documentation.

The documents were incomplete.

Some invoices referred to work orders that did not exist in the central system. Others listed personnel who had never been assigned to the project.

The audit committee widened its review.

It began examining the financial records associated with the vault's security upgrade.

What it found was not a simple bookkeeping error.

Over the previous eighteen months, TechNova had paid several million dollars to a network of vendors whose services overlapped with work already performed by internal teams.

Some payments were legitimate.

Others lacked clear documentation.

A small number appeared to have been approved through an exception process that Victor Sloane had personally authorized.

The committee did not immediately conclude that the money had been stolen.

It ordered an independent forensic audit.

Victor was informed that his approvals were under review.

For the first time, he began to understand that the vault's failure might expose more than a technical mistake.

The security modification had created an opportunity for the company to spend money on emergency work, additional testing, and specialized consulting.

If the investigation established that the vendors had been paid for services they never provided, the consequences could be serious.

And if the same people who had approved the incomplete configuration had also authorized the questionable invoices, the committee would have to determine whether the overlap was coincidental.

Victor called Whitmore.

“We need to discuss the audit.”

Whitmore sounded irritated.

“What audit?”

“The committee is reviewing the configuration change and the associated vendor payments.”

“Why are they reviewing payments?”

“Because several invoices lack supporting documentation.”

“Then find the documentation.”

“We're trying.”

Whitmore paused.

“Victor, I don't want this turning into a scandal.”

“Neither do I.”

“Then make sure the investigation stays focused on the technical issue.”

Victor looked at the email chain on his screen.

“I don't think we can separate the two.”

Whitmore's voice cooled.

“Why not?”

“Because the same approval process appears in both.”

Silence followed.

Whitmore understood the implication.

“Are you telling me someone deliberately caused the vault to fail?”

“No. I'm telling you we don't yet know why the configuration was deployed without final validation, and we don't know whether all the associated payments were legitimate.”

“Then don't speculate.”

“I'm not speculating.”

Whitmore ended the call.

He sat alone for several minutes.

The vault had been a technical problem.

Now it was a governance problem.

And the boy who had helped identify the first fault had unknowingly set in motion a chain of questions that could reach the highest levels of the company.

Whitmore had spent his career building a reputation for knowing what happened inside TechNova.

He had trusted Victor to manage the company's operations.

He had trusted the engineering team to protect its systems.

He had trusted the security procedures to prevent unauthorized changes.

Now he was discovering that trust, without verification, could become another kind of locked door.

News in the same category

“$500M If You Can Open This Safe” the Billionaire Mocked — Then Black Cleaning Lady’s Son Stunned Him

20 Part