Arrogant Manager Kicked a Poor Old Man Out of a $3 Million Supercar Showroom—Then Froze When the Staff Revealed Who He Really Was!

Chapter 31

Theme:
Font Size:
24px

When news of the Nocturne investigation appeared, the unusual shipments came back to her. She contacted the insurer's legal department and asked whether the records should be preserved. This time the answer was yes. The company authorized her to provide relevant documents to the independent committee. Marisol spent a weekend organizing manifests, declarations and correspondence. She resisted the temptation to make the records tell a complete story. Some shipments were entirely legitimate. Others had missing details that could arise from ordinary clerical errors. Her task was to identify what she could establish and leave investigators to determine what it meant.

At the hearing, an attorney asked why she had not raised the matter with regulators sooner. Marisol answered that she had followed the insurer's internal process and had not possessed evidence of an actual safety problem. Asked whether she regretted stopping there, she said yes. The admission seemed to surprise the attorney, who had prepared a series of questions designed to expose defensiveness. Marisol explained that she had learned to distinguish between a lack of proof and a lack of concern. She could not accuse a client without evidence, but she could have sought another review when the first inquiry ended without explanation.

Her documents helped investigators reconstruct the path of several components after leaving protected inventory. A shipment declared as demonstration equipment had contained factory-certified assemblies with a higher resale value than the manifest suggested. Another shipment had been routed through a warehouse used by Adrian Pike's brokerage network. A third had returned to Asterion under a replacement-parts code. The movements were not proof that the same people controlled every stage, but they explained how components could leave the company's records and later reappear as apparently ordinary stock.

Martin Cho compared the shipping dates with changes in the inventory database. He found that several adjustments occurred within hours of the freight declarations. A single discrepancy might have been accidental; the repeated timing suggested coordination. Ruth asked him to prepare a chart showing which connections were supported by timestamps and which remained assumptions. He used solid lines for verified links and dotted lines for possible links. The visual distinction prevented viewers from treating the entire network as equally proven. Elias studied the chart and said it was a better explanation of the case than any dramatic speech he could have made.

Marisol's testimony changed the insurer's internal procedures too. The company reviewed how unusual client declarations were escalated and introduced a requirement that certain closures be documented with reasons. Senior underwriters complained that the process would slow approvals. Marisol suggested a risk-based approach rather than universal additional paperwork. High-value goods, repeated changes and unexplained ownership transfers would trigger review; ordinary shipments with consistent records could move as before. The insurer adopted a pilot program. It found errors unrelated to Asterion and corrected them before they became disputes. The improvement did not erase earlier failures, but it gave meaning to what the inquiry had exposed.

Outside the hearing room, Marisol spoke briefly with Jonah Reed. They recognized a similarity between their experiences. Each had noticed a problem within the limits of a narrow role. Each had reported it through an official channel and watched the response disappear. Neither had possessed enough information to understand the larger pattern. Jonah said he had blamed himself for not seeing the danger sooner. Marisol replied that professionals needed to take responsibility for their own judgments, but companies should not build systems that depended on every worker independently discovering a hidden conspiracy. A warning ought to reach someone capable of examining it.

The next witness, a software engineer named Priya Sethi, described the temporary credential system used during the restructuring. The original design had included automatic expiration and separate approval for access to inventory, finance and maintenance records. A later modification allowed administrators to extend access across several systems with one exception request. Priya had objected because the change reduced the separation between functions. Her concern was recorded in a development ticket and marked deferred. She had been told the modification was temporary and necessary to keep production schedules stable. The code remained in place for eighteen months.

Priya explained that software did not become unsafe merely because it contained an administrative exception. The risk depended on who could use the exception, what records it affected and whether someone independently reviewed the changes. In Asterion's case, the exception could restore an old contractor credential and grant enough access to modify both maintenance and inventory entries. Audit logs recorded the changes, but the alert system sent notifications to a mailbox no one actively monitored after the department reorganization. The information existed; the organization had lost the habit of looking at it.

News in the same category

Arrogant Manager Kicked a Poor Old Man Out of a $3 Million Supercar Showroom—Then Froze When the Staff Revealed Who He Really Was!

45 Part