This page explains VitalCV’s evidence and signing architecture. It is not a clinician record and does not represent a completed credentialing decision.
The state rows below are an architectural illustration of the trust-state grammar (example run ids and timestamps), not live source-check results. For a human-readable overview, see the Trust Center. The machine-readable register is served at /.well-known/trust-register.
Trust State Register
Institutional trust surface for VitalCV credential verification
Clinician-provided, not verified
Derived from verified data
Checked against authoritative source
Cryptographically signed by issuer
Exploratory view — no ownership attribution, no lineage, no replay. All slots are unbound.
Attributed to vcv-system. Lineage is visible; replay is tracked. Source checks applied.
Cryptographic plane. Issuer-signed (ES256), T4-capable — the signed-receipt grammar shown as an example, not a live artifact.
did:web:vitalcv.com/.well-known/did.json · did:web:vitalcv.com
machine-readable: /.well-known/trust-register
Trust Doctrine
Infrastructure Continuity
Verifier Guarantees
Live Operational Status
Independently verifiable. No auth required.
Machine-Readable Endpoints
| Endpoint | Description | Auth |
|---|---|---|
| /.well-known/jwks.json | Public signing keys | None |
| /.well-known/did.json | W3C DID document | None |
| /.well-known/openid-credential-issuer | OID4VCI metadata | None |
| /.well-known/trust.json | Trust manifest | None |
| /.well-known/trust-register | Machine-readable doctrine | None |
| /trust/graph | Verifier-readable trust graph | None |
| /trust/schema | Trust graph schema reference | None |
| /trust/doctrine | Replay contract doctrine | None |
| /api/receipts/verify | Verify a receipt JWT | None |