Lab / Truth gates
The lab

How we decide a result is real.

A clear evidence standard sits between the lab and every claim. Each result carries how it was produced — rigor is built into the pipeline, not added after.

The gates

Contract gateRows match the logger schema; provenance is verified.
Model gateBaseline passes clean-vs-post-use, IQOS-vs-vape, time-bucket & false-alarm thresholds.
Adversarial gateLabel-shuffle & metadata-only checks must fail to act as detectors.
Evidence gateEach result is tagged with the stage it was produced at, from bench to validated.
Storage gateEvery bundle has a manifest + samples; filenames carry no labels.

Evidence ladder

Every result is tagged with how it was produced, so we always know what a number is allowed to mean.

PipelineAnalysis pipeline & modeling.
BenchControlled lab hardware — where we are now.
ChamberRepeatable sample enclosure.
FieldReal environment.
ValidatedRepeated, reviewed, and confirmed.

Where we are now

Current stage controlled e-nose bench · ESP32-S3 LIVE

What we are working toward: bench and chamber runs that move each result up the ladder — from pipeline baseline to validated.

References

  • 01PHASE0_HARDWARE_LAB.md — the bench rig & gate workflow.
  • 02PHASE1_CONTROLLED_ENOSE_EXPERIMENT.md — gate definitions & checks.
  • 03GitHub — XoAnonXo/aeralyte.