What your passport said, on the day it said it.
Every published passport is a fixed version that is never rewritten. An independent timestamp authority dates each version, every value keeps the document and the person behind it, and the record of changes can only grow. When an authority asks what you declared and on what basis, the answer is already on file.
A published version never changes.
Publishing a passport writes a fixed file at its own address, version by version. A correction is a new version: the code on the label leads to it, and the previous one stays readable with the date it was published and the date it was replaced. Once a version is out, nobody can rewrite it, at the brand or at Tramaproof.
The date does not come from our clock
When a version is published, a fingerprint of its file (a SHA-256 hash, unique to that exact content) is sent to an independent timestamp authority under RFC 3161, the internet standard for proofs of date. The authority returns a signed token stating that these exact bytes existed at that instant. The token is stored beside the version, with the authority's name.
The authority can be one you already use
By default Tramaproof uses DigiCert, an independent certification authority, at no cost to you; it receives only the fingerprint of the file, never its content. A brand with a contract with its own timestamp provider can connect it instead: the credentials are stored encrypted, and that provider dates every new version.
Publication never waits for the stamp
If the authority is slow or unavailable, the passport is published all the same and the version shows the stamp as pending. The request is repeated automatically until the token arrives.
Behind every value, a document and a person.
A value enters a passport only after a person has confirmed it. From that moment it keeps its origin: the document it was read from, the supplier who sent it, the date it was captured and who confirmed it. The engine proposes, a person decides, and the record says who.
The record only grows
Evidence and the change log can only be added to. A correction adds an entry; it does not replace the earlier one. The history of a product, a certificate or a supplier's answer reads from the first entry to the last.
An environmental claim, with its list of proofs
For a claim such as a fibre content or a certification, Tramaproof builds a dossier that lists the documents behind it, who confirmed each one and when. It can be generated only when every line is covered, it is kept as a file that never changes, and its fingerprint is dated by the same authority.
The packaging declaration is dated too
The declaration of conformity for packaging that Tramaproof generates is numbered, kept as a new file at every generation and stamped in the same way. Its history shows what changed since the previous number.
When someone asks.
What did the passport say on 12 March?
Open the version that was current on that day. It is the same file the public read, with the date an independent authority recorded for it and the documents behind each of its values.
A value was wrong, and you fixed it
The corrected version and the one it replaced both stay on file, each with its own dates. You can show that the error was corrected and when, instead of having to claim it never existed.
Someone questions “100% organic cotton”
The dossier names the certificate, its validity, the composition and the chain that carried it, and the date it was generated. The file does not change afterwards, even if the evidence does: the platform shows that the dossier is out of date instead of rewriting it.
What a timestamp proves
A timestamp is a proof of date: it shows that a file existed in that exact form at that moment, and which authority records it. It says nothing about whether the content is right. That rests on the documents behind each value and on the person who confirmed them, and both are on the record too.
Questions
Which authority dates the versions?
By default DigiCert, an independent certification authority that receives only the fingerprint of the file. A brand can connect a provider it already has a contract with. The name of the authority that dated each version is shown beside that version.
Does every value get its own timestamp?
No. The timestamp covers each published passport version, and the claim dossiers and packaging declarations Tramaproof generates. Each value inside carries its own provenance: the document, the date it was captured and the person who confirmed it.
What happens if the authority is down when we publish?
The passport is published all the same. The version shows the stamp as pending, and the request is repeated automatically until the authority answers.
Can a published version be edited?
No. A change is published as a new version at the same printed address. The previous version stays readable at its own address, with the date it was published and the date it was replaced. A page is removed only after an erroneous publication or on an order from an authority.
Does the timestamp make the content legally binding?
No. It is a proof of date under RFC 3161: it shows that a file existed in that exact form at that moment, and which authority records it. What the file says is supported by the documents behind each value.
Can a confirmed value be changed without a trace?
No. A new document or a corrected value is added as a new entry, and the earlier one stays in the history with its date and the person who confirmed it.