No
sign-in required
The future public verifier is meant for signers, schools, regulators, and third parties without requiring an Otto account.
Public document verification
Otto public verification checks a certificate number or a signed PDF hash against the sealed record. This page is still a controlled preview: real uploads, production lookup, support routing, and retention enforcement are not connected.
No
The future public verifier is meant for signers, schools, regulators, and third parties without requiring an Otto account.
2
A verifier can use a certificate number or compare a signed PDF hash with Otto's sealed record.
3
Valid, Changed, and Not found cover the public-safe outcomes without exposing raw audit details.
Full
Verification must remain available for the school's full document-retention period, even after school departure.
What it checks
The public verifier is narrow by design: enough to prove integrity without exposing private records.
The public number printed on the certificate should find the sealed record and return public metadata.
Useful when a signer, employer, auditor, or regulator has the certificate page.
A completed PDF should match the stored SHA-256 hash; changing one character should fail verification.
Useful when the verifier has the PDF and wants to know whether the file changed.
A valid result shows document title, school, completion date, certificate number, verification code, and signer initials only.
Useful for confirming the document without exposing private signer records or the raw audit trail.
Each school export includes the certificate data needed to keep verification available for the retention period.
Useful for continuity if a school later leaves Otto or needs audit package evidence.
Verification input
The control is visible for review, but this ticket does not accept real files, parse PDFs, or store uploaded documents.
Certificate number found
Entering the sample certificate number returns public-safe document metadata and signer initials.
The entered certificate or document hash matches Otto's sealed-document record.
Uploaded PDF hash matches
A PDF whose SHA-256 hash matches the sealed record should show Valid.
The entered certificate or document hash matches Otto's sealed-document record.
One-character change fails
Changing one character in the hash creates the Changed state required by the QA plan.
The document hash does not match Otto's sealed-document record, so the proof treats the PDF as changed.
Retention and export
Public boundary
Requires sign-in
NoStores upload
NoProduction DB lookup
NoRaw audit trail
HiddenResults
Each state is intentionally limited so public verification confirms integrity without becoming a private record portal.
The certificate number or document hash matches the sealed record, so public-safe metadata and signer initials can be shown.
The compared hash does not match the sealed record. The verifier should treat the PDF as changed and avoid showing signer metadata.
The certificate number does not match a public proof record. The verifier should reveal no private document metadata.
Ticket 044 boundary