Solution · unmanned systems

Command without a leash, and a record that holds up

For UAS units whose ground stations are located and struck because they radiate continuously, whose swarms depend on a jammable arbiter, and whose mission records are asserted rather than proven.

Mission
Users
UAS units across the Services
Threats
GCS location, link jamming, identity replay, insider edits
Products
Quorum Lace / UAS, Sigilcore, Driftwell
The mission problem

Every minute of link is a minute of exposure

Emission

The GCS is the target

A continuously commanded drone needs a link that is jam-resistant and quiet. The ground station radiates continuously, which is how it is found.

Spoofing

The swarm trusts the ground

Membership is arbitrated by the GCS. Jam the GCS and the swarm fragments or accepts anything, including a downed aircraft's replayed identity.

Provenance

Asserted, not proven

After a strike goes wrong, "what was the aircraft told, and who authorised it?" depends on logs that an insider could have edited.

What changes

The aircraft carries its own authority

  • Transmit once, go quiet. A signed, time-boxed, geofenced intent capsule; link loss becomes the designed state.
  • Fail closed. Expiry, a geofence exit or a non-quorum signature stops the aircraft, without operator discipline.
  • No single tablet can task an aircraft. Capsules are signed by a quorum-bound identity.
  • The swarm authenticates itself. Admission and expulsion by quorum of airframes, epoch rotated in flight.
  • A ledger an insider cannot rewrite. Hash-chained, signed, with a formation-witnessed head.
What a trial looks like
  1. Ledger first

    Hash-chained provenance on an existing platform: no radio replacement, an immediate audit benefit.

  2. Capsules on the bench

    Intent capsules and fail-closed checks against the unit's own mission profiles and ROE.

  3. Swarm quorum in flight

    Admission, expulsion and replay rejection with the ground link deliberately denied.

Stated plainly

Whether a capsule may ever authorise weapon release is a policy decision for the user, not a default in the software.

Get in touch

The binding constraint is a signals regiment willing to run a trial.

Not capital. If you can open that door, or want the architecture note and the runnable prototype to take apart yourself, we would like to hear from you.