TRV-2026-1875Certified recordPeer-reviewed

Sample-efficient machine learning for dairy pathogen detection and origin traceability under multivariable conditions using gold nanoparticle colorimetry

Storage temperature, humidity, and time jointly influence pathogen growth in dairy products, yet most rapid detection methods are validated under single-variable conditions that do not represent real supply chain scenarios. Testing across these combined conditions sharply increases the number of samples needed, whereas dairy safety studies usually work with small data sets, which limits the use of conventional machine learning. Here we combined gold nanoparticle colorimetric sensing, a time-temperature-humidity…

Science · The Trace — both readings · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

A sample-efficient Random Forest model trained on colorimetric readings predicted pathogen concentration and identified dairy pathogen species and production region with high accuracy under combined storage conditions.

Current reading — problem

Because each region was represented by a single commercial product per type and one production batch, the results are only proof-of-concept and may not generalize to wider supply chains.

What this doesn’t fix

Each region was represented by a single commercial product per type and a single production batch, so the findings are proof-of-concept and not validated across wider products or batches.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1875, v1: “Sample-efficient machine learning for dairy pathogen detection and origin traceability under multivariable conditions using gold nanoparticle colorimetry.” Truvace, 2026-10-19. /record/TRV-2026-1875 (accessed at citation time). sha256 e9e52321123abdb1…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1e9e52321123a…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1875 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.