How the range breaks a system.

Adversarial testing, side-by-side benchmarking, and an assurance record that states the operating envelope it never reached.

Range capabilities

Red teaming

Operators paid to defeat your system

The red team is staffed by the range, briefed on the mission only. They are measured on whether they broke the system, which is the only incentive structure that produces an honest test.

Runs are repeated with the adversary permitted to adapt. Where a system begins to degrade under that repetition is the finding, and the file records the run it began on.

Benchmarking

Identical conditions, identical scoring

Two or more systems from different suppliers run the same scenario with the same opposition, the same environmental conditions and the same scoring rubric, published before the run.

Each vendor receives their own results in full. The programme office receives the comparison. Vendors do not receive each other's raw data.

Assurance

A file that states its own envelope

The assurance file states the scenarios run, the adversary's brief, the conditions, the failures observed, and the operating envelope outside which nothing was tested.

Structured for NATO TEVV review so a programme office can compare a Verax file against evidence gathered elsewhere without reconciling two vocabularies.

Method

Published in full, on this page, without a form in front of it. A programme office that has to trade contact details for a methodology has learned something about the supplier before it learns anything about the method.

Scoping. The vendor states what the system is intended to do and the envelope it is intended to do it in. The range writes the adversary brief from that statement. The vendor does not see the brief.

Baseline. One scripted run establishes that the system works as described. A system that fails its own baseline does not proceed, and that outcome is recorded.

Contested runs. Repeated engagements with the adversary free to adapt between them. Conditions change without notice to the vendor.

Disclosure. The vendor sees every result before the programme office does, and may attach a written response to the file. They cannot remove a finding from it.

Range specification

What the range can host, and under what constraints.

Engagement

Run duration
20 to 90 min
Runs per slot
6 to 12
Adversary
Human-directed
Adaptation
Between runs

Environment

GNSS
Denied or degraded
RF
Contested
Comms
Intermittent by design
Light
Day and night

Instrumentation

Truth track
Independent of system
Telemetry
Range-recorded
Decision log
Required
Retention
Full run archive

Systems under test

Air
Fixed and rotary, uncrewed
Ground
Uncrewed
Multi-agent
Supported
Human-in-loop
Required or optional

Handling

Classification
Up to programme level
Vendor data
Not shared cross-vendor
Model access
Not required
Source access
Not required

Output

Finding set
Per run
Assurance file
Per engagement
Format
NATO TEVV aligned
Vendor response
Attachable

Scoping starts with what the system is meant to do.

Send that, and we will send back the adversary brief we would write against it.