Know exactly what was tested.
Input integrity supports reproducible engineering checks. FlightTwin can compute SHA-256 over the original local flight files and record test rule outcomes without uploading the source telemetry to our servers.
How the evidence chain works
CSV or supported PX4 ULog, read on device.
Original input bytes, filename and byte size.
Rules, comparison, JUnit and review status.
The tool does not prove who originally created a file, when it was first recorded, or whether it was modified before the first trusted checksum. In particular, SHA-256 alone does NOT provide a cryptographic signature, trusted timestamp or formal chain of custody.
Mission Passport · Cohort provenance (v2.12)
The offline command-line tool can bind a six-flight-pair comparison to its exact original CSV bytes, its cohort manifest, operator-declared mission/airframe/conditions and testing policy. A separately retained passport can later be checked for changes before running CI.
node scripts/flighttwin-passport.mjs --manifest tests/cohort.json --output artifacts/passport.json
node scripts/flighttwin-passport.mjs --manifest tests/cohort.json --verify artifacts/passport.jsonA passport is unsigned and does not prove aircraft identity, flight condition truth, trusted acquisition time, or security approval. The browser demo does not verify Passport files; verification is available in the local Node CLI.
What we do not claim
FlightTwin is not certified for airworthiness, flight release authorization, security accreditation or classified data handling. Log integrity is a supporting engineering control, not a defence procurement or forensic certification.
Unsigned manifests can be regenerated by anyone with access to the source file. For independently trusted evidence, organizations must establish restricted access, digital signing, trusted timestamps, retention policies and approved storage procedures outside this prototype.
Local-first data handling
The public app uses browser-based parsing and local report downloads. Static assets are cached after the first successful online visit. A completed offline visit depends on the browser and its storage policies; use a locally installed source deployment for more controlled offline environments. Do not enter classified or export-controlled telemetry into an unapproved endpoint or third-party workflow.