Authenticity vs Truth

Every verification system eventually faces the same question from a new user: "so if it's verified, it's true?" The honest answer is no, and the distinction is the entire point of the exercise.

Verifying a document means confirming two things: that it is unchanged since the moment it was issued, and that it genuinely came from the organisation it claims to. Neither of those is a judgement about whether the document's contents are correct. A hospital can issue a medical report containing a genuine clerical error; a verification layer will still confirm it as authentic, because it authentically came from that hospital, unaltered, exactly as issued.

That boundary is deliberate, not a limitation to apologise for. The moment a verification layer starts making claims about factual correctness, it has taken on responsibility that belongs with the issuer — and it has made a promise it cannot keep at scale, across every industry, for every kind of document. No independent third party can meaningfully confirm that a degree was academically earned, that a repair estimate reflects the true cost of parts, or that a certificate of origin describes goods accurately. Only the issuer, or an investigation, can answer questions like that.

What a verification layer can do, reliably and at scale, is answer a much narrower question: is this the same document that was originally put into the world? That narrower question turns out to matter enormously, because so much of the actual risk in document-based decisions comes from alteration and substitution after issuance — not from the issuer being wrong.

Authenticity and integrity are the layer independent parties can build confidence on, because they are objectively checkable. Truth stays where it has always belonged: with the organisation that created the record. Keeping that line clear is not a weakness in the system. It is what makes the rest of it trustworthy.