EVIDENCE INTEGRITY

Follow the evidence
back to its source.

Order references, original files, timestamps, and event history explain where the record came from. Integrity checks let reviewers examine its digital state.

EVIDENCE MODELOriginal evidence. Recorded references.
Committed originalSource file + recorded SHA-256 digest
SOURCE
Separate, linked records
Finalized manifestFixed inventory and integrity references
Event historyRecorded actions, sources, and timestamps
File integrity checkCompare a file with its recorded digital fingerprint.
Compare digital files with the references recorded in the Proof.
01

Order association

Each Proof belongs to a transaction. The order reference and item information give the evidence context and identify the shipment being discussed. The association links the evidence to the transaction; it does not independently identify the physical item that was shipped.

02

Sources and timestamps

Packing video, participant statements, system events, and carrier reports retain their recorded source information. The timeline places these contributions in chronological context.

Timing sources may differDevice capture time, receipt time, and carrier-reported event time can differ. The timeline preserves those distinctions.

03

Preserved originals

The original is the source file committed to the Proof. Source-linked moments refer back to that recording. Original describes the stored source file, not an independent determination that everything depicted is true.

04

Finalization and event history

Finalization fixes the committed evidence inventory in a manifest. The inventory retains the recorded digital state, while supported later submissions and activity remain separate. Audit events record supported actions on the Proof.

05

File integrity checks

PackProof records SHA-256 digests for committed evidence and finalized manifests. A digest acts as a digital fingerprint: a check compares the file’s bytes with the recorded reference. A match confirms that byte-level comparison.

06

Review scope

An ordinary Shared Proof link exposes the shared record and recordings. Separate buyer-receipt and claims-review modes can limit fields and media. Reviewers should check which material their view includes and which sources are unavailable. An omitted submission is a gap in the available record, not a finding against a participant.

07

Exports and independent checks

A Proof archive includes an inventory describing available, omitted, or missing material. The independent verifier checks included files and, where present, signed records against separately obtained trust information.

Export scopeAn export represents the Proof at a defined point in time. Verification uses the available integrity references and separately obtained trust information for signed records.

Read the export verification steps
08

Retention and access

Participant permissions govern contribution and management. Shared views provide separate recipient access. Check the Proof’s preservation status and applicable account terms for its retention period. Export records that need longer preservation and review the inventory to confirm what your copy includes.

EVIDENCE LIMITATIONS

What a Proof can establish.

What you can inspect

  • The order association and recorded item details.
  • Available evidence, its sources, and reported timestamps.
  • The sequence of recorded activity and disclosed gaps.
  • Whether checked files match their integrity references.

What remains outside the record

  • Events that were never captured or submitted.
  • Independent authentication of an item.
  • Uninterrupted physical custody or package contents at delivery.
  • Whether a claim succeeds or a participant is at fault.

PackProof preserves evidence. The reviewer applies the relevant decision process.