EviState Core defines a common evidentiary model without requiring one network, operator or universal score.
Start a conversationEviState Core / Reference architecture
Evidence establishes state — change does not automatically become state
EviState Core is an evidentiary-state architecture for establishing, maintaining and independently verifying state across digital entities, objects and relationships—including continuity or evidenced alteration over time
Relevant evidence can remain with different authorities, access-controlled, minimised or selectively disclosed.
The architecture supports accountable decisions; it does not confer truth, endorsement, safety or compliance.
Security outcome
Confidence should not have to depend upon a single source or assertion
EviState Core combines multiple evidential dimensions so that individual compromise does not necessarily make the surrounding history impossible to examine.
Explore Evidential Security →Why it exists
Point-in-time checks do not establish enduring relationship state
Identity checks, signatures, security controls and audit records each solve important problems. The weakness appears between them: the relationship changes, context is lost and the evidence needed to distinguish continuity from material alteration becomes difficult to assemble.
Record the authentic starting state and the authority behind it.
Preserve provenance and assess material changes over time.
Provide a genuine route to inspect the current state independently.
Evidentiary State Field
Evidence has context — relationships have state
EviState Core provides a public conceptual model for describing the evidence around digital entities, objects and relationships—how a state is established, whether it continues, and when a material alteration is evidenced.
Conceptual notation only. It describes the public architecture and does not disclose confidential decision functions, protocols or implementation methods.
ArchitectureAESEstablish · maintain · verify
R(A ↔ B)Relationship state
A relationship treated as an evidentiary object with its own establishment, continuity and history.
Evidence has context
An evidentiary element has a source, scope, time and relationship to the state it is being used to support.
Relationships have state
A relationship can be treated as a first-class evidentiary object with establishment, continuity, change and history.
Change requires evidence
Activity alone does not automatically create a new authoritative state. A material alteration must itself be evidenced.
State remains inspectable
A genuine route to the current record lets an authorised or independent party inspect the bounded evidence shown.
Channel continuity
The relationship is not the channel.
Digital relationships can move between communication environments. An established interaction may begin in email and later continue through SMS or another digital channel. The change of channel is an event within the relationship; it does not automatically prove that continuity exists.
EviState Core is designed to support assessment of evidentiary continuity across those transitions. The question is not simply whether a communication is authentic, but whether the available evidence supports continuity with the relationship already established.
A new channel does not automatically create a new trusted state. Evidence determines what can be supported.
Party AA
Evidenced relationship stateR(A ↔ B)EviState Core
Party BB
Channel at t₁Email
Δ channelChannel at t₂SMS
EstablishedSupportedConflictingNot established
Conceptual public model only — no scoring, protocol or confidential state-transition logic is disclosed
Public architectural foundations
Five ideas working as one evidentiary system
This public overview explains the operating concepts without disclosing confidential implementation detail.
Authentic state
A bounded account of the parties, authority, channels, context and evidence established at a point in time.
Provenance
A traceable account of where evidence came from, what it supports and how the recorded state evolved.
State continuity
An assessment of whether an established relationship remains consistent as identities, channels and circumstances change.
Independent verification
A genuine route through which the current live state can be checked without relying on a copied assertion.
Persistent trust evidence
A durable evidential trail that remains intelligible across organisations, systems and time.
Architecture to implementation
The framework remains stable — implementations stay bounded
ES Record applies EviState Core as persistent evidentiary infrastructure. ES Mail applies that foundation to communications and counterparties. Neither inherits claims the underlying evidence cannot support.
Explore the trust services →CompanyEviState
Common architectureAES
Infrastructure → implementationES RecordES Mail
Relationship with existing standards
Complementary by design
EviState Core is intended to work with relevant identity, signing, security, provenance, governance and sector standards—not replace them. A specific technical integration should only be claimed when it has been implemented and verified.
Existing controls+EviState Core evidentiary context→Inspectable relationship state
Architecture boundary
EviState Core does not decide who or what should be trusted
It establishes and exposes evidence around defined state. Organisations, regulators, platforms and people retain responsibility for the decisions they make using it.
EviState Core is not
×
A sovereign identity issuer or certification authority
×
A universal trust, truth or safety score
×
A substitute for legal or regulatory judgement
×
A guarantee that underlying conduct or content is legitimate
Public architecture statement. EviState Core is a proprietary evidentiary-state architecture being developed by EviState. This public overview explains its purpose, conceptual model and boundaries without disclosing confidential implementation methods.