Exact-byte inspection
The controlled implementation inspects PDF, PNG and JPEG inputs and binds SHA-256 and byte length to the exact recorded representation.
Exact-file evidence
ES Stamp
ES Stamp connects an exact document or image to a persistent, independently inspectable evidence record. The current controlled implementation is for digital files; physical labels and object carriers remain a separate future deployment programme.
Current capability
What the controlled implementation can demonstrate.
These capabilities are implemented as a bounded technical foundation. They do not claim that general customer issuance, physical-object authentication or public corporate stamping is already available.
Signed evidence structure
The implementation constructs canonical evidence records, signs through a managed Ed25519 boundary and rejects altered objects, records or packages.
Visible inspection carriers
A compact ES Stamp carrier can be placed bottom-left on each PDF page or in a bounded image footer. The visible carrier is an inspection interface, not the evidence mechanism.
What it does not establish
The evidence scope stays explicit.
- It does not independently establish legal authorship, ownership, copyright, factual truth or parliamentary endorsement.
- A copied mark, footer 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.
- The present digital-file implementation does not authenticate a physical object or batch merely because a carrier is attached.
Compatibility and continuity
Existing references remain valid.
Existing PVN- references and issued verification links are not rewritten by the ES Stamp presentation. A future corporate-document issuance route must preserve the same exact-file and lifecycle boundaries before it is represented as live.