The record and its presentation
A readable timeline is a projection of underlying data. Our intended evidence workflow preserves the original captured artifact separately from that presentation, so a reviewer can distinguish source material from derived fields.
Integrity needs a reference point
A hash can reveal a mismatch only when it is compared against a trustworthy reference under a defined scheme. Merely placing a hash next to a document does not establish who created it, when it existed, or whether its account of the world is true.
UpTrain does not currently implement a production verification scheme. The sample JSON intentionally carries no verified badge.
Independent attestation is a separate decision
The proposed certification path would concern one eligible, already captured artifact and an independent provider. Recording time and attestation time would remain separate facts. No attestation provider is currently integrated or contracted for this website.
Certification would not validate a model’s conclusions, cover actions never captured, or guarantee acceptance by a court, regulator, or auditor.
Sensitive content and exports
Confidential capture and selective disclosure are planned design areas, not current guarantees. Before any pilot, we would need to agree what leaves the runtime, what stays with the operator, how exports are protected, and how retention and deletion work.