Drones, Mesh Networks, and Runtime OS — What the Ukraine War Reveals About the Future of Distributed Coordination Systems

In recent years, the war in Ukraine has become more than a conventional military conflict.

It has evolved into a large-scale testing ground for:

• AI
• Drones
• Communication Networks
• Electronic Warfare (EW)
• Distributed Systems

Among these developments, one of the most significant is the emergence of:

Drones × Communication Mesh Networks

This is not merely a communications technology.

Rather, it represents a true distributed coordination system and may be viewed as an important technological precursor to Runtime OS and Runtime Society.

Traditional Drone Operations

Early drone operations were relatively simple.

The structure looked like this:

Operator
↓
Communication Link
↓
Drone

A central operator controlled the drone.

This is a classic example of a star topology communication model.

While simple and effective, it has a major weakness:

If communication is disrupted, the mission ends.

For example:

• GPS jamming
• Radio interference
• Satellite communication disruption

can render a drone uncontrollable.

In the Ukraine war, electronic warfare (EW) has become a decisive factor, and communication disruption often determines success or failure on the battlefield.

The Revolution Brought by Starlink

This is where Starlink entered the picture.

Starlink utilizes:

Ground Station
↓
Low Earth Orbit Satellites
↓
User Terminal

to provide high-speed connectivity even in environments where traditional communication infrastructure is unavailable.

The Ukrainian military has deployed tens of thousands of Starlink terminals to support battlefield communications and drone operations.

However, Starlink also has limitations.

The Problem of Centralized Dependence

Starlink is an impressive system, but fundamentally it remains a:

Centralized Infrastructure

It depends on:

• Satellites
• Network Operators
• Communication Service Providers

As a result, it can be affected by:

• Service outages
• Technical failures
• Political decisions
• Electronic interference

There have been reported incidents where Starlink disruptions affected military communications on the battlefield.

The Emergence of Mesh Networks

In response, increasing attention has shifted toward:

Mesh Networks

A mesh network is a network architecture in which every node simultaneously functions as:

• A communication endpoint
• A relay station
• A router

Traditional networks often rely on fixed routes such as:

A → B → C

A mesh network, however, can dynamically utilize multiple paths:

A → B → C

A → D → C

A → E → F → C

If one route is disrupted, the network automatically switches to another.

This capability is known as a:

Self-Healing Network

Why Can Communication Continue Even When Nodes Fail?

The secret is that the network is continuously recalculating routes.

Each node periodically broadcasts a signal that essentially says:

“I am here.”

As a result, every node can maintain information about:

• Neighboring nodes
• Link quality
• Network latency
• Reachability

For example, suppose the following route exists:

A → B → C

Now imagine that node B is destroyed or becomes unreachable.

The surrounding nodes detect that:

“B is no longer responding.”

The routing algorithm is then executed again, and the network discovers an alternative path:

A → D → C

Communication is automatically redirected to the new route.

This is the essence of a self-healing network.

A Highly Simplified Algorithm

Conceptually, the process looks something like this:

if current_route.is_broken():

    new_route = find_shortest_path(
        source=A,
        destination=C
    )

    switch_to(new_route)

In reality, the implementation is far more sophisticated.

Many well-known routing algorithms are used in mesh networks, including:

• Dijkstra’s Algorithm
• A*
• OLSR (Optimized Link State Routing)
• AODV (Ad hoc On-Demand Distance Vector)
• BATMAN (Better Approach To Mobile Adhoc Networking)

These algorithms continuously evaluate network conditions and dynamically select the most effective communication paths.

The result is a network that can adapt, reroute, and continue operating even when individual nodes fail, move, or are destroyed.

Drones as Communication Infrastructure

Even more interesting is the idea that drones themselves become communication nodes.

For example:

Drone A
↔
Drone B
↔
Drone C
↔
Drone D

In this configuration, drones act as:

• Relay Stations
• Routers
• Flying Communication Infrastructure

As a result, even if some drones are destroyed, the network as a whole can continue operating.

Recent developments in the Ukraine war have demonstrated the practical deployment of drone-based mesh networks that dynamically establish communication routes between drones, improving resilience against electronic warfare.

How Mesh Networks Differ from Autonomous AI Drones

A common comparison is with:

Fully Autonomous AI Drones

AI drones can operate with:

• No communication requirements
• Independent decision-making
• Autonomous flight capabilities

However, they may struggle with:

• Rapidly changing situations
• Dynamic mission updates
• Large-scale coordination

Mesh-networked drone swarms, by contrast, enable:

• Distributed coordination
• Shared information
• Real-time updates

In other words, they achieve not merely individual intelligence but:

Collective Intelligence

Similarities with Runtime OS

At this point, an interesting parallel emerges with:

Runtime OS

Traditional operating systems manage:

• CPUs
• Memory
• Storage

Runtime OS extends this concept further.

Instead of coordinating computational resources alone, it coordinates:

• Agents
• AI Systems
• Humans
• Devices

For example:

Agent A
↔
Agent B
↔
Agent C

This coordination structure strongly resembles:

Drone A
↔
Drone B
↔
Drone C

within a mesh network.

From Communication Networks to Coordination Networks

The truly important question is not communication itself.

The critical question is:

What is being shared?

The Internet shared:

Information

Cloud computing shared:

Computational Resources

Web3 shared:

Ledgers

Runtime Society seeks to share:

• Decisions
• Trust
• Boundaries
• Coordination States

Runtime Society Begins on the Battlefield

What is happening in Ukraine is not simply drone warfare.

It is also a real-world experiment in:

• Distributed Nodes
• Distributed Decision-Making
• Dynamic Routing
• Self-Healing Networks

Together, these form a:

Runtime System

Communication mesh networks are not merely technologies for transmitting signals.

They are foundational technologies that enable distributed entities to coordinate with one another.

Beyond drone swarms, we can already glimpse a future in which:

• AI
• Humans
• Organizations
• Cities

coordinate through shared runtime structures.

That future points toward:

Runtime OS

and ultimately,

Runtime Society

Technologies born on the battlefield often evolve into civilian infrastructure.

Communication mesh networks may be one of the earliest signals of that transformation—a glimpse into a future where society itself operates as a distributed coordination system.

Chinoba — Runtime Society and Coordination Systems:
chinoba.org

Chinoba

Chinoba

Intelligence as Relationship

Research Platform

founded by

Masao Watanabe

AI Systems Architecture
Decision Trace
Human–AI Coordination
Algorithmic Governance