“Right.”

His brother stepped toward him.

“Careful.”

“No, I want to understand this. Yesterday we had a system that passed bench testing. Today we get one warning and some discoloration and suddenly we’re dead in the water.”

“Two warnings,” I said.

He looked at me.

“And a data freeze.”

“Twelve seconds.”

“Would you accept twelve seconds without communications in the field?”

“It came back.”

“So did your brother’s convoy net.”

That stopped him.

I wished immediately that I had phrased it differently.

Not because it was false.

Because it was cheap.

Sergeant Reed’s face closed.

Mason noticed.

“Don’t do that.”

“I shouldn’t have.”

He seemed surprised by the apology.

I continued.

“But the question stands.”

Mason looked toward the open equipment rack.

“No.”

“What?”

“No, I wouldn’t accept twelve seconds.”

“Then don’t.”

He looked at the monitor.

His voice changed.

Less defensive.

More tired.

“You know what happens if we fail certification?”

“Yes.”

“Do you?”

I waited.

“Our section gets pulled from the rotation. Another unit takes the slot. We retrain on the system. Everybody gets blamed for not being ready.”

“You think I don’t understand that?”

“I think you go back to your office.”

That landed cleanly.

Sergeant Reed said, “Mason.”

I raised a hand.

“He’s allowed.”

I looked at Mason.

“You’re right. At the end of this, I go back to an office.”

His expression said he had expected resistance, not agreement.

“But before that, my name goes on the acceptance document.”

“So?”

“So if this system fails later, I don’t get to say I was only the office girl.”

He looked away.

I closed the equipment panel.

“Secure the unit. Nobody touches the connector.”

Sergeant Reed nodded.

Mason asked, “Then what?”

“Then I pull the production records.”

“From your own company.”

“Yes.”

He studied me.

“You really think they’ll hand them over?”

“No.”

That surprised both brothers.

I picked up my folder.

“That’s why I’m asking before they know exactly what I’m looking for.”

By noon, the company knew.

Not because I told them.

Because somebody at the installation had called the local contractor team and complained that an independent reviewer had stopped certification.

At 12:16 my phone rang.

I let it ring twice before answering.

The voice on the other end belonged to the program director, a man who had perfected the calm tone of someone accustomed to delivering pressure without sounding as though he was applying any.

“I heard the test ended early.”

“It did.”

“Equipment failure?”

“Undetermined.”

“Then why stop?”

“Repeated thermal warnings, data interruption, heat stress on a connector.”

A pause.

“Within threshold?”

“The warning was within threshold. The behavior wasn’t.”

Another pause.

“You know the delivery schedule.”

“Yes.”

“This installation is the final acceptance point.”

“I know.”

“If they miss certification, we miss the deployment window.”

“I’m aware.”

“Then I need your judgment, not caution.”

I looked through the office window toward the maintenance building where Mason and Sergeant Reed were inventorying removed components.

“My judgment is why the test stopped.”

The program director sighed.

Not angrily.

Worse.

Patiently.

“We’ve run that architecture for thousands of hours.”

“Not those modules.”

“Same design.”

“Different production lot.”

“Have you confirmed a lot issue?”

“Not yet.”

“Then don’t create one.”

I leaned back.

“What does that mean?”

“It means don’t turn an isolated event into a systemic finding until you have evidence.”

“Agreed.”

“Good.”

“I’m requesting production records for the last three lots.”

Silence.

Then: “That’s broader than this failure.”

“Yes.”

“Why?”

“Because the replacement showed the same symptom as the removed unit.”

“That can happen for reasons other than production.”

“Then the records will help prove that.”

Another silence.

“You’ve always had a talent for making simple things expensive.”

“That’s why you hired me.”

“We hired you to keep us honest.”

“Same job.”

This time he did not answer.

I said, “Send the records.”

“I’ll see what I can do.”

“No.”

He went quiet.

“I need them.”

“You’ll get what we have.”

“All of it.”

He exhaled.

“You’re making this adversarial.”

“No. The hardware did that.”

I ended the call.

For several seconds I sat alone in the borrowed office.

Then there was a knock.

Mason stood in the doorway.

“You always talk to your boss like that?”

“That wasn’t my boss.”

“Sounded like your boss.”

“He outranks me on an org chart.”

Mason leaned against the frame.

“That’s usually what boss means.”

“Not in my line of work.”

He nodded slowly.

“That an Iron Ten thing?”

“No.”

“What is an Iron Ten thing?”

I looked at him.

He had asked it without sarcasm.

“Staying on the radio.”

“That’s it?”

“That was enough.”

He stepped into the office.

“My brother never talks about that night.”

“He shouldn’t have to.”

“He talks about everything else.”

I closed the folder in front of me.

“Mason.”

He stopped.

“This review doesn’t need your brother’s history.”

“I know.”

“Then don’t use it to understand him.”

His expression tightened.

“Easy for you to say.”

“No, it isn’t.”

He studied me, perhaps waiting for an explanation.

I did not give one.

After a moment he asked, “You think he changed the report because of me?”

“Yes.”

His jaw shifted.

“He tell you that?”

“Enough of it.”

Mason looked toward the floor.

“He’s been doing that my whole life.”

“Doing what?”

“Making decisions for me and calling it protection.”

I said nothing.

He rubbed his palm over the back of his neck.

“When I enlisted, he told me not to go into his field. Said people would think I was following him. When I picked something else, he told me I was trying too hard to prove I wasn’t.”

A brief smile, without humor.

“Man can win both sides of an argument before breakfast.”

“Sounds efficient.”

Mason looked at me.

Then he actually smiled.

It faded quickly.

“He thinks the install crew will get blamed.”

“Would they?”

“Contractor already floated it.”

“Informally.”

“Same as with him.”

“Yes.”

He looked toward the window.

“If the module was bad before we installed it, can you prove that?”

“Maybe.”

“And if you can’t?”

“Then we prove what we can.”

He nodded.

Not satisfied.

But listening.

At the door, he stopped.

“I was out of line last night.”

I waited.

He glanced back.

“Don’t make a big thing out of it.”

“I wasn’t planning to.”

“Good.”

He left.

It was not an apology.

It was close enough to one that I did not chase the difference.

Part III — What the Paperwork Said

The records arrived at 18:40.

Not all of them.

That was the first useful thing about them.

When people gave you exactly what you asked for, sometimes they were confident.

When they gave you almost everything, they were afraid of one particular piece.

I spread the files across the desk.

Production logs. Quality-control summaries. Shipment records. Environmental test results.

The missing section was small.

Connector subassembly traceability.

I called the program director.

He did not answer.

I sent one message.

Need connector source and lot trace.