Evidence that can be checked, not just show
A pack of evidence identifies its object of origin, records who produced it and with which versions, and distinguishes precisely what it shows and what it does not.
From the capture to the seal
Each step exists for a specific reason: between uploading a file and sealing it there is a window in which the object could change, and the process closes it explicitly.
- 01
Capture
Photos, signatures, quantities and readings are associated with the work that caused them.
- 02
Up
The files go first to a staging key, not to its final location.
- 03
Check
It checks content and hash before accepting the file as part of the pack.
- 04
Promoting
The object is copied to a unique final key where the upload URL can no longer overwrite it.
- 05
Seal
The hash of the final object is recalculated, the canonical manifesto is generated and the review is sealed.
- 06
Share
The link carries random token, scope by object, maturity and revocation.
What includes a pack
The content is configured by type of work. What was not captured does not appear: a template is never filled with simulated data.
Always.
- Object of origin: work, incident, node or result of integration
- Actor that produced it and versions involved
- Time, vehicle and location when applying
- Hash per file and hash of the manifesto
- Validation of the sealed review
Only if it was captured.
- Quantities, receivers and signatures
- Associated trade documents
- Temperature, QR codes and stamps
- Video and data of the vehicle bus
As long as a photo is missing or its rise is missing, the state of the pack says evidence pending.
What does a hash prove and what doesn't?
We prefer to say this before a sale rather than after a dispute.
A hash detects byte changes
It serves to prove that the file was not altered after the seal. It does not in itself prove that the GPS was correct, that the receiver is who it claims to be, or that the time is certified.
See the security modelThree different things
A screen-drawn signature, a cryptographic signature and a third-party time seal are different mechanisms with different guarantees. We do not present them as equivalent.
See the security modelThe PDF is a representation
The verifiable content is the manifesto and the files. The document is a legible view of a specific review, not the source of truth.
Back to the processWho can see what, and for how long
The storage is private and is separated by customer, and each access authorization is registered. The links shared with a person contain a random token saved with hash, scope limited to the object, maturity and revocation; never sequential identifiers that are sufficient to reach the file.
The follow-up of a delivery expires when it is closed and shows only what is necessary. The vouchers and invoices may have different policies, because they meet different obligations.
For material that requires immediate revocation and audit of each download, access passes through an authorized gateway instead of a reusable signed URL. Issuing a link does not show that someone has seen the content.
Preguntas frecuentes
Show us a case and we model it.
The contents of the pack are set by type of work. Let's talk about what you need to support your operation.