What is checked
- Required record structure.
- Signed payload consistency.
- Signature verification where browser support exists.
- Optional local file-hash comparison.
Read first. Check what can be checked here. Keep the boundaries clear.
GetEvidex is designed to be understandable before it becomes technical. The default path is local: open the record on your device, run the checks this browser can perform, and consult the public standard when you need more depth.
1. Open
The browser reads the selected JSON record locally and shows the core fields in a human-readable form.
2. Check
The verifier checks required structure, signed payload consistency, and attempts signature verification when the browser supports it.
3. Compare
If you have the original file, the browser can hash it locally and compare that hash with the hash stored in the record.
What is not checked
- Broader legal or factual disputes.
- Identity outside the data that is actually present and signed.
- Compliance outcomes across every jurisdiction or process.
- Any file you did not choose to compare locally.
What the result states mean
- PASS — the checks that ran here passed.
- PARTIAL — the record was readable, but one or more checks were unavailable or not run in this session.
- FAILED — one or more checks that ran did not pass.
What the result states do not mean
- They do not decide legal outcomes.
- They do not guarantee identity outside the checks performed here.
- They do not replace a fuller review when the context demands one.
What stays local in this build
- File opening
- JSON parsing
- Hash computation
- Signature verification attempt
- Verification summary export