Protocol states
Initialized, Enrolled, Operational, Synchronizing, Recovering, Suspended and Archived states make execution transitions explicit.
QVTM / Protocol
A protocol for verifiable trust continuity.
QVTM defines how continuity-relevant change becomes immutable evidence, how that evidence is packaged and synchronized, and how continuity is evaluated while application authorization remains separate.
Continuity topologyQVTM
Evidence correlation fabric
Existing trust controls remain in place. QVTM connects their continuity-relevant evidence across time.
Evidence correlation fabricQVTM
Protocol operations
Enrollment, Authentication, Synchronization, Recovery, Trust Evaluation and Version Negotiation have defined observable contracts.
Continuity Evidence + CEP
Evidence is immutable; CEPs preserve and transport it without changing the meaning of the underlying history.
Synchronization
Evidence can be reconciled without destructive state replication, including after disconnected operation.
Recovery
Successful recovery extends continuity history instead of silently restarting it.
Deployment profiles
Profiles may select cryptography, transport, encoding and policy constraints, but may not redefine core protocol semantics.
Architectural comparison
Different controls answer different trust questions.
Technology / architecturePrimary questionWhat QVTM adds
Zero TrustShould this subject access this resource now?Evidence-backed continuity across changes behind successive access contexts.
PKI / Verifiable CredentialsCan this identity or claim be verified?Continuity across renewal, recovery, authority succession and related system change.
PQCCan cryptography resist the target quantum threat model?Continuity semantics across classical, hybrid and post-quantum migration.
Transparency / append-only logsWas an event or artifact recorded in a tamper-evident history?Cross-domain evidence packaging, correlation and continuity evaluation.
QVTMDid an established trust relationship remain verifiably coherent through change?Protocol semantics for evidence, CEPs, synchronization, recovery and Trust Evaluation.
QVTM is complementary: it does not replace authentication, authorization, PKI, transparency systems, cryptographic algorithms or domain policy.
Formal properties
QVTM is specified beyond prose.
The public Formal Foundations define the continuity graph, observable protocol state, transition system, synchronization and recovery models, plus invariants including evidence immutability, append-only evidence, CEP preservation, failure containment and cryptographic independence.
The Protocol Specification defines externally observable behavior; the SDK Reference maps that model into public integration contracts.
Read the formal and normative documents →