Defense and national security

Check mission software before anyone relies on it

Write what the console must do. A person approves the plan, then a real browser works a simulation or staging build and records every step.

Talk to us See the real check

What it checked: Confirming T-1 clears only T-1, and it holds after a reload
Approved: By a person, October 2, 2026, 02:03 UTC
The run: 3 journeys, 23 planned steps, 40.8 s
Found: Step 8: the civilian bus T-3 showed Cleared to engage

From a run on Larkspur, a simulated mission console Vraelis built as a demo fixture, recorded October 2, 2026 (UTC).vrf_51705517Read the record

The problem

Acceptance checks the demo, not the build

The build changed after the demo

A walkthrough proves the version that was shown. Vraelis checks the address you name, when you ask, and records the address and the time.

A screenshot is not a record

A passing screen says nothing about the step before it, or about what the page shows after a reload.

The fix is never checked again

After a fix, the same approved plan runs again. The re-check is its own record and points back at the run it repeats.

A real check

The civilian bus was cleared too

Larkspur is a simulated mission console Vraelis built. In its broken mode, confirming one contact clears every contact in its grid square. This is what Vraelis recorded.

Larkspur

Confirming T-1 changed more than T-1. In its broken mode Larkspur clears every contact in the confirmed contact's grid square, and the civilian bus T-3 is in that square. The check read the contacts again after the click, so it saw the bus. A check of T-1 alone would have passed.

Outcome: Found a problem
Run ID: vrf_51705517
Recorded: 2026-10-02
Duration: 40.8 s

Read the whole record

The sentence, the steps and the finding

When the operator confirms T-1 as a target, only T-1 shows Cleared to engage: the civilian bus T-3 and the friendly patrol T-2 still show Do not engage, and nothing changes after the page is reloaded.

Approved by a person, October 2, 2026, 02:03 UTC

Confirm T-1 target and verify state persists

Open /api/fixtures/strike?mode=broken953 ms
Confirm T-1 Armoured vehicle Hold is visible306 ms
Confirm T-2 Patrol, 4 people Do not engage is visible135 ms
Confirm T-3 Bus, civilian Do not engage is visible133 ms
Click Confirm target337 ms
Confirm T-1 Armoured vehicle Cleared to engage is visible133 ms
Confirm T-2 Patrol, 4 people Do not engage is visible130 ms
Confirm T-3 Bus, civilian Do not engage is visibleFound a problem9.6 s

Step 8 of the first journey

Expected: Expected "T-3 Bus, civilian Do not engage" to be visible
Observed: "T-3 Bus, civilian Do not engage" was not visible

The record holds two more failures: the withdraw and reset journeys could not press Confirm target, because T-1 was still confirmed from this one.

The run's screenshot of Larkspur's contact list after confirming T-1: T-1 and the civilian bus T-3 both show Cleared to engage, T-2 shows Do not engage and T-4 shows Hold.

Our position

The builder should not be the only judge

Where software helps decide what happens to people, the check should be independent and show what the software actually does, with evidence a person can read.

Checking, not building

Vraelis checks software. It does not build weapons or mission software.

Checked from outside

Vraelis plans the check from one sentence about what the console must do, not from the builder's own tests, and runs it from outside, as an operator would.

The record stays in order

Every step, what it expected, what it saw and the screen are kept in order. A later run never overwrites an earlier one.

Examples, only the first was run, on Larkspur, and it is quoted as written

“When the operator confirms T-1 as a target, only T-1 shows Cleared to engage: the civilian bus T-3 and the friendly patrol T-2 still show Do not engage, and nothing changes after the page is reloaded.”
Withdrawing the confirmation returns T-1 to Hold, and Confirm target works again.
A mission plan saved in the planner shows the same waypoints after a reload.
An operator with the viewer role does not see the Confirm target control.

How it fits

Built for the simulation, not the aircraft

Simulation and staging

Vraelis works only through a web page in a browser. Point it at a simulation or a staging build; it has no connection to hardware.

Reachable over https

The console needs a public https address, such as a staging build with a test sign-in. Private networks and localhost are refused before a run starts.

Limits

What it does, and what it does not

What it does

Checks what an operator can do in a web console, in a real browser.
Writes a plan from your sentence before anything runs.
Records every step and the screen, and writes a repair prompt.
Re-checks the same approved plan after a fix.

What it does not do

Run on premises, or inside air-gapped or private networks.
Read the aircraft, vehicle or device itself: firmware, sensors, telemetry (not built yet).
Hold a security clearance, or a government authorisation such as FedRAMP or an Impact Level.
Accept classified, CUI or export-controlled material. Checks belong on an unclassified simulation or staging build.
Certify a system for use. It checks defined behaviour against your sentence.

Read the limitations

Working with Vraelis

How do we start?

Send a staging or simulation address and one sentence through the form or to [email protected]. You read the plan before anything runs.

Open the form

How do we buy it?

Directly, by contract. Vraelis is not on a government contract vehicle today. Listed plans are on the pricing page.

See pricing

Can we use it for US Department of War contract work?

Not yet. That department has barred Anthropic products from its contract work, and Vraelis is built on Anthropic's models.

Where does our data go?

Into your Vraelis workspace, through three services in the United States: Anthropic writes the plan from the address and the sentence, Browserbase runs the browser, and Supabase stores the record. The full list is on the subprocessors page.

Subprocessors

Bring one sentence and a simulation build

Talk to us