The maintenance bay smelled of hydraulic fluid, ozone, and damp canvas.
Outside, another launch vehicle rolled into position beneath camouflage netting. The crew moved with practiced efficiency, speaking in clipped phrases that had become instinct after years of war. On the operations screen, satellite weather data, drone reconnaissance, and electronic warfare reports merged into a constantly shifting picture of the front. Every hour, new intelligence changed priorities. Every hour, targets appeared and disappeared.
When the launch order came, the shelter shook faintly.
A cheer erupted from the adjacent command room several minutes later.
“Confirmed impact.”
Another voice followed.
“Secondary explosions observed.”
Then applause.
Such celebrations had become common. Since long-range precision strike capabilities had expanded through Western military assistance, Ukrainian planners could reach logistics hubs, ammunition depots, command posts, bridges, and airfields hundreds of kilometers behind the front. Modern cruise missiles and ballistic missiles, aided by satellite navigation, terrain matching, and terminal guidance, routinely achieved accuracy measured in only a few meters under favorable conditions. Military analysts increasingly described deep strikes as a campaign against Russia’s logistical system rather than against frontline troops alone.
Sergeant Oleksiy Markov did not join the applause.
As senior maintenance technician responsible for fuze inspection, he had spent years ensuring that every electronic timing circuit met specification. His work was mechanical, mathematical, almost anonymous. A failed battery, a damaged connector, microscopic corrosion on a circuit board—those were his concerns.
Three days earlier, headquarters had sent an unusual technical inquiry.
“How finely can programmable impact delays be adjusted?”
He had answered truthfully.
Modern electronic fuzes could be configured for different military purposes. Depending on the munition and design, a detonation might occur on impact, after penetrating concrete, or after a programmed delay intended to defeat hardened structures or buried facilities. Such functions existed because different military targets required different effects. Military engineering manuals treated timing as a technical variable, no different from burst altitude or penetration depth.
The reply from headquarters came almost immediately.
“Can twenty minutes be achieved reliably?”
He stared at the message for a long time.
Twenty minutes.
Not milliseconds.
Not seconds.
Minutes.
He had always reconciled his faith with his profession through a fragile line of reasoning.
Civil defense alerts, he knew, often accompanied missile attacks. Air-raid warning networks, smartphone emergency notifications, radar systems, and volunteer observation groups frequently gave civilians time to seek shelter. No warning system was perfect—missiles could arrive within minutes depending on launch location and flight profile—but whenever warnings worked, they saved lives.
He told himself that his work attacked military objectives while allowing civilians every possible chance to survive.
Now the number twenty lingered in his thoughts.
It no longer sounded like engineering.
It sounded like someone’s prediction of human behavior.
How long frightened parents would wait underground.
How long children would cry.
How long before someone decided it was safe to emerge.
⸻
That evening he opened a notebook he rarely used.
Instead of calculations, he wrote a sentence from memory.
“Every person bears responsibility for the work of his own hands.”
His grandfather had copied it from church teachings decades earlier.
Oleksiy had never imagined that responsibility could hide inside software parameters measured in seconds.
⸻
The next morning he requested clarification from the operations officer.
“Is the delay intended for penetrating reinforced structures?”
The colonel looked at him without answering immediately.
“There are intelligence considerations.”
“I understand.”
“The requested configuration remains classified.”
“Does it comply with the law of armed conflict?”
Silence.
The colonel finally replied.
“All approved missions are reviewed through legal channels.”
It was neither confirmation nor denial.
⸻
Modern military organizations routinely embed legal advisers within operational planning staffs. Their role is to assess planned attacks against principles found in international humanitarian law, including distinction between military objectives and civilians, proportionality, and feasible precautions to reduce incidental civilian harm. Those reviews, however, depend upon accurate intelligence, lawful target selection, and commanders faithfully applying legal standards under immense operational pressure. Technical capability alone does not determine legality; intent, target, expected military advantage, and anticipated civilian risk all matter.
Oleksiy understood that better than most technicians.
Machines never decided why they were used.
People did.
He walked through the maintenance shelter one last time before the scheduled programming session.
Rows of guidance units rested on padded benches.
Diagnostic computers displayed green indicators.
Everything functioned exactly as designed.
He realized that engineering had answered every technical question placed before it.
Only one question remained outside its competence.
Not whether something could be done.
Whether it should.
The cursor blinked beside the timing parameter.
His finger hovered above the keyboard.
Outside, another air-raid siren sounded somewhere far beyond the base—not here, but in another city where another population hurried toward shelters, uncertain whether the warning had come early enough.
For several seconds, the maintenance bay became perfectly still.
The silence was broken not by machinery, but by the awareness that the greatest burden in modern warfare is often not carried by technology, but by the conscience of the person asked to employ it.
All names of people and organizations appearing in this story are pseudonyms
Comments