Updated Mar 23, 2026 • ~5 min read
Chapter 6: She’s right again
RYAN
She put the shadow calculation documentation on his desk before Intel called.
He found it when he came back from the compound layout review — the analysis laid out in two pages, clean and referenced, with the sun-angle vector diagram attached. He read it and thought: *she documented it before the verification came back.*
Intel called at 1700 and confirmed the construction at the road junction. Secondary route changed to the southwestern pass. The briefing update went out to the team.
He sat in his office and looked at the shadow calculation document and thought about Madison Reeves.
He thought about her in the briefing room — the way she’d said *the secondary route* and let the silence sit before she explained. Not dramatic, not performative. She’d identified the correct moment and she’d spoken.
He thought about the two weeks of 0530 starts and the northeastern approach intelligence and the communication protocol and the way she’d adjusted her entry angle on day one when Kowalski had gone left.
He thought: *she’s right consistently, and she says it clearly, and she puts it in writing.*
He thought: *that’s what good looks like.*
He had been skeptical. He was honest enough with himself to name it: he had been skeptical, not of her record but of the deployment context — a new team member on a high-stakes mission in hostile territory. New team members were variables, and variables in that environment produced risk. His job was to manage risk.
She had spent two weeks reducing the variable.
He picked up the deployment manifest and reviewed the transport assignment. The flight to Karesh was a fourteen-hour run, commercial charter to the forward base, then a military hop to the operational staging area. The team would have the charter flight to sleep and the rest of the staging time to run the final prep.
He added a note to the operational brief: *Shadow calc verified. SW pass confirmed as secondary route. Analysis: Reeves.*
He thought about putting just *Reeves* for a moment, then let it stand. Attribution mattered. She had documented her analysis before verification precisely because attribution mattered and she knew it. He was not going to erase the attribution from the operational record.
He pulled the deployment roster.
Team composition: Torres, Kowalski, Dominguez, Lee, the five support element soldiers, and Reeves. Eleven people. He had deployed with smaller units and with larger ones and with units where the cohesion had been built over years. This unit had nine soldiers who had been together for three years and two additions from outside — Reeves, who had been here for two weeks, and himself, who had taken command eighteen months ago and had spent the first six months earning what he now had.
He thought about the unit’s cohesion relative to Reeves.
He thought: *Torres.*
He went to find Torres, who was at the equipment bay running the pre-deployment kit check.
He said: “Assessment. Reeves in the unit.”
Torres said, without looking up from the kit: “She’s in the unit, sir.”
He said: “Specifically.”
Torres set down the kit.
He said: “Kowalski adjusted his entry angle in day three to use her cover. He didn’t mention it. She didn’t mention it. It just happened.” He paused. “Dominguez came to her with the angle problem.”
Ryan said: “I know.”
Torres said: “Before he came to you, sir. He went to her first.”
Ryan looked at him.
Torres said: “It’s not a hierarchy issue. He went to her because she’d identified it first. He knew she had the analysis. He wanted it directly.” He paused. “That’s how this team works. The best analysis is the authority.”
Ryan said: “The shadow calculation.”
Torres said: “The team noticed she put it in writing before the verification.”
Ryan said: “What was the reaction.”
Torres said: “Lee said: she knew she was right and she made sure the record knew.” He paused. “He meant it as a compliment.”
Ryan said: “It was a compliment.”
Torres said: “Yes, sir.” He picked up the kit. “She’s in the unit. I would have told you if she wasn’t.”
Ryan said: “I know.”
He went back to the command office and looked at the deployment timeline.
Seven days.
He thought about the mission: fourteen months of intelligence, a compromised asset, a forty-kilometre exfiltration through terrain he’d been studying for three weeks. He thought about the eleven people he was taking into that terrain, the protocols they’d built and refined, the adjusted southwestern pass that was going to be the route that mattered.
He thought about the officer who had done the sun-angle calculation.
He thought: *I’m going to need her at the front of this.*
He thought: *I already know she’ll be there.*
He thought: *that’s the thing about consistency — it makes the future readable.*
He opened the transport manifest and confirmed the seating assignments.
He put himself on the aisle.
He put Reeves two rows ahead.
He thought: *professional distance.*
He thought: *yes.*
He thought: *seven days.*
He went back to the command office and began reviewing the updated secondary route for the fourth time, and was aware — in the specific way that had been building since day one — that his attention kept returning to the two pages of shadow calculation on his desk, and that this was more than professional interest, and that he was going to manage it with the same approach he managed every variable that introduced risk into an operational environment.
He was going to manage it.
Seven days until deployment.
He had seven days.
Reader Reactions