Home  /  Technology

Engineered to be inspected

PERSEUS is built to a defence-grade engineering standard, a deterministic C++20 core, standards-based interoperability, and evidence that an evaluator can verify independently, down to the byte.

Interoperability

SAE AS-4 JAUS, the single interop path.

PERSEUS speaks JAUS over real UDP. Its wire conformance is cross-validated against an independent Python decoder, so the interoperability claim rests on evidence, not assertion.

AS5669A

JUDP transport

JAUS UDP transport, every byte of platform feedback flows over real UDP, no file-based simulation.

AS5710A

Core service set

Management state machine, discovery, heartbeat and ACK/NAK response handling.

AS6009A

Mobility service set

SetGlobalVector / SetTravelSpeed / SetGlobalWaypoint outbound; ReportGlobalPose inbound.

AS5684B · 4586/4677

SIDL & LOI semantics

Service interface definition plus STANAG-aligned levels-of-interoperability semantics.

Cross-validated.  JAUS output is independently decoded and checked against an external reference implementation, wire conformance you can reproduce, not a claim you have to take on faith.
Engineering invariants

Hard rules, enforced automatically.

These are not guidelines, they are invariants checked by automated guardrails on every commit.

Deterministic reasoning

No hidden ML, no opaque inference. The Brain is replayable, identical inputs produce identical, explainable advice.

Advisory-only output surface

Every v1 contract carries advisory_only=true. Zero commanding fields, no throttle, steering, brake, weapon or effector, anywhere in any output.

Sensor-agnostic core

Zero sensor / camera / LiDAR / radar / GNSS / radio identifiers in the Brain, doctrine or perception-products layer, audited at every commit, 0 hits.

Emergency stop stays with the host

PERSEUS implements no e-stop. Braking, steering, throttle, tracks and safety certification belong to the host platform.

Validation evidence

The current gate report.

A snapshot of the validation gates from the submission evidence. Every figure regenerates locally and is byte-verifiable against an included SHA-256 manifest.

Gate
Result
Strict-warning build -Wall -Wextra -Wpedantic …
Clean
Automated tests (unit + integration)
332 pass · 0 fail  5 build-config skips
Architecture guardrail script
OK
Sensor-agnostic core audit
0 hits
DIANA contract / runtime / host-emulator demos
PASS
Brain decision p99 (dev host, aarch64)
< 4 ms
Memory growth
Bounded · peak RSS ≈ 126 MB
Replay-determinism check
PASS
Evidence-package SHA-256 manifest
95 OK · 0 failed

Figures reflect the 2026-06-06 submission snapshot. Current counts are maintained in the repository’s verification-status record.

Reproducible evidence

Every run produces a verifiable pack.

Each demo emits a timestamped evidence archive, and a full package can be assembled with a single script. An evaluator can regenerate it locally and verify it against the included manifest.

  • Test logs & verification outputs
  • Runtime / edge-performance timing
  • COP contribution record
  • Mission-coordination advisory
  • Host-execution-feedback mirror
  • Navigation-trust & comms-degraded state
  • Content-derived evidence hash
  • Replay-determinism outputs
evidence pack · MANIFEST.sha256
$bash scripts/package_diana_evidence.sh → collecting verification outputs… → hashing artefacts (content-derived)… → writing MANIFEST.sha256… verifying manifest: ✓ 95 OK · 0 failed replay-determinism: PASS brain p99 (aarch64): 3.7 ms $
At a glance

The engineering profile.

C++20

Deterministic core, strict-warning build

Linux · aarch64

Runs on edge-class compute aboard the host

UDP · JAUS

Real wire-level interoperability boundary

Replay

Deterministic record & replay for audit

Talk to our engineering team.

We walk integration and evaluation teams through the architecture, the live JAUS demonstration, and the adapter boundary for host-UGV integration.