EviStateEvidential State Architecture
Verified does not mean endorsed
Menu

Object evidence

ES Passport

A product direction for evidence attached to digital and physical objects. This first public slice documents the tested digital-object reference implementation only.

Current capability

What the reference implementation can do today.

These capabilities are implemented and tested as a controlled technical foundation. They are not a claim of production service availability.

Exact-byte inspection

The tested reference adapters recognise PDF, PNG and JPEG inputs and calculate the digest of the exact submitted representation.

Signed evidence structure

The implementation can issue signed evidence records and portable evidence packages, then detect altered objects, records or packages.

Visible verification carriers

A PDF cover or image panel can carry a reference and HTTPS verification destination. The visible carrier is an interface, not the evidence mechanism.

What it does not establish

The evidence scope stays explicit.

  • It does not independently establish legal authorship, ownership, copyright or factual truth.
  • A copied mark or QR code does not make an unrelated object valid.
  • Unregistered copies and later edits do not inherit a verified state from the recorded representation.

Migration continuity

Existing references continue to work.

Existing PVN- references and issued links remain valid and are not rewritten by this route release. The established ES Record path remains canonical while the short public alias is introduced.