But the record showed what information had been available and what she did after receiving it.
That was enough to raise serious questions about her judgment and use of corporate privileges.
Then the team found an attempted post-incident change.
Approximately twenty minutes after speaking with her father, the woman had logged into the platform.
She attempted to modify the original incident description.
The system recorded the request.
But the access restrictions were already being implemented, and the underlying record remained preserved.
The modification did not overwrite the original entry.
The audit committee documented the attempt.
The woman later claimed she was trying to correct an error.
Investigators would evaluate that explanation in context.
But the timing was troubling.
She had been warned not to alter records.
And she tried anyway.
The technical review was led by a Black American woman in her late thirties who had spent more than a decade developing secure access-control systems.
She was the kind of engineer who spoke quietly during meetings and then asked the one question everyone else had avoided.
She had worked at Asterion for almost seven years.
During that time, she raised concerns about the difference between verified security events and subjective resident complaints.
Her team wanted the interface to display those categories clearly.
A verified access-control failure should look different from a resident saying someone seemed unfamiliar.
A confirmed theft report should not share the same urgent visual warning as an unverified suspicion.
And privileged accounts should not allow marketing directors to change operational incident severity without independent review.
She had written memoranda.
Prepared prototypes.
And requested design changes.
Some were adopted.
Others were delayed.
The luxury division argued that customers preferred simple interfaces.
The director had insisted that "premium residents" needed the ability to receive immediate attention.
The engineer disagreed.
She believed premium service should mean accurate information and responsible escalation, not unquestioned acceptance of a wealthy customer's fears.
But her recommendations became trapped between engineering, marketing, and senior management.
Now the new investor's audit committee asked her to explain the problems.
She arrived carrying a thick folder.
For nearly two hours, she walked the independent reviewers through the software.
The technical safeguards.
The missing safeguards.
The different levels of administrative access.
And the points where human judgment could transform a subjective report into an apparently serious warning.
One reviewer asked whether the software contained an automatic racial-profiling feature.
The engineer answered firmly.
"No."
Then she added something more important.
"But a system doesn't need to identify race directly for people to use it in discriminatory ways."
The room became quiet.
She continued.
"If residents repeatedly report certain people based on appearance, and operators treat those reports as credible without verification, the system can amplify the residents' bias."
She pointed toward the interface.