Nia asked one question.
"Then show me the model."
He did not.
The next morning, an anonymous email appeared in Nia's inbox.
The subject line read: YOU NEED TO SEE THE FLAGS.
Attached were screenshots from a dashboard Nia had never seen.
The interface bore Sentinel's logo. Each customer interaction had a case number, time, store location, associate note, and a colored risk label. Green meant routine. Yellow meant monitor. Red meant intervention.
Beside some entries were short codes.
R3. R5. U2. NQ.
One screenshot made Nia sit back.
Case 4418. Hawthorne flagship. Female, approx. 30-40. Browsing premium handbags. No purchase history located. Large personal tote. R5. Monitor.
Another:
Male, approx. 18-25. Hoodie. Multiple visits. No transaction. U2/R3. Photograph if lingering.
Another:
Female, head covering. High-value cosmetics. Group of three. R5/NQ. Maintain sight line.
There was no explicit racial category.
There did not need to be.
The codes appeared to stand in for observable traits.
Priya came to Nia's office after reviewing the attachments.
"If this is authentic, we have a serious problem."
"We have a serious problem even if the codes mean something innocent," Nia said. "Because people were being tracked through a system our customers never knew existed, and our own complaint process kept sending them back to the same contractor that flagged them."
Priya nodded slowly.
"There's another issue."
"What?"
"The operating agreement delegates loss prevention to Sentinel through our management company. If senior management knew the complaints were being auto-closed based on Sentinel's own review, plaintiffs could argue the process was structurally designed to erase evidence."
Nia looked through the glass wall of her office toward the design floor where employees were arranging samples for a collection launch.
Eleven years of work lived in the brand outside that glass.
She had spent years promising that Marrow & Vale was not merely luxury clothing. It was hospitality. It was dignity. It was the feeling that no one had to apologize for wanting something beautiful.
Now she was looking at evidence that, behind the soft lighting and polished floors, some customers had been classified before anyone asked what they needed.
Her phone rang.
It was Martin.
His voice was strained.
"There's something else."
"Tell me."
"A former security supervisor contacted me this morning. He says Sentinel trained staff to use coded appearance markers because they didn't want written records that looked discriminatory."
Nia closed her eyes.
"Does he have proof?"
"He says he kept training slides."
"Get him a lawyer."
Martin paused. "For him?"
"Independent counsel. I don't want anyone saying we coached his testimony. And preserve every camera log, complaint, email, text, and incident file. Nobody deletes anything."
That evening, Nia returned to the flagship after closing.
The store was silent without customers. The polished floors reflected ceiling lights in long pale lines.
She stood where Officer Mercer had spoken to her.
The entire viral story had focused on the moment Martin said she owned the boutique.
But Nia no longer cared about that moment.
She cared about the thirty-one people for whom no manager had rushed from a back office.
She cared about every customer who had been told a humiliating encounter was routine procedure.
And she cared about the possibility that someone had built a system inside her company that depended on nobody powerful ever experiencing it personally.
Martin stood several feet away.
"What are you going to do?" he asked.
Nia looked around the store.
"First," she said, "we find out exactly what we've been hiding from ourselves."
The first records reached Nia that same evening. Martin sent a folder containing forty-two customer complaints marked resolved. Most were brief. A shopper said a guard followed her through three departments and then denied doing so. A college professor said he was asked to show a receipt while two customers beside him were not. A mother complained that a security officer photographed her teenage son after he tried on a jacket but bought nothing. The official responses were polished and nearly identical: staff conduct reviewed, no policy violation identified, customer experience regretted.
Nia read every one. The language bothered her because it seemed designed to close a conversation without describing what had actually been reviewed. She called Martin at 10:47 p.m. and asked what evidence supported the no-violation findings. Martin said he assumed security supervisors checked video. Nia asked where those reviews were documented. He did not know. She asked who approved the response templates. He said Northmere Operations had standardized them across the chain. Nia looked again at the phrase customer experience regretted and realized how efficiently a sentence could acknowledge pain while refusing responsibility.
The next morning, Priya joined Nia and the company's data director, Omar Reyes, in a conference room before sunrise. Omar had spent the night exporting security contact logs before any vendor could claim the information belonged to a different system. He showed them columns Nia had never seen: observation level, purchase likelihood, intervention priority, escalation code. Some entries had plain behavioral notes such as removed tags or concealed item. Others contained phrases like browsing without selection, repeated handling, luxury mismatch, oversized outerwear, and accompanied by youth group.
Priya stopped at luxury mismatch. 'Define that,' she said. Omar could not. The field came from Sentinel Retail Solutions, the outside security analytics company used by Northmere. Nia asked whether the system influenced guards in real time. Omar said he was not certain, but store tablets displayed colored risk markers linked to camera zones. He had assumed the markers were based on known theft patterns. He had never been given the scoring logic.
At 8:16 a.m., an email arrived from a former assistant manager named Jasmine Wade. She had left the Hawthorne store fourteen months earlier. Her subject line read: Since you are finally asking. Jasmine wrote that she had complained repeatedly about selective surveillance and had been told the system was data-driven. She described one night when a Black couple buying an anniversary gift were followed until they left without purchasing anything. Jasmine had asked the security supervisor what triggered the watch. He had tapped a yellow icon on his tablet and said, 'The model doesn't like them.' Jasmine wrote that the sentence had stayed with her long after she quit.
Nia called Jasmine personally. The former manager sounded suspicious at first. She asked whether the call was being recorded and whether Marrow & Vale intended to blame individual employees for vendor instructions. Nia said no. She asked only for documents and memory. Jasmine agreed to meet Priya under a formal witness protocol. Before hanging up, she told Nia there were other former employees who would talk if they believed the company was seeking facts rather than preparing a defense.
By noon, Nia had authorized an independent review led by outside counsel and a civil-rights compliance firm. She suspended deletion schedules for security data across all stores. She ordered Northmere and Sentinel to preserve every configuration file, customer photograph, complaint note, and model revision connected to Marrow & Vale. Northmere responded within an hour with a carefully worded objection about scope and vendor confidentiality. Nia forwarded it to Priya with one instruction: broaden the request.
The crisis team expected the owner to focus on the viral video, public relations, and Evelyn Harcourt. Nia barely mentioned Evelyn. She wanted to know whether a person could enter one of her stores, do nothing wrong, and still become a security subject because software or staff decided she did not look like the expected buyer. If the answer was yes, then the problem was not a bad afternoon. It was an operating model.
The internal review began on a Monday and stopped feeling internal by Wednesday.
Sentinel Retail Solutions refused voluntary access to its scoring software. The retail-management company, Northmere Operations, produced contracts and invoices but claimed it did not control Sentinel's proprietary methods. Several store managers said they had never been trained on the meaning of the codes. Others admitted they knew enough to understand that some customers were labeled for monitoring before any theft indicators appeared.
The former security supervisor was named Calvin Moss.
He met Nia's outside counsel in a rented conference room away from company headquarters. Calvin was forty-six, soft-spoken, and visibly frightened. He had worked for Sentinel for eight years, the last three overseeing luxury retail accounts.
He brought a laptop, a box of printed materials, and a flash drive sealed in a plastic evidence envelope his attorney had insisted on using.
The training presentation did not mention race.
It used words like presentation profile, purchase inconsistency, environmental mismatch, and concealment opportunity.
One slide instructed guards to increase observation when multiple indicators clustered. The examples included oversized bags, repeated visits without purchase, photographing merchandise, "unfamiliarity with premium retail norms," and "attire inconsistent with location profile."
Nia read the final phrase twice.
"What does that mean?"
Calvin looked ashamed.
"Whatever the supervisor wanted it to mean."
"And the codes?"
"R was appearance risk. U was unknown customer. NQ meant nonqualified."
Priya frowned. "Nonqualified for what?"
"High-value purchase expectation."
Nia felt her jaw tighten.
"You were predicting whether someone looked like they could afford the merchandise."
Calvin nodded once.
"Officially, we were predicting loss exposure. Unofficially, yes."
"Who designed it?"
"Sentinel's analytics group. But Northmere liked it because stores using the program reported lower shrink."
"Did anyone question the complaints?"
"All the time."
"Then why did they disappear?"
Calvin looked at the table.
"The customer-response protocol routed complaints involving loss prevention to Sentinel for fact review. Sentinel would check whether staff followed Sentinel procedure. If they did, the complaint was marked unsubstantiated."