State exactly what has been recorded or checked.
Start a conversationEviState Core / Infrastructure / Implementation
One architecture. Three entry points.
This page covers the established, demo-backed ES Record and ES Mail entry points. ES Stamp, for files and objects, remains in controlled development.
Trust under challenge
Trust depends upon evidence that can withstand challenge
EviState Core strengthens the evidence around origin, continuity and relationships without claiming to replace ordinary cybersecurity or secure storage.
Explore Security →01
Persistent evidentiary infrastructure
Evidence around digital state that remains attributable, inspectable and lifecycle-aware
ES Record is the persistent infrastructure layer built on EviState Core. It can record the accountable subject, authority route, official channel, digital object or content record, publication state, relationship context and provenance reference behind public or controlled digital information.
Its purpose is not to declare a universal truth. It makes the evidence supporting a bounded state—and any evidenced change to that state—available through a genuine live route.
Securing a record is not only about where it is stored. It is also about being able to establish its origin, history and relationship to surrounding evidence.
Accountable subjectAuthority and scopeRelationship stateLifecycle and provenance
- 01Accountable subject
- 02Authority and scope
- 03Digital object or channel
- 04Publication and relationship state
- 05Lifecycle and provenance
02
Accountable communications within evidenced relationships
Communication can change channel without becoming context-free
ES Mail applies EviState Core to important communications and instructions within an evidenced relationship. That relationship may involve more than one communication channel.
An interaction established through email may subsequently continue through SMS. Rather than treating the SMS as automatically trusted—or as an entirely unrelated event—ES Mail provides a route to inspect the relevant evidentiary state.
Authentication of a channel is not the same as evidence of relationship continuity or authority.
Recorded sender contextMessage referenceCross-channel continuityBounded evidentiary outcomes
Live sender state
EviStateSSender
RRecipient
- Recorded domain
- proovetech.com
- Verification route
- Official live record
- Record principle
- Do not trust the badge alone
ES Mail / Cross-channel continuity
Communication can change channel without becoming context-free
ES Mail extends the Counterparty Handshake across communication environments. The relationship remains visible while the channel changes, but the later communication receives its own evidentiary conclusion rather than inheriting trust automatically.
AEmailOriginating partyIdentity · authority · route
BSMSReceiving partyKnown context · live state
03 / Relationship evidenceChange channel
The interaction continues through SMS. The communication environment has changed, so continuity should not simply be assumed.
Possible continuity outcomes
The demonstrated evidence produces the highlighted outcome- Current resultContinuity established
- Possible outcomeContinuity supported
- Possible outcomeContinuity conflict identified
- Possible outcomeContinuity not established
Inspectable evidence
See the Email → SMS demonstrationThe objective is not to make every communication trusted. It is to make the evidence around the relationship inspectable. ES Mail does not guarantee the sender, approve an instruction, authorise payment or replace normal security and due diligence.
Shared operating discipline
Every service makes its boundary visible
Do not imply claims outside the bounded verification.
Expose expiry, correction, suspension or supersession.
Direct the viewer to the current official route.