"That's a reasonable goal." He gathered the papers. "Go back to your unit. If there are further developments, I'll inform you."
Ward saluted and left. In the corridor, Mercer waited near the training hall. He had not been told the meeting's details, but had noticed the colonel's arrival.
"How did it go?"
"He's reviewing my previous assignment."
"Did he identify any new evidence?"
"Not yet."
"Then what exactly is he reviewing?"
"The decision I made and the consequences that followed."
"Wasn't that already reviewed?"
"Yes." Mercer looked toward the administrative building. "Something doesn't add up."
Ward adjusted the strap on her bag. "Perhaps not."
"Do you know why he's doing this?"
She considered telling him everything, but gave him the truth she could support. "I know he disagreed with the original review's conclusions. I don't know why he has chosen to raise the issue now."
Mercer nodded slowly. "All right." He did not press her. That restraint meant more to Ward than he probably realized: she had expected suspicion and someone deciding that uncertainty was proof of guilt. Mercer simply accepted that she did not yet have every answer.
"Training starts in ten minutes," he said. "Blake has decided to redesign the coordination exercise."
Ward raised an eyebrow. "Should I be concerned?"
"Absolutely."
For the first time since Cross had entered the compound, she laughed—brief, but genuine. As she followed Mercer toward the training hall, she decided she would not allow the review to turn every day into a defense of her past. If the evidence supported her actions, she would trust the process; if it revealed mistakes, she would face them. But she would not surrender the present to someone else's interpretation of the past. Not again.
The following afternoon, Mercer announced that the unit would be conducting a paired assessment. Each soldier would be assigned a partner for a series of problem-solving exercises, sharing information, making decisions, and completing objectives under different constraints.
Mercer read the assignments. "Dawson with Miller. Blake with Sergeant Lewis. Staff Sergeant Ward with me."
Blake looked disappointed. "Sergeant, I was hoping to work with Ward."
"Why?"
"Because I want to learn from her."
The sincere answer silenced the jokes forming around the room. Mercer looked toward Ward. "Any objection?"
"None, Sergeant."
"Then we'll change the assignments. Blake, you're with Ward. I'll supervise your first exercise."
Blake straightened. "Understood."
Ward glanced at him. "Do you know what the exercise involves?"
"No."
"Then don't assume that working with me will make it easier."
He smiled. "I wasn't planning to."
The first exercise was deceptively simple: a map of a fictional emergency site, a list of personnel needing assistance, and constraints on time, resources, and restricted access. They had to develop a plan, explain their priorities, and respond to new evaluator information.
Blake began studying the map. "We should start with the central route. It's the shortest."
"Shortest according to which measurement?" Ward asked, examining the information sheet.
"Distance."
"What about access restrictions?"
Blake checked the second page: the central route passed through an area that would become unavailable. "I missed that."
"Good thing we're reviewing it before we start."
Comparing options, Blake proposed a flexible route while Ward suggested explicitly recording changes. Neither alone sufficed, but together they produced a workable solution, and when the evaluator introduced a delay, they adjusted without abandoning the objective.
Afterward, Mercer reviewed their performance. "You communicated well. Blake, you were more willing to reconsider your first assumption. Ward, you gave your partner enough room to make decisions instead of taking over."
Blake looked pleased. "Does that mean we passed?"
"It means you completed the exercise."
"That sounds suspiciously like a yes."
"It means you completed the exercise," Mercer repeated, walking away.
The second exercise was more difficult: Blake and Ward received different information, neither seeing the other's briefing sheet, and both had to identify what needed sharing—revealing how teams handled incomplete knowledge.
Blake began by explaining his objective. Ward listened, then described her own. Their instructions overlapped in one area but contradicted each other in another.
"Which instruction has priority?" Blake asked.
"Neither, until we know why they're different. We can ask the evaluator, but we should explain the conflict clearly enough that the answer addresses the actual problem."
They submitted a clarification request and received an updated instruction. The conflict had been deliberate: the evaluator wanted to see whether they would blindly follow individual orders or recognize that the combined instructions could not be executed as written. They completed the exercise with a strong score.