INVITED-TRIAL GUIDE · UPDATED 9 October 2026
Evidence, coverage and what a result means
How LotTrail separates recorded paths from context, states coverage and keeps corrections, and what it never claims.
This guide describes the trial scope. Access and the workflow supported for your site are agreed before the trial starts.
Physical paths and recorded associations
Where used and where from follow only recorded input and output relationships. Recorded associations are a separate view for kit checks, procedures, label jobs and booking references, each labelled as what it is. A scan, a kit check, a label print or a booking never proves what went into a product or a shipment.
Coverage comes first
Every result opens with its state. Complete within the declared scope means the admitted evidence, permissions and limits were complete for that question. Partial, unknown or truncated results say so, and LotTrail never describes them as unaffected or as a complete recall list.
Corrections, late records and conflicts
A correction is a new record from the source, not an overwrite. Late records change new investigations, not saved ones. A changed record under an existing identity is held as a visible conflict until it is explained.
Fingerprints prove bytes, not events
LotTrail keeps the SHA-256 fingerprint of each accepted file. It proves that the file is the one accepted, unchanged. It does not prove that the recorded physical event happened, or happened as described.
Quantities as recorded
Quantities are shown exactly as each source records them, with their units. LotTrail does not add them up, convert units, allocate material between outputs or check a mass balance.
No AI on the evidence
Investigations use fixed, bounded investigation views. No AI reads files, matches identities or reconstructs evidence. Plain English rules, automatic investigations and connections to other systems are not part of the trial.