Evidential Mark

How to Verify the EviWrite Mark

Learn how the mark should be checked against an official EviWrite route, receipt, proof link, or authorised evidence context.

A genuine mark should connect to verifiable EviWrite context where possible. The safest approach is to check the official route, receipt, proof link, or evidence package rather than relying on the visual mark alone.

Core principles

How this mark guidance should be read.

The EviWrite mark only has value when its meaning remains controlled, checkable, and bounded by the evidence behind it.

Check the official route.

Do not rely on a screenshot, copied icon, cropped image, or unsupported claim. Look for an official EviWrite route or receipt context.

Check the claim being made.

A valid mark does not automatically validate every claim around it. The evidence must match the claim.

Check the limits.

A verification result should explain what is supported and what remains outside the record.

verification

What this explains.

Verification path

A marked item should lead to evidence context.

Where the mark is clickable or accompanied by a proof link, use that route to inspect the record, receipt, public proof, or claim boundary.

  • Check the URL or official source.
  • Check the receipt or proof reference.
  • Check the record identity.
  • Check the verification status.
  • Check what the evidence does not claim.

Static use

Static mark use needs extra caution.

A mark printed on a document, image, slide, certificate, PDF, or media file may be legitimate, but the mark alone is weaker unless it includes a verification route or reference.

Screenshots

Screenshots of the mark are not verification.

Screenshots can be copied, altered, detached from context, or reused. Treat them as prompts to check, not as proof by themselves.

Important

The mark is not proof by appearance alone.

The EviWrite mark should point to evidence, verification context, public proof, or authorised use. A copied mark, screenshot, icon, or unsupported visual claim should not be treated as EviWrite verification by itself.