Chapter 6: Cross Does Not Answer

The comms log on Kashar's terminal showed three lines that refused to add up.

HAIL OUT — 07:14:33 — PRIORITY DELTA — RECIPIENT: CROSS, R. (ADM.) — FLEET RELAY CORVIN-7

ACK RECEIVED — 07:14:41 — RELAY CORVIN-7 — DELIVERY CONFIRMED

RESPONSE: NONE

Eight seconds for the acknowledgment packet. Eight seconds was fast — Corvin-7 was well within the Corridor's signal geometry, no lag, no degradation. The relay had received the hail, logged it, returned the automated confirmation. Fleet infrastructure working exactly as designed. And then nothing. No handshake, no traffic, no hold signal, no encryption flag that would indicate the channel was being routed to a secure buffer for delayed response.

An acknowledgment was not a response. Every officer who had ever touched a comms panel knew the difference. The relay confirmed delivery the way a postbox confirmed insertion — it did not guarantee anyone had opened the letter.

Kashar had opened enough letters.

He pulled the timestamp counter on his secondary screen. Hour nine. The standard command-response window for non-emergency contact was three hours. Six for active operational silence protocols. He had now exceeded both twice over.

"Send a second hail," he said. "Drop it to priority echo. Phrase it as a routine drive status inquiry. Route it through the general Fleet relay, not the direct flag channel."

Vol, at the signals console, did not ask why. He entered the parameters and the transmission went out at 09:22:07.

They waited.

The acknowledgment came back in eleven seconds. Relay CORVIN-7 again. DELIVERY CONFIRMED. Same architecture. Same silence on the far side.

"All right." Kashar leaned back. "Walk me through it."

Vol turned his chair. He had a way of organizing information that dispensed entirely with hierarchy — he laid possibilities in sequence, like a technician setting tools on a bench before surgery.

"Four scenarios. First: Cross is compromised. Someone has taken her off the board — physically, medically, or politically. She can't respond because she's no longer in command of her own communications. Second: she is in deliberate communication lockdown — a protocol she has not disclosed to us, triggered by information we don't have access to. Third: the relay is lying. The acknowledgment packet is being generated by an automated process that no longer represents the actual receipt of our signal. The relay is cycling through a dead channel and printing confirmations anyway. Fourth: she received both hails, understands what they mean, and has chosen not to respond."

He stopped there. He did not rank them. He did not assign probabilities. He had given Kashar the map.

Kashar looked at the acknowledgment timestamps for a long time. Eleven seconds. Eight seconds. The variance was consistent with live relay cycling, not a dead loop — a dead relay would return identical timestamps or fail entirely. Corvin-7 was functioning.

Which narrowed it.

"If she's compromised," he said, "someone has controlled her environment closely enough to intercept outbound hails without tripping any of the standard dead-switch protocols. That's a significant operation."

"Yes," Vol said.

"And if the relay is lying, whoever is running that deception has access to Fleet comms infrastructure at the relay hardware level."

"Also yes."

Both were possible. Both required an adversary with considerable reach. Kashar did not rule them out. He filed them to the side of the table where the things you couldn't act on went.

Which left the two he could.

---

He heard the hatch at 09:31. Not a knock — Okafor didn't knock, she announced herself by the specific weight of her footstep on the ladder, the way you learned someone's voice before you learned their name. She came into the tactical room without invitation and stood at the threshold in the way she had — midway between ease and attention, which meant she had made a decision before she walked through the door.

"Drive coupling is within tolerance," she said. "Slight thermal variance in the secondary injector but within acceptable parameters. The Ardent is ready to move if needed."

Kashar looked at her.

She had not been asked for a drive status report. She was the chief engineer. She knew when drive status was relevant to a conversation and when it was not, and this conversation had not been about the drive. The tactical room was three levels from the engine bay. She had climbed up without being summoned and was now standing in his doorway telling him the ship could go.

"Thermal variance," he said.

"Minimal. Nothing I'd flag on its own." Her eyes moved to the comms log on his terminal, just once, then back to him. "I'll monitor it."

"Do that."

She held still for a moment — not waiting, exactly, more like leaving the door open — and then she said: "I'm just reporting drive status," and turned and went back down the ladder.

The sound of her footsteps faded.

Vol was looking at his signals console. He did not say anything.

"She heard something," Kashar said.

"Engineers hear everything," Vol said. "It's the vibration."

Kashar didn't respond. He sat with Okafor's information for a moment — not the drive coupling, the other thing she had brought him, the thing she had communicated in the eleven words that weren't about the drive and the one sentence that technically was. She had climbed three levels to tell him the ship was ready. That was a specific thing to climb three levels to say.

He opened the mission log.

---

The mission log was a formal Fleet document, time-stamped by the ship's navigation computer in non-adjustable UTC intervals. It was legally binding. It was admissible. Every entry carried a hash that tied it to the navigation computer's own record, which meant the entries could not be altered after the fact without flagging a forensic discrepancy.

Kashar had written mission logs for eleven years. He knew what they were.

He typed:

09:33:41 — ATTEMPTED COMMAND CONTACT — CROSS, R. (ADM.) — HOUR 9 — NO RESPONSE RECEIVED. TWO HAILS TRANSMITTED (PRIORITY DELTA, PRIORITY ECHO), RELAY ACKNOWLEDGMENTS RETURNED ON BOTH. NO COMMAND RESPONSE LOGGED. MISSION CONTINUES PER LAST RECEIVED ORDERS.

He read it back. Every word was accurate. The log did not speculate about why there was no response. It did not characterize the silence as defiance or compromise or protocol. It recorded what had happened: he had hailed, the relay had confirmed delivery, no response had come.

He signed it with his command code and filed it at 09:33:58.

Vol was still at the signals console. He had been watching the comms log during the last transmission cycle, and now he was watching Kashar's hands on the terminal, and when Kashar lifted them from the keys, Vol set his own hands flat on the edge of the console and did not move them.

He was very still.

Kashar closed the mission log.

"Continue on current heading," he said. "Standard watch rotation. Wake me if anything changes on the comms."

"Understood," Vol said.

Kashar stood, and took one last look at the acknowledgment lines on the terminal — eight seconds, eleven seconds, Corvin-7, delivery confirmed — and then he walked out of the tactical room and let the door seal behind him.

The Ardent continued into the Corridor.

The log was filed.