NELSE Proof
Examine the package.See exactly what the check establishes.
The public verifier works locally in your browser. It recalculates the internal consistency of a NELSE demonstration package instead of asking you to infer integrity from a screenshot or a dashboard status.
Browser-local verification
Recalculate it yourself.
Load one of the public fictional cases or drop a compatible JSON package. The browser recalculates fingerprints, chain continuity and root without uploading the file to NELSE.
No download required: click to verify
Cataract surgery
No statutory reflection period is declared for this procedure in the demonstration corpus. A professional-practice delay can still be recorded separately and its provenance remains visible.
Cosmetic surgery
The demonstration package records a 15-day period after delivery of the estimate (French Public Health Code, Art. D. 6322-30), with the resulting timing constraint represented explicitly.
The file never leaves your browser. Fingerprints are recalculated locally. NELSE does not receive the package, its contents or the result.
Download package « Cataract surgery »·Download package « Cosmetic surgery »
Establishes · does not establish
Proof is stronger when its boundary is explicit.
A journal and declared root are present in the submitted package.
That the package really originated from a particular source.
Recalculated SHA-256 fingerprints match the presented events.
That the data contained in those events is factually true.
Each event references the recalculated fingerprint of the preceding event.
That no other internally coherent version of the file ever existed.
The recalculated root matches the root declared by this package.
That it existed at a particular date without independent external evidence.
A module, version and effective date are declared.
That the corpus is legally complete or correctly encoded.
The package can declare an anchoring state; external evidence can strengthen the check.
Authenticity of an external anchor when its independent receipt is not provided.
From integrity to replay
Verification is one layer of the trust chain.
A public package can demonstrate internal consistency. Stronger assurance can additionally depend on source provenance, fact evidence, human review, external continuity evidence and the preserved historical execution context. Those layers must not be collapsed into one marketing claim.