Architecture → Validation

Validation notes.

Every number we publish should be checkable. These notes record how each result was produced (and how it was independently cross-checked) so a skeptical engineer can rerun it rather than trust it.

VN-001 · 14 Aug 2026

One simulation, three independent languages, identical bytes

The UAV companion-power simulation behind datasheet DS-001 is a single integer model : milliwatt/millivolt units, a deterministic generator, published battery-discharge curves and measured Raspberry Pi power envelopes: implemented three times, independently: in Simplex (our own language and compiler, the platform’s native stack), in Python, and in C.

All three implementations produce byte-identical telemetry files (matching checksums per scenario) and integer-identical summaries. A bug in any one stack (or a hidden dependence on one language’s arithmetic) would break the match. The physical inputs are public, measured data: Raspberry Pi Zero 2 W power draw from independent published teardowns, standard LiPo discharge behaviour, and the 80% flight-battery rule.

The flight side is not simulated marketing: Senua AI flies full autonomous missions against a real autopilot (ArduPilot), commanded over its own pure-Simplex MAVLink codec, with QGroundControl recording the same telemetry stream as independent ground truth: on video, with the flight logs to match. See the autonomous flight use case.

Want to check a claim?

Ask for the falsification kit for any published number: the harness, the data, and the expected output.