Chapter 4.8 — Turning the Medical Visit into an Intelligence Opportunity
Chaala finishes, leaving the priorities clear. For several seconds JEEM says nothing. His attention shifts between the communications plots already gathered and the orbital telemetry feed from the
Azure Voyager.
Then he looks up.
"Captain, I recommend we stop thinking of the Azure Voyager merely as transportation."
Wilbur glances toward him. JEEM brings up a schematic of Marinagua, followed by the Voyager’s current orbital track.
"We have been attempting to understand the Alejia communications environment primarily from down here. That provides excellent local collection, but only across a limited horizon."
He highlights the orbiting Scout ship.
"The Azure Voyager is a TL-15 Scout vessel with considerably more sensor processing, communications capacity and computing power than anything we can deploy from the cutter. We should use the ship as an electronic surveillance platform."
A new layer appears over the planetary map.
"Not to read everything."
JEEM emphasizes the point before anyone can draw that conclusion.
"To collect everything we reasonably can."
He begins marking categories.
"Signal frequency. Duration. Direction. Modulation. Relative power. Repetition. Timing. Apparent source area. Changes before our movement, during our movement, during each handoff, while the Doctor is with Kade, and after we return."
Another marker appears over the cutter.
"Mr. Voss remains useful here because orbital collection and local collection answer different questions. Voyager may see that a transmission originated from this portion of Balac Pontli. Voss may be able to tell us which side of the district it came from, whether it coincided with a nearby transmitter, or whether something that looks like one signal from orbit is actually several."
Harlan Voss studies the display and gives a short nod.
"That I can do."
He gestures toward the city.
"Especially if you give me exact timestamps. I don’t need to understand what they’re saying to tell you who lights up when you move."
JEEM nods.
"Precisely."
Wilbur has been studying the timeline rather than the map, finally, he leans forward.
"Then we need to define what we’re actually trying to learn before we start collecting."
He looks toward Chaala.
"Your point about the ambush simplifies things. We aren’t hunting the people who attacked the Harrier because we want to close an old case. We are trying to identify who matters now."
Wilbur touches the timeline.
"So we establish known events."
A marker appears.
"We leave the cutter." Another marker.
"Someone receives us." Another marker.
"We get handed to somebody else." ANother marker.
"Transport changes." Another marker.
"We arrive wherever Kade is being kept." Another.
"Doctor Shone begins examining him." Wilbur looks around the compartment.
"Those are things we know happened. Exact times. Exact people we can see. Exact places when we can establish them."
He points toward JEEM’s communications display.
"Then we compare those known events against what happens electronically."
Wilbur moves two markers closer together.
"If every time responsibility for us changes hands, a particular network wakes up, that means something."
Another pair.
"If one group transmits when we depart, another answers when we arrive, and a third becomes active only after the meeting is over, that gives us a chain."
He pauses.
"Not necessarily a chain of command."
Wilbur looks specifically toward Chaala.
"But a chain worth investigating."
JEEM adds quietly,
"And if the same sequence occurs repeatedly, its value increases."
The comm terminal sounds softly as Edrin Mallor joins the discussion from the
Azure Voyager. Edrin has apparently been listening for several minutes.
"There is one thing I want everyone clear about before we start expecting miracles from the ship."
He brings up one of the captured Alejia bursts. A dense block of encrypted data fills part of the display.
"This is not one problem."
He separates it into several boxes.
"First we have to capture the transmission." The first box illuminates.
"Then determine which network it belongs to."
A second.
"Then defeat whatever encryption that particular network is using."
A third.
"Then translate what we recovered."
A fourth.
"Then decide what the Alejia actually meant."
He leaves the boxes displayed.
"Those are not the same task."
Edrin enlarges the encrypted burst.
"Our technology gives us an enormous advantage. More computing power. Better signal processing. Better storage. Better ability to compare thousands of transmissions against one another."
He shakes his head slightly.
"It does not give us the missing key because we want it badly enough."
Wilbur smiles faintly at that.
Edrin continues.
"And even if JEEM hands me the key to this transmission tomorrow morning, what comes out may still be Alejian shorthand between two people who already know what they are talking about."
He replaces the encrypted text with a deliberately simple example.
"Suppose we decrypt a message that says, ‘The third cord has passed beneath the blue hand. Return the stone before sunset.’"
Edrin looks toward the cutter feed.
"Wonderful. We broke the encryption."
A pause.
"Now tell me what it means."
Nobody immediately answers.
"Exactly."
He removes the example.
"Language matters. Tribal usage matters. Obligation matters. Titles matter. Personal relationships matter. A phrase that is literal to us may be procedural to them. Something that sounds like an order may be a courtesy. Something that sounds harmless may carry enormous significance because everyone involved understands the context."
JEEM adds,
"And nine factions do not necessarily mean one encryption system."
Edrin nods.
"That too."
He brings up several previously collected signal families.
"We may crack one network and learn almost nothing about another. We may identify a key-change interval without being able to predict the next key. We may successfully decrypt twenty messages and discover nineteen are routine logistics."
He settles back.
"That is how this works."
Then he smiles slightly.
"Which does not mean Chaala’s order is wrong."
The orbital display returns.
"Quite the opposite. If she wants computer resources concentrated on these short bursts, we can do that."
He taps the orbital track.
"And JEEM’s idea gives us more data to work with."
Edrin looks offscreen briefly.
"Amara?"
Amara Havel’s voice joins the channel.
"Already looking at it."
A second orbital schematic appears.
"We can reallocate a significant portion of the Voyager’s sensor and computer capacity while the medical team is moving. I can also make sure the sensor packages are synchronized so JEEM gets one continuous timestamped collection set rather than several systems producing separate logs."
She enlarges the orbital path.
"But orbit is orbit. We will not sit directly over Balac Pontli staring straight down at it all day. We collect when geometry permits, build successive bearings over multiple passes, and combine them with what Voss and the cutter hear below."
She pauses.
"Urban structures, terrain, reflection and thousands of legitimate emitters will complicate localization."
JEEM nods.
"Which is why correlation is more important than individual intercepts."
Amara continues.
"I can also prioritize passive collection. The less we transmit unnecessarily, the less we advertise exactly what we are doing."
Edrin looks toward her feed.
"Good."
Then back toward Chaala.
"I’ll take responsibility aboard Voyager for organizing the orbital collection. Amara handles the ship and sensor configuration. JEEM defines what data he wants captured. Voss gives us the local reference from the cutter."
Wilbur taps the medical-visit timeline.
"And those of us going with the Doctor give them the most important thing intelligence people can ask for."
He looks around.
"Ground truth."
Wilbur indicates the first marker.
"We tell them exactly when we move."
The second.
"Who receives us."
The third.
"When responsibility changes."
The fourth.
"How long we wait."
The fifth.
"Who appears unexpectedly."
Then the last.
"And when we leave."
He sits back.
"We aren’t just going to see Kade anymore. We are creating another set of known events that JEEM can compare against the network."
Edrin nods from orbit.
"That is where this becomes useful."
He points toward the accumulated traffic.
"One intercept tells us very little."
Another set appears.
"Ten associated with known events gives us a pattern."
More appear.
"Several missions producing the same pattern begin giving us a model."
He looks directly into the pickup.
"That is how we get from encrypted noise to understanding who reacts to whom."
A moment of silence follows.
Then Ruiha clears her throat.
"There is another variable we haven’t included."
Several people turn toward her.
"Verik." She pauses.
"And probably Sera."
Ruiha looks toward Chaala.
"Unless I badly misread them, Captain Verik and Sera Vorn are going to stop by sooner or later to find out how the meeting went."
She gestures toward the intelligence display.
"So what are they?" Ruiha raises one finger.
"Do we give them a brief?"
She raises a second.
"Do we bring them in and explain what happened with Dominicus, the obligation accounting, Kade, and what we are planning next?"
Then a third finger.
"Or do we treat them as useful people who are helping us but who also have their own motivations?"
She lets the last possibility hang for a moment.....
"Because Verik knows this planet better than we do. He knows people we don’t. He understands relationships we are still trying to identify."
Ruiha glances toward JEEM’s network display.
"That makes him potentially very useful."
Then she looks back to Chaala.
"It also means anything we tell him may enter networks we do not control."
Edrin says nothing...Neither does JEEM. Ruiha continues.
"There may be a middle ground. Tell him what he needs to know to help us, ask him questions only he may be able to answer, but do not hand him our entire collection picture."
She gestures toward the displays.
"For example, we might ask him who normally assumes obligation for an offworlder moving between tribal authorities without telling him that we are mapping communications every time that responsibility changes."
Voss gives a quiet grunt of agreement.
Ruiha finishes by looking directly at Chaala.
"But that is your call, Captain. When Verik and Sera come asking how things went, are they being briefed as partners…"
A short pause....
"…or handled as very useful friends whose interests happen to overlap with ours?"
Around them, the plan has begun to take shape.
The medical visit remains exactly what Doctor Shone intends it to be: an attempt to reach Tomas Kade and determine his condition.
But around that humanitarian purpose, another operation is forming, the team on the ground will provide known events. Voss will listen locally. and the cutter will record what it can. High above Marinagua, Amara Havel will configure the
Azure Voyager for passive collection while Edrin Mallor organizes the orbital surveillance effort. JEEM will bring the pieces together. And somewhere inside thousands of bursts of encrypted Alejia traffic, they may begin learning—not everything the Nine Tribes are doing...but who reacts when the Scouts move.