Chương 7: Episode 7 - The Avarin's Objection

The document was on Cassian's locker shelf when he got back from the 0630 supplementary session. Not a physical document — a transfer notification on his tablet, a file pushed from Cirus's device to his at some point during the night with a timestamp of 0147 and a subject line that read: FORMAL OBJECTION — SQUAD 7-DELTA LEADERSHIP METHODOLOGY — VAIL, C. (SQUAD LEAD). He stood in front of his locker and looked at it for a moment. The subject line alone was going to take some processing. He sat down.

He opened the file and read it. Four pages, single-spaced, with a bibliography. Three numbered objections, each with its own subsection: the specific tactical error observed, the exercise instance in which it occurred, the quantified performance impact, and a proposed remediation. The document had been formatted to the Confederation's standard for formal squadron grievance filings — a format Cirus had apparently looked up and applied correctly, at 0147, instead of sleeping. He read it once, quickly.

Then he read it again, slowly. By the end of the second read he had marks next to two of the three objections. He set the tablet down. Picked it up. Made a third mark, lighter, next to the third. The objections were good. That was the thing he kept coming back to while he sat there. Two of them were right. The third one was wrong in an interesting way that told him something he hadn't fully understood about how Cirus was reading the situation. He sent back a single-line reply: When you're awake. Common area.

He spent the time before 0720 figuring out how he wanted to open it. * Cirus arrived at the common area table at 0720 with his slate in hand and the posture of someone who had ranked the possible versions of this conversation by probability and was prepared to execute on whichever one he found himself in. He sat across from Cassian.

His crest was at trained neutral, his wings at their practiced fold — feathers still in the way they went still when he'd made a decision and was waiting to see if the situation would allow him to implement it. He looked like someone who had decided, very deliberately, how this was going to go. Cassian had decided to not let it go that way.

"Objection one," he said, before Cirus could open with whatever he'd prepared. His stylus was flat against the table, not turning.

"My pre-exercise briefs are too detailed for real-time adaptive conditions. They create a mental model that's too rigid to update when the grid shifts. You're right." Cirus blinked. One beat.

"You're—""Agreeing. Yes. I over-brief. I know what each of you can do individually, and I build plans fixated on those capabilities, which means when reality deviates, the plan has to be thrown out rather than adjusted. I'm working on a shorter format with more decision latitude built in." He moved.

"Objection two. My redirect calls come too late because I wait for full confirmation of the grid state before calling. You're right about that too. I should be calling provisional directions earlier, with updates to follow. The hesitation costs more than the occasional wrong provisional call would." The silence had a specific quality. He'd encountered it before — the silence of someone who had loaded a precise argument and arrived ready to use it, only to find the ground had already moved.

Cirus's wings shifted three degrees, the micro-adjustment that meant he was updating without announcing it. His crest held neutral through the effort of it.

"That's two of three," he said, finally.

"Yes."

"You're not going to agree with the third."

"No." Cirus set his slate on the table. He'd prepared for Cassian to be defensive. He'd prepared, probably, for Cassian to concede something small and argue the substance. He had not prepared to lose two of three before he'd said a word, and the recalibration was visible in his crest — fractional, present, the shift of someone rebuilding a model on the fly. The skill existed. It just didn't translate reliably to live conditions yet. Cassian noted it and filed it.

"Objection three," he said, recovering.

"You're assigning positions based on individual capability profiles rather than complementary coverage. The result is redundant strengths in some areas and unaddressed gaps in others." The narrative has been taken without permission. Report any sightings.

"That's an accurate description of the current formation," Cassian said.

"It's not an accurate description of the formation I'm building toward." Cirus looked at him.

"You're mapping failure modes." The speed of it. He hadn't gotten there yet in the explanation. Cassian paused.

"Yes."

"Not strengths. Failure modes."

"Correct. What each of us does wrong under pressure, and when. When I have enough data to trust it, the position assignments are going to change. Your objection assumes the current assignments are the intended final state. They're the starting point." A longer silence.

"You haven't shared this hypothesis," Cirus said.

"Not yet."

"I made eleven quantified observations across those three objections. You're asking me to withdraw three of them on the basis of a hypothesis you won't share." His crest had moved to the concentration frequency, the grey-adjacent shade of someone actively working through something and not planning to stop.

"That's an asymmetric information problem." It was. Cassian had already worked out that it was and had decided he was going to proceed anyway.

"The hypothesis isn't complete. When it is, you'll have it."

"When."

"End of week two. Maybe three." Cirus looked at the table. The wings, folded against his back, were very still. He was deciding something. Cassian waited.

"Two of three," he said.

"Two of three," Cassian confirmed.

"I'll withdraw the third pending further information. If the hypothesis doesn't materialize, the third objection reinstates automatically."

"Fair." Cirus stood. He was halfway to his bunk when he stopped without turning around.

"The brief format. When you develop the shorter version — I want to see the decision latitude boundaries in advance. So I know which parameters I can adapt without a call." Cassian wrote it down.

"I'll build that in." Cirus nodded and went back to his bunk. He picked up his slate and his crest shifted to the concentration frequency almost immediately and he didn't look up again. Cassian sat at the table for another minute. He was thinking about the speed with which Cirus had identified the failure mode mapping — he'd gotten there before Cassian finished the sentence. He'd also prepared eleven quantified observations for a conversation he was planning to have at 0720 instead of sleeping at 0147.

He added to the file: Cirus, operating register. Not pedantry. Genuine precision. Works differently. * Cassian didn't see what Cirus wrote in his log that morning. He found out later, when Cirus mentioned it in passing as though it were a normal thing to share. Vail conceded two of three objections without qualification before I could argue either.

Third objection withdrawn pending further information — explanation provided was internally consistent and suggests a longer planning horizon than the current approach implies. Update model: leadership methodology is not static. Approach may be adaptive rather than fixed. Continue observation. He had filed the objection expecting to win or lose. He'd done neither.

Updating his model of who he was dealing with was, for Cirus, a significant cognitive undertaking — major structural renovations, performed with care and not quickly. Cassian filed this under: Cirus, trust-building mechanisms. Cross-reference: responds to precision over authority. Note — the document was four pages with a bibliography. He is not going to stop doing this. Plan accordingly. * That evening he finally pulled the maintenance record for B-7's viewport.

He'd been putting it off for a week — not because he'd forgotten, the three bolts were in his notes at entry twelve — but because the maintenance records required a secondary access request through the station's administrative system, and he'd had other things to do first, and the viewport wasn't going anywhere. The record loaded. He found the viewport entry under physical infrastructure, Level B-7, Unit 4. SEALED. SECURED PER INCIDENT REPORT 7D-114. DO NOT MODIFY WITHOUT AUTHORISATION FROM STATION COMMAND.

He looked at that for a moment. The stylus was in his hand and he had stopped moving it. He searched the accessible records for Incident Report 7D-114. It didn't exist. Not redacted, not restricted-access, not flagged as classified. It simply was not there. The number appeared in the viewport's maintenance entry and nowhere else in the accessible record system. He sat with that. He was familiar with the specific texture of this.

Not the bureaucratic texture of restricted access, where the record existed and someone had decided not to show it to you. This was something else — a record that referenced something that had been removed rather than sealed, the shape of an absence rather than a wall. He had learned the difference at seventeen, in a Meridian server archive, looking for documentation that had been there on a Tuesday and was not there on a Wednesday.

A barracks room not on the orientation map, with a viewport bolted shut pursuant to an incident report that didn't exist. He was not prepared to say what this meant. He was prepared to say that none of the possible innocent explanations held up well when you put them together. He had learned, at seventeen, to write combinations like this down and hold onto them. He filed a formal records access request for Incident Report 7D-114. The system acknowledged the request. He noted the timestamp.

He added to the infrastructure file: Viewport — 7D-114. Non-existent in accessible records. Formal request filed. Do not lose this thread. Then he closed the viewport entry and opened the brief format document. Cirus had asked for decision latitude boundaries. He needed to build them before the next drill, and the next drill was in two days, and the viewport was going to take time that the next drill didn't have. The thread was in the file. He wouldn't lose it. One thing at a time. He started on the brief.