Degraded sensing
Poor light, weather, occlusion, and sensors that partially fail.
Method · Simulation & Test
Most of our progress happens in software. Testing an idea in simulation is faster, safer and repeatable in a way that field testing never is — so we find problems on screen, and only move to hardware once the software holds up.
The Method
Autonomy is developed by iteration, and iteration speed decides how good a system eventually becomes. In the field, a single test can take a day to set up and produce one noisy result. In simulation, the same scenario can be run thousands of times before lunch, with every variable controlled.
That does not make simulation a substitute for reality — it makes it the filter. By the time something reaches hardware, the obvious failures are gone, and the tests that remain are the ones that genuinely need the physical world.
The Loop
Our name describes the method. Every run — simulated or physical — is recorded, replayed and assessed honestly. What went right, what went wrong, and why.
What We Test For
Anything can be made to work in the nominal case. We spend our time on everything else.
Poor light, weather, occlusion, and sensors that partially fail.
What the platform does when the link thins, drops, or returns unexpectedly.
Situations the system was not explicitly designed for, to see how it fails.
Behaviour right at the boundary of the limits an operator has set.
Whether the same input reliably produces the same behaviour.
Transferring control between autonomy and operator without confusion.
Our systems have not been fielded. Everything to date has lived in development and simulation; our first end-to-end real-world mission test is planned for December 2026. We would rather say that plainly than imply more.
Go Deeper
If disciplined testing is how you like to work, you'll fit here.