AVANOAvano
Autonomy security

Autonomy: an autonomous system that knows when to stop trusting its link.

Autonomy is the security an autonomous platform's own software needs from its communications: commands it can trust, orders that lapse, and a clear signal when something is wrong. Avano does not write a platform's autonomy or its decisions.

01: Built

What exists of Avano Autonomy today.

Commands that cannot be replayed

A command recorded and sent again, altered or forged commands nothing.

Built
Permissions per module

A module whose software was replaced keeps its pairing but gains no power it was not given at the bench.

Built
A command checked against the platform’s own state

Since 4 November 2026 a permission can say “only while the platform itself says so”: a release granted for the ground is refused in flight, because the platform’s own software, not the commander, decides whether it is on the ground.

Built
Two people for an effect

A command with a physical consequence can need a second person: it is handed to the platform only with a signed authorisation for that exact command from a second operator pinned at the bench, used once, and a record naming the command and both people is written before it is handed out. Our library decides who may ask; what the command does stays the maker’s, under its customer’s authority.

Built
Orders that lapse

An order whose end has passed is never handed to the platform's software, and the platform counts the orders it let go.

Measured
A call for help from a device

A vehicle's crash sensor or a worn device can ask its team for help, or arm a check-in its team keeps; in our test a device's call rang its station and a medic within eight seconds.

Measured
A Safe State interface

Since 4 November 2026 one call of our library gives a platform's own safety monitor what the library knows: its links gone silent past the platform's bound, an order or message let go after its end, something signed or authorised refused, and doubt about the net's positions. The platform decides what each means.

Built
02: Next

What we build next, with no hardware.

Nothing further without hardware: the next step is a maker's platform.

03: Needs

What it still needs, and from whom.

A maker to implement the safe states in its own platform.

04: Status

Avano Autonomy: partly built.

Pre-release. Built and tested in our own laboratories: not deployed with any customer, not audited by a third party and not certified. The engineering record behind every line here is in the source, under docs/CORP/DEFENCE-INTELLIGENCE-LINE-2026-10-29.md.

All products: Products. Who they are for: Industries. How they are checked: Trust.