Chapter 10: Senn's Transmission

Day twelve of the Ceros transit.

The message had been flagged at 0327. Kael had not opened it during night watch—too much else running: the fuel allocation, the maintenance report from the carrier group's engine deck, the quarter-hour she had spent reviewing the engagement plan's second-wave timing before logging off. She had marked the flag as reviewed-pending and moved on.

At 0800 she came back to it. The flag bridge was at full watch, standard morning operational tempo. She took the terminal in the secondary communications alcove and locked the compartment door.

The cipher took forty seconds to reconstruct. She had not used it since the academy. It came back in the same order she had learned it—symbol tables, substitution keys, verification sequence—the same deep recall as star tables and emergency atmosphere protocols, knowledge that didn't degrade because it was never far from surface. At eighteen she had memorized it in one night, sitting alone in her academy quarters, because Senn had given it to her and she had treated it the way she treated every competency Senn handed her: as a thing worth having precisely because she hoped never to need it.

She had been keeping it available without examining why.

The message was text. Six lines:

Logistics filing, submitted Dominion High Command Operational Coordination. Second-wave main battery lock: first submission 0340, second 0341, third 0338. Four minutes from standard doctrine.

Approach vectors: doctrine-conform. Feint from ecliptic, drive from below. Your signature.

I see what you built in it.

Why.

That was the message. No offer, no argument, no accounting of the twelve years between them.

Kael sat with the decrypted text on the screen and did not write back.

Senn had read the logistics filing. The filing had been submitted four days ago—mandatory pre-battle procedure, routed to Dominion High Command Operational Coordination and seventeen subordinate desks. Not secured against an adversary with penetration at those levels. The timing adjustments were there in the filing, three revisions of the same field. Anyone who compared the submission versions carefully would see what she had changed and when she had changed it.

Senn had compared them carefully.

The message acknowledged the What. I see what you built in it—meaning: the 4-minute hold, the adjusted fire sequence, the thing Kael had embedded in a legitimate tactical document and left available to be found. Senn was positioned to find it. Senn had found it.

Why came after.

Not: what does this mean. Senn knew what it meant. The timing adjustment was either error or intention, and Senn had been reading Kael's tactical signatures for twenty years. Not error. Not: are you signaling me. By quoting the filing in the message, Senn had already demonstrated she'd read it, compared the submission versions, located the adjustment. The signal had been received. Senn wasn't asking whether the adjustment was intentional or whether it had been found.

She was asking what Kael had been doing when she built it. Whether Kael had known she was doing it. Whether Kael was prepared to say she had done it on purpose and name what the purpose was.

The question he asked versus the question he actually had—Kael recognized the distinction immediately, because she ran this analysis on tactical communications constantly, and Senn's message was a tactical communication. The form was why. The function was: I already know the what. I am asking you to name your own intention, which is the only thing I don't have, because naming your own intention requires you to own it, which you have not yet done.

The problem with naming it: naming it made it owned.

The unnamed intention in the battle plan was a technical adjustment—documented, defensible, reviewable by any external board. It existed in the space between what she was required to do and what she had chosen to do inside that requirement: the thin layer where compliance ran alongside something that wasn't compliance, invisible from the outside because it wore compliance's shape. She had been in that layer since day five, when she first noticed the timing adjustments in her own work and left them in and logged the legitimate rationale and moved on. Senn was asking her to come out of the layer.

A named intention was something different. It had a shape that could be seen from outside her own head. It was a decision with an owner—a commitment to an account of herself she would then have to hold.

She could not hold it yet. She had built the gap during three hours of tactical work nine days ago and left it in because the quality of the pause it created when she reviewed the plan told her it was right to leave it. She had not examined what "right" meant in that sentence. She had been working around it the way you worked around something you knew was there before you were ready to look at it directly. The gap existed. The rightness of leaving it existed. What she was prepared to name: not yet.

Why.

She deleted the message. Standard procedure for encrypted personal communications on operational systems: no persistent record, deletion logged as routine. The terminal returned to the fuel allocation screen.

She ran through the fuel allocation one more time. Carrier group at 91%, escort line at 94%, capital ships at 92%. All within operational parameters. These were the same numbers she had logged at 0347. These were the same numbers now.

She logged them again.

In the twenty-three hours that followed, she did not name what she had built into the plan or explain to herself why she had built it. The flag bridge ran its standard shifts. The approach vector held. The engagement plan sat on her planning terminal, unchanged, the 4-minute hold in the second-wave sequencing exactly where she had put it.

Day twelve. Ceros Station was three days away.