VESVerifiable Evidence Standard
Version 1.2 Draft
VES 1.2 DraftLatest draft · 2026-09-20

VES 1.1 remains active and citable.

Version historyPermanent citation
Read VES 1.2

Implementation path

Build against the public exchange surface.

Start with the JSON Schemas and fictional test vectors. Preserve native evidence, pin versions, declare limitations and keep proprietary implementation choices outside the portable envelope.

Latest draftVES 1.2 DraftPublished:

For implementation review. VES 1.1 remains the current active, citable version until VES 1.2 is formally published.

View versions →

Public artefacts

VES Decision Envelope schemaJSON ↗External Evidence Object schemaJSON ↗Fictional Qualified claims-referral envelopeJSON ↗Fictional Qualified verification resultJSON ↗

Suggested implementation path

  1. Select and pin the applicable VES profile.
  2. Map existing decision identifiers, context, conditions, authority and commitment fields.
  3. Wrap native evidence with External Evidence Objects; do not rewrite source semantics.
  4. Generate a Decision Envelope at or immediately adjacent to organisational commitment.
  5. Retain integrity details, applicability periods, replay references and explicit limitations.
  6. Validate the exchange structure and publish the result status for the stated profile.

Implementation guidance

VES does not require a database, a particular cloud, a VES-hosted API or storage of raw insurance evidence on a public website.

Use opaque references where possible. Separate public exchange semantics from internal capture orchestration. Do not place personal or confidential claim content into public test vectors.

Roadmap, not current capability

A maintained conformance test suite, adapter interface and implementation registry may follow after public review. No broad adapter support, independent verification service or conformance programme is claimed in this draft.