Engineering Roadmap

The path to TRL 5

Technology Readiness Level (TRL) is the scale NATO, the EU and most defense and aerospace procurement processes use to state how proven a technology actually is, from a documented concept (TRL 1) to a system flight-proven in operation (TRL 9). The next milestone for the control plane is TRL 5: the same authorization and fail-safe behavior validated repeatedly, across a real fleet, in an environment that behaves like the target deployment — not a bigger simulation, but a harder one.

What TRL 5 requires

Four conditions, one bar

01

A real fleet, not a bigger demo

Multiple independent vehicles, each with its own verified identity, coordinated across a real network — not a single simulated process standing in for many.

02

An environment that fights back

Real network degradation, link loss, and at least one physical flight controller and companion computer in the loop — not idealized conditions.

03

Every hazard, every time

The system's conservative fail-safe behavior demonstrated across the realistic range of failure conditions, not just the convenient ones.

04

Proof that holds up to scrutiny

Repeated, statistically consistent results, independently reproduced and verified by someone who didn't build the original evidence.

Non-goals

No physical flight and no test range: every step on this path stays on the bench, in simulation, or on a virtual network — the ability to command a real vehicle stays off by default throughout. A safety threshold never moves just to make a run pass; it moves only through a documented decision that cites the measurement behind it.

Estimated at four to six months for one to two engineers plus a hardware bench, with hardware procurement running in parallel with the earlier software milestones. This page will be updated as the picture changes.