THE SEVERANCE DEMO

Cut the link.
Watch it keep going.

We do this on a table, with the cable in our hand. Here it is as a diagram you can operate yourself — pull the uplink and see which parts of the fleet stop, and which ones do not.

Book the live versionVerify an example archive

Operate it

Pick how the site is run. Then cut it.

Fleets are run in several shapes on site, and the shape changes what you lose when a link goes. Cut the long haul, then the local segment, and watch the one line that never changes in any of them.

Unchanged in every arrangement: the drone is the one doing the checking. Taking a network away removes a conversation, never the drone’s ability to check what reaches it. No service is consulted, on any segment, in any state.

Right now

All links up. Commands are checked on board; evidence is reaching the archive.

An illustration of the demo we run live, not a live fleet. The drone counts, queue depths and timings here are for the picture; the hardware version is the one we bring to the meeting. Tethered rigs and self-meshing swarms are two more arrangements we work with and have not drawn here — they change the topology, not the argument.

What you just did

Three things. Only one of them moved.

Never changed

Who does the checking.

The drone, in every arrangement. With a pilot on site the long haul can go and the flying carries on, each command still checked on board. With nobody on site the flying stops for want of a commander — but the checking was never what depended on the link. The aircraft go on checking each other, and the evidence still stands up.

Stopped

Reach.

Cut the segment the drones actually sit on and no commander can reach them at all — not from the site, not from HQ. What does not stop is the checking: the aircraft were already talking to one another, and they go on verifying every message that arrives. They fly the tasking they already have and keep sealing what they do.

Waited

The long haul.

Outbound evidence queued on board rather than being lost. When the uplink came back the backlog drained and tasking resumed — nothing from the severed window was missing. That queue is sized in days offline, not minutes.

That is the whole claim, and it is deliberately a small one: the network carries your evidence, it does not decide your authority. A link you do not control can take away your bandwidth. It should not be able to take away your ability to act, or your record of having acted.

So who authorizes whom, exactly?

Authorization is a relation, not a state of mind: something presents a request, something else checks it. Here the drone is the one checking. Whoever is commanding it is the other side — the ground station over the long haul, the pilot over the site’s own wireless, a remote centre down a backhaul, or another aircraft in the same formation — and the credential travels on the request itself, the same way a request already carries its own authentication today.

So cutting a network removes a commander, not the drone’s ability to check what arrives. That is why the interesting state is the first cut, not the second: the fleet is off the internet and is still being flown from the site, with every command verified where it lands. Cut the local network as well and every commander is gone — and the aircraft carry on checking each other, because that traffic was running the whole time and is simply what is left when the rest goes. Nothing about the checking changed when the networks did. Nor does the sealing stop: the actions each drone takes on its existing tasking still go into its own evidence chain, and that chain is what drains to the archive when the link returns.

The obvious objection

“That is just a redundant link.”

These are not two roads to the same place: the local segment is the drones’ only network, and the long haul is how that network reaches the world. Nor is this bonded multi-link C2 — RF, cellular and satcom carried at once — which is a real product and a different thing. Bonding buys more ways to keep reaching the gatekeeper, and does nothing once every path is gone. We remove the need for one: a command is checked by the drone receiving it, not blessed by whatever sent it. Switch the diagram to the unattended dock and the difference is stark — nobody is on site to fail over to, and the fleet still produces evidence that stands up.

The second question

Survives multi-day disconnects.

Days, not minutes — and the bound is not the network. What limits a severed run is what the fleet is carrying: power, the tasking it already has, and room on board for the evidence it keeps producing. None of those get shorter because a link went down. Where your own limits land depends on your aircraft and your duty cycle, and we size it with you in the architecture review.

Why we lead with it

It is the fastest way to disprove us.

Most infrastructure claims are hard to test in a meeting. This one is not. Pulling a cable is a thing anyone in the room can do, and the result is immediate and undeniable in either direction — either the fleet keeps authorizing or it does not.

We run it the same way every time: the comparison side times out, EdSSA keeps going, and then you change one row of a sealed record and watch it fail on your own laptop. We would rather be found out in an hour than in year two of a contract.

Verify an example archive yourself first →

Bring your skeptic

The demo is the argument.

We demo before we contract. If the severance step does not do what this page says it does, there is nothing further to discuss — and you will have spent an hour finding that out.

See it break before you buy it.

One meeting: we pull the uplink live, you change one row of a signed record and watch it fail, and you verify an evidence archive on your own laptop in airplane mode.

Book the demo →