FLIGHTTWIN 2.13 / SIGNAL PROVENANCE

One flight can mislead.
Know what to test next.

Compare at least five matched baseline/candidate flight pairs. Inspect descriptive deterioration intervals; a source-bound CI PASS requires independent Mission Passport verification in the local CLI.

Local browser processingPaired bootstrap intervalsFail-closed decisionNo log upload

Experimental research aid, not statistically validated for operational release approval or safety certification. Pairing metadata is operator-declared; intervals do not prove causation.

01 / INPUTS

Evaluate your own paired flight set

Load a JSON manifest that names each baseline and candidate CSV file and declares mission, airframe and conditions for both. Add those CSVs locally. Files are not sent to a server.

Cohort manifest (.json)

Flight CSVs (at least ten files for five pairs)

Ready. Each source CSV is limited to 5 MiB; maximum 20 paired trials.

Sample JSON manifest ↓ CSV schema / docs ↗

02 / ENGINEERING DECISION

Confidence is part of the result

AWAITING COHORTBrowser decisions remain REVIEW without an independently verified Mission Passport.

Positive differences mean deterioration in the candidate
Metric	Mean Δ	Interval	Tolerance	Decision

Next Best Test · Evidence-directed plan

Deterministic guidance based on the submitted test decision — not an AI diagnosis or flight approval.

Signal Provenance · Trace the decision

Explore sample indexes, timestamp windows, source fields, and formulas for each quality metric. Integrity hashes refer to source bytes; mission context remains operator-declared.

The bootstrap interval is descriptive. Five observations cannot establish strong statistical power; correlated flights and unobserved conditions can invalidate conclusions. REVIEW blocks CI just like FAIL.

03 / LOCAL CI

Same gate in your developer workflow

node scripts/flighttwin-cohort.mjs \
  --manifest tests/cohort.json \
  --passport artifacts/passport.json \
  --json artifacts/cohort.json \
  --junit artifacts/cohort.xml

Exit 0 = source-bound PASS with a verified Passport, 1 = FAIL or REVIEW (including a missing Passport), 2 = invalid files/configuration. Source SHA-256 byte digests and data-coverage checks are included in the report. This is not a published Marketplace Action.

Mission Passport · Verify before you compare

Create an unsigned, SHA-256-bound record of the exact source bytes, the cohort input manifest, the declared test context and the configured analysis policy. Keep this file separately to detect later changes.

node scripts/flighttwin-passport.mjs \
  --manifest tests/cohort.json \
  --output artifacts/passport.json

node scripts/flighttwin-cohort.mjs \
  --manifest tests/cohort.json \
  --passport artifacts/passport.json \
  --json artifacts/cohort.json \
  --junit artifacts/cohort.xml

Download synthetic example Passport ↓ · Integrity limitations and verification ↗

The browser Cohort Gate does not independently verify this Passport and cannot issue a source-bound PASS; it shows descriptive statistics and a REVIEW decision. The CLI requires --passport for PASS. Matching hashes do not establish who recorded the data or whether operator-declared conditions are true.

One flight can mislead.Know what to test next.