Proof summary
Status, proof type, issued-at time and the context needed to understand the bundle quickly.
Public verification
Open a proof, inspect it, and verify what was sealed.
LegalProof should adopt the same clear posture already visible in CargoProof: the proof is not trapped inside the product. A verifier opens a public page, reads the record and retrieves the relevant artifacts.
Readable proof page
PDF + JSON artifacts
Signature + key
Anchor material when available
What the verifier should see
A good public proof page is not only a display layer. It is the readable surface of the proof engine underneath.
Artifact access
Links to the PDF, canonical JSON and the cryptographic material exposed by the deployment.
Stable cryptographic reference
Hash and Merkle-root level identifiers that allow the proof to be referenced consistently later.
Independent review posture
The page is intended for counsel, counterparties, auditors or compliance teams, not only the original sender.
What verification is designed to prove
Keep the explanation precise and careful.
What version was sealed
The proof can show the version of content or document state that was preserved in the bundle.
When the bundle was issued
The record can show the issuance time and related technical timing material captured by the flow.
What artifacts support the record
The verifier can retrieve the human-readable and machine-readable outputs instead of relying on assertions alone.
What verification does not prove by itself
The site must include this caution explicitly. It increases credibility.
Not automatic identity proof
Identity assurance depends on the workflow and any authentication or trust service actually used.
Not automatic legal qualification
A sealed bundle is not automatically a qualified electronic trust service unless that exact service and provider configuration exists.
Not a legal opinion
The proof surface supports review and evidence handling. It does not decide the legal outcome of a dispute.
Recommended wording for the site: LegalProof provides a cryptographic verification surface. Legal effect depends on the governing law, the concrete workflow, and the trust services actually used in the deployment.