1
Ingest the sensitive event
Bring in the relevant content, matter metadata, access record, notification state or document bundle that needs to be preserved.
How LegalProof works
A narrow workflow on top of VeriSeal Core.
Keep the architecture clean. VeriSeal Core handles the cryptographic layer. Public Verify handles external reading. The LegalProof site explains the product and routes qualified prospects to the next step.
Backend separated
Public verify separated
Marketing separated
Workflow-ready later
The recommended four-step flow
The message should mirror CargoProof’s existing logic: request or ingest, seal, expose a proof surface, and keep independent verification possible later.
2
Canonicalise and seal
VeriSeal Core produces the canonical JSON, signed PDF, cryptographic signatures and ledger-linked fingerprint material.
3
Store or expose
Keep the proof private by default, or expose a public verification page when a third party needs a readable and stable reference.
4
Verify and reuse
Later, the proof can be checked, cited and revisited without reopening the internal workflow or reconstructing the event manually.
What gets sealed
This is the trust-grade explanation layer that supports the commercial story without dragging the site into backend implementation details.
Canonical JSON
The machine-readable record that defines the bundle consistently and supports downstream verification.
Certified PDF
A human-readable representation designed for sharing, review and preservation.
Hashes and Merkle root
The cryptographic fingerprint that binds the bundle and connects it to the broader VeriSeal ledger posture.
Verification artifacts
Detached signature, public key and anchor material that can support independent review outside the UI.
What stays outside the MVP site
The site should sell the architecture without pretending to be the application itself.
Backend proof logic
Hashing, signing, PDF generation, timestamping, ledger logic and APIs stay in VeriSeal Core.
Public verify frontend
The read-only verification surface remains a separate frontend that can be proxied under the LegalProof domain later.
Capture and case workflow
Matter intake, access capture, team workspace and payment flow can come after the marketing launch, not before.
Do not mix the marketing site with proof-generation logic tonight. A fast, credible split is more valuable than a rushed monolith.