smon

Chương 15

He shut off the water.

"Because if Victor thinks he can explain this, I want to hear how."

"That isn't why."

He dried his hands.

"Okay."

I waited.

He looked toward the rehabilitation room.

"I want to see whether he lies when he knows we have the logs."

"That is why."

Nathan leaned against the counter.

"You don't want me there."

"I didn't say that."

"You made the face."

"Apparently my face has legal standing now."

He almost smiled.

Then he said, "Come with me."

"Miriam will decide."

"I'm asking you."

I looked at the dark X9.

"Yes."

Nathan nodded.

Then his phone buzzed.

Another email.

This one was not anonymous.

It came from Elias Mora.

The technician who had told me to export the logs.

The message contained no attachment.

Only four sentences.

I did not send the first email.

I saw what happened to the event table today.

Victor did not authorize that session.

If you meet him tomorrow, ask who controls the maintenance tokens.

Nathan read it twice.

I said, "If Victor didn't authorize it, somebody else did."

Nathan looked at the X9.

"Or nobody did."

"What?"

He handed me the phone.

"If the maintenance system is automated."

The thought settled heavily.

An automated deployment might have selected Owen.

An automated maintenance process might have removed event references.

No single villain.

No dramatic command.

Just systems designed by people, approved by people, and trusted by people until the consequences became somebody else's child.

I read Elias's last sentence again.

Ask who controls the maintenance tokens.

Nathan said, "Tomorrow, we're going to find out."

Victor arrived at nine with two attorneys, a compliance director, and no technicians.

Miriam was already at the Brooks house.

She had chosen the dining table instead of Nathan's office because, as she put it, "Nobody should negotiate beside framed photographs of aircraft carriers."

Nathan had not laughed.

I sat to his left.

Sam sat across from us with his legal pad closed.

Victor looked tired.

Not frightened.

Not defeated.

Just tired in a way that made him seem more human and, somehow, more dangerous.

His lead attorney began with introductions.

Miriam stopped him.

"We know who everyone is."

The attorney folded his hands.

"Then perhaps we can be efficient."

Nathan said, "That would be new."

Miriam put one finger against his wrist.

He stopped.

Victor looked at me.

"You exported the local logs."

"Yes."

"Before third-party access."

"Yes."

"And you preserved them."

"Yes."

His eyes shifted to Sam.

Sam said nothing.

Victor leaned back.

"Good."

Nathan stared at him.

"Good?"

"Yes."

"Why?"

"Because if the local tables were altered during synchronization, a prior export lets us reconstruct the sequence."

Miriam said, "Were they altered?"

Victor glanced at his compliance director.

The woman was named Rachel Kim.

She opened a folder.

"We confirmed a maintenance synchronization occurred yesterday at 11:38 a.m."

Nathan's jaw tightened.

"Who initiated it?"

"An automated service process."

"Who controls the maintenance tokens?"

Victor's eyes moved to him.

Very small reaction.

There it was.

Miriam saw it too.

"So you recognize the question," she said.

Victor looked at his attorney.

His attorney answered.

"Maintenance credentials are governed by StrideCore's infrastructure security system."

Nathan said, "That's not an answer."

Miriam did not stop him this time.

Rachel spoke.

"The tokens are issued by an automated credential service."

"To whom?"

Sam asked.

"Authorized maintenance processes."

"Can a human request one?"

"Under some circumstances."

"Did a human request the token used yesterday?"

Rachel looked down at her folder.

"No."

Nathan leaned forward.

"So nobody at StrideCore deliberately erased the event."

Victor said, "Correct."

Sam opened his legal pad.

"But your automated process removed the visible event references."

Rachel hesitated.

"Yes."

The word changed the room.

Nathan did not raise his voice.

"Why?"

Rachel's answer came carefully.

"The synchronization service reconciles local status tables against the central incident database."

"And if the central database says an event is resolved?"

"The local reference may be removed from the active table."

I said, "Even if the patient is still experiencing the same failure."

Rachel looked at me.

"The service does not interpret clinical circumstances."

"That's exactly the problem."

Victor rubbed his thumb against his index finger.

The same movement I had noticed the first day.

Miriam said, "Who marked the first three events resolved centrally?"

Rachel opened another page.

"Service support."

"Names."

The attorney interrupted.

"We can provide relevant personnel through formal process."

Nathan laughed.

Miriam said, "You came here requesting a direct meeting."

Victor finally spoke.

"Give her the names."

His attorney turned.

"Victor."

"Give them the names."

Rachel read three entries.

Two belonged to ordinary support technicians.

The third belonged to Elias Mora.

I looked up.

Nathan did too.

Victor saw us react.

"You've been in contact with Mr. Mora."

Miriam said, "Do not ask my clients to confirm communications."

Victor's mouth tightened.

Rachel continued.

Elias had closed the third event twelve minutes after reviewing a diagnostic summary generated by the system.

Nathan said, "So Elias hid it."

"No."

Victor answered immediately.

Too immediately.

We all looked at him.

He leaned forward.

"Elias followed procedure."

"Procedure for what?"

"For incidents classified as known protective-state activations without injury."

I felt something ugly settle in my stomach.

"Without injury."

Victor looked at me.

"That classification exists because not every protective stop is a reportable malfunction."

"Owen nearly fell four times."

"And your supervision prevented injury."

Nathan stood.

Miriam said his name.

He remained standing.

Victor did not move.

Nathan asked, "Are you actually telling me that because Lauren caught him, your system treated the failure as less serious?"

Rachel said, "The classification is based on documented outcome and diagnostic category."

"That's a yes."

"No," Victor said.

"It is an explanation of how the workflow functions."

Sam spoke for the first time in several minutes.

"Who designed the workflow?"

Silence.

Victor looked at him.

Sam repeated, "Who decided that a protective knee lock without injury could be auto-resolved as a known event?"

May you like

Rachel looked toward Victor.

That was enough.

Related Stories

Other posts