VES 1.2 · Stewarded by Veriscopic

Verifiable evidence for consequential decisions.

VES is a published standard for preserving the evidence, authority, conditions, judgement and commitment behind consequential decisions, so they can be independently reviewed without reconstructing them later.

Valid evidence is not always sufficient decision evidence.

Evidence and governing decision inputs are linked by a VES Decision Envelope for later review, replay and verification.
EvidenceConditionsAuthoritySystemsJudgementCommitment
VES 1.2Decision EnvelopePortable links to native evidence
ReviewReplayVerify

The 60-second explanation

Preserve the decision, not just the activity.

A consequential decision is rarely contained in one system. VES links the material evidence into a portable point-in-time envelope without replacing the systems that produced it.

Different evidence answers different questions.

Runtime records can show what a system did. Governance evidence can show how an organisation is controlled. VES addresses a different question: what evidence, authority, conditions, judgement and commitment formed the decision at the moment the organisation acted?

VES is

  • A standard for preserving consequential decision evidence
  • A portable decision envelope
  • Applicable to human, rules, workflow and AI-assisted decisions
  • A way to verify a declared evidence package later

VES is not

  • A runtime-control receipt or gateway
  • An audit log or replacement for source systems
  • A governance maturity taxonomy
  • A certification that a decision was correct

Public model

The VES Decision Envelope

Nine public components establish what was decided, what applied, who or what contributed, and how the resulting package can be checked later.

01

Decision identity

The decision type, opaque subject reference, outcome and execution time.

02

Decision context

The material facts and source evidence considered in relation to the decision, with their declared relationship—for example, available, relied upon, excluded or superseded.

03

Governing conditions

The policy, wording, rules, requirements or instructions applicable at the time.

04

Business authority

The role, delegated authority, limits and approval state at execution.

05

System contribution

Rules, models, workflows or external systems that materially influenced the decision.

06

Human judgement

Review, intervention, approval, override or rationale where applicable.

07

Commitment

The organisational outcome, including financial, contractual or customer consequence.

08

Evidence integrity

References, hashes, signatures and declared provenance for Evidence Objects, where available.

09

Verification

The profile used, checks performed, result status and visible limitations.

Decision-Evidence Maturity

A progression from recollection to preserved state.

The levels describe evidence maturity. They are not certification grades and do not determine whether a decision was correct.

L1

Narrative

The decision is described after the fact.

L2

Documentary

Documents and artefacts are retained, but association or timing may be weak.

L3

Traceable

Source evidence, versions and attributable decision history are linked.

L4

Preserved Decision-State

A time-bound envelope preserves authority, conditions, human and system contribution, integrity data and a replay path.

Insurance applications

One evidence model across consequential workflows.

VES applies wherever an organisational commitment may later need to be understood, tested or replayed.

Claims

Preserve the basis of a settlement, referral or denial so later reviews do not begin with a forensic search.

Underwriting

Bind risk decisions to the evidence, authority and governing conditions in force at acceptance.

Delegated authority

Show which mandate, limit and approval state applied when an organisation committed.

Operational risk & assurance

Review consequential decisions through a consistent, portable evidence structure.

Reinsurance

Retain the decision evidence needed to examine coverage, authority and material conditions later.

Implementation-neutral by design

Start with the public schema and a worked claims referral.