Assurance Middleware
for Degraded C2
and Autonomous Systems.

AURM-NET Is a Resolvix Product.

Resolvix is a C2 systems company developing assurance middleware and survivability-governance infrastructure for degraded, contested, and disconnected operations.

AURM-NET is Resolvix’s first product: a protocol-neutral assurance layer for command integrity, trust continuity, and operational coherence across existing C2, autonomy, and communications systems.

Resolvix is focused on a central command-and-control problem:

How do distributed forces and autonomous systems maintain trust, command integrity, and operational coherence when communications become degraded, fragmented, or unavailable?

AURM-NET addresses this problem at the assurance layer. It is designed to sit above or beside existing communications, autonomy, and C2 systems — adding trust, command integrity, custody, RF/GNSS evidence, and audit metadata to support decision-making under degraded conditions.

As future Resolvix products are developed, AURM-NET will remain the company’s flagship assurance-middleware layer for contested, disconnected, and degraded operating environments.

AURM-NET is being developed as a deep-technology infrastructure layer rather than a single-domain platform — a reusable assurance capability intended to be integrated across multiple domains rather than tied to one vehicle, radio, or mission system.

The Problem Is No Longer Theoretical.

“Basically, everything is getting jammed and spoofed now.”

Public reporting increasingly shows that autonomous systems may not simply lose connectivity under electronic warfare pressure. They may continue operating on positioning, timing, or command assumptions that appear valid while no longer matching operational reality.

Recent reporting has also shown GPS disruption affecting high-value defence aircraft, reinforcing that PNT uncertainty is now a live operational issue across mission systems — not only small drones.

AURM focuses on the governance layer: preserving mission-valid behaviour when RF, GNSS, trust, timing, and command freshness become uncertain.

Carries Assurance Metadata Over Existing Bearers.

AURM-NET is designed to create a protocol-neutral metadata object that binds to a command, retask, or mission event. It travels over existing radios, waveforms, and tactical networks — adding assurance evidence that helps receivers reason about whether a command remains operationally valid as conditions degrade.

Field-level structure, configuration, and integration detail are shared with qualified partners under controlled technical disclosure.

Governed Degradation, Not Uncontrolled Adaptation.

AURM-NET is designed around bounded adaptation: deciding when to adapt, when to hold state, when to suppress stale information, and when to degrade safely. It is intended to complement physical and signal-layer protections — anti-jam GNSS receivers, positioning-integrity checks, and anomaly detectors — by adding the assurance layer that helps systems decide how to behave when those inputs become uncertain, delayed, inconsistent, or degraded.

Three Deployment Patterns Across Existing Systems.

AURM-NET is designed to be protocol-neutral, so it can integrate with partner systems through the pattern that fits the deployment. Each pattern keeps authorisation, policy, and execution inside the partner’s own boundary.

Validated in Simulation. Operationalisation on the Roadmap.

AURM-NET is currently being validated through reproducible simulation scenarios. Current work focuses on command integrity, FHC validation, custody and resynchronisation, RF/GNSS evidence abstraction, contested retasking, and static behavioural trust.

Future operationalisation will require live assurance envelopes, protocol adapters, production-grade cryptographic integration, measured RF/GNSS ingestion, human-in-the-loop workflows, and lab/HIL/field validation.

Current evidence

Operationalisation roadmap

Operational Domains.

Public Materials Describe the Problem. Mechanisms Are Shared in Confidence.

AURM’s public materials describe the problem space and operational outcomes. Detailed mechanisms, validation artefacts, implementation details, and partner-specific integration pathways are shared only with qualified partners under appropriate confidentiality and security controls.