Skip to main content
HAVOC: Friendly Fire

HAVOC: Friendly Fire

by Nathan Cross

military-fiction

Read Sample

Read the first 3 chapters for free

18px
Chapter 1 of 3

HAVOC Designated

PROLOGUE: HAVOC DESIGNATED

At 0421 the first signal went dark.

The Commander did not move. His hand rested at the console edge. He waited.

At 0421 and fourteen seconds, the second went dark. Fifteen seconds later, the third. The pattern was clear before it was complete. Sequential losses. Fixed intervals. Fourteen to sixteen seconds between each, consistent across three data points. In a standard firefight, positions fell in clusters. The chaos of simultaneous engagement produced near-simultaneous signal loss. Sequential losses at fixed intervals meant something else. They meant a single element moving through the contact sequence with enough control over each engagement to resolve it cleanly before moving to the next. Constant movement time between positions. The approach to each position known in advance.

He wrote: Contact initiated 0421. Alliance element conducted sequential position neutralisation at consistent interval of fourteen to sixteen seconds. Pattern inconsistent with coordinated assault. Pattern consistent with single high-capability operative moving under conditions that prevented Veth position coordination and foreknowledge of approach geometry.

At 0422 and thirty seconds, the fourth signal.

At 0423, the fifth.

At 0423 and forty seconds, the sixth.

Total duration from first signal loss to last: four minutes forty seconds. He ran the baseline comparison. Alliance regular units at comparable contact parameters: fourteen minutes eleven seconds, mean. Top performance decile: nine minutes forty. Elite specialist units, the best outcomes Alliance training and selection had ever produced: nine minutes twenty-two seconds.

Four minutes forty seconds.

The difference was not one of degree. It was a difference of category. The simulation runs had already established that. Three runs, each flagged anomalous by a training supervisor who ran out of frameworks before the third was complete. Eleven seconds on the first. Seven on the second. Six on the third, a coordination scenario rated for nine to fourteen minutes. The supervisor's final notation had been four sentences and one admission: I have no category for this.

The Commander had provided a category now. He opened the threat classification registry and found the term in the Veth lexicon, built across four centuries of engagements, which had encountered in those four centuries everything the Alliance was now beginning to encounter. The term described a specific condition: the state in which the rules of an engagement ceased to apply, not through any change in external circumstances, but through the introduction of an element that caused those rules to become unreliable. Not an unpredictable element. An element that operated outside the frame that made prediction possible.

HAVOC.

He typed it into the designation field. He wrote the description:

Non-standard combatant. Capability limits outside documented Alliance training outcomes. Expected performance ceiling: indeterminate. Monitoring at senior command level recommended.

He flagged the entry against the subject's service number. The time was 0412. He wrote HAVOC five times in the battle report. In the contact description, the threat assessment, the tactical analysis, the recommendation section, and the header field. He marked it for escalation to Veth Kaan with the priority designation he had used twice in thirty-one years. Both times he had been correct.

He read the report back. It was accurate. He sealed it and transmitted it.

The Alliance would not know for several hours, until the patrol failed to check in and the emergency protocols engaged. By then the Veth battle network would have the designation active, the report at senior command level. The enemy had a word for what the Alliance had deployed before the Alliance had a word for it. He noted this and added a final line: Designation HAVOC should not be disclosed to the Alliance. They do not yet understand the nature of what they have deployed. The asymmetry is an advantage.

He did not know the recruit's name. It would not stay unknown for long.

---

She photographed the scene before she moved.

The third contact in three weeks. The third photograph to join the series. Seventeen pages of journal entries documented the same pattern, alongside three database searches that arrived at the same conclusion from three different angles. The same shape, seen each time from a different position.

She stowed the device and returned to her station. At lights-out she wrote the entry that had been building since the patrol ended: direct, precise, the hypothesis stated plainly in the format she used when a hypothesis had earned that level of commitment.

She dated it and closed the journal.

Outside, the sector settled into its night cycle. She went to sleep with the journal under her bunk. In the morning the investigation would still be there. She had learned that the work that lasted was work done correctly, and doing it correctly required patience. She had seventeen pages.

She would have more.

Reader Reviews