Use the official route.
A screenshot of a receipt or mark is not the same as verification. Verification should be checked through an official EviWrite-backed route where possible.
Verification
Verify Proof
Start here when you have an EviWrite receipt, proof link, public reference, or evidential mark and need to check it.
Verification starts with the official EviWrite route, not with screenshots, copied text, or someone else's description of a proof item. A valid verification path should let you inspect the record context and understand what the proof can support.
Core principles
How this verification route should be read.
Verification is useful because it is specific. These principles keep the record, the claim, and the limits separate.
Check what the record actually supports.
The relevant question is not whether proof exists in a vague sense. The question is what the record supports: timing, integrity, continuity, provenance, public anchoring, or something else.
Separate proof from interpretation.
Verification can help check consistency with EviWrite evidence. Interpretation still depends on context, claim language, and sometimes legal or factual assessment outside EviWrite.
Verification steps
Check the proof before trusting the claim.
A marked item, receipt, proof link, or public reference should lead to a bounded conclusion about what can be checked.
Start with the original proof route.
Use the official EviWrite receipt, verification link, public proof route, or authorised context rather than a copied image or second-hand claim.
Check the record identity.
Confirm the item, receipt, reference, or mark being checked corresponds with the evidence being claimed.
Read the verification context.
Look for what is being verified: file integrity, timing, receipt status, public proof, chain context, or another evidence field.
Read the limits.
Do not infer ownership, authorship, permission, legality, or truth unless the surrounding evidence and appropriate authority support that conclusion.
action
What this explains.
Warning
Do not verify from screenshots alone.
Screenshots are easy to crop, copy, alter, or detach from context. Use the live or official verification route where possible.
Outcome
Verification should lead to a bounded conclusion.
A good verification result should help you say what was checked and what remains outside the record.
Important
Verification checks evidence context. It does not decide the whole dispute.
EviWrite verification helps check EviWrite-backed records, receipts, public proof, proof links, and evidential context. It does not replace legal advice, courts, regulators, investigators, expert witnesses, official registers, or factual review.