Frequently asked questions

Questions about VES

Clear boundaries are part of the standard. These answers distinguish evidence-package verification from governance, storage, certification and decision quality.

Current publicationVES 1.2Published:

Current, published and citable. VES 1.1 is superseded.

View versions →

Is VES an audit log?

No. Logs may be useful Evidence Objects, but VES preserves the wider decision-state: governing conditions, authority, system and human contribution, commitment and verification context.

Is AI required?

No. VES applies to human, rules, workflow and AI-assisted decisions. Its scope follows the consequence of the organisational decision, not the technology used.

Does VES replace runtime evidence standards?

No. Runtime-control receipts, model-gateway logs, signed action records and policy-enforcement records may form part of a VES Decision Envelope. They do not, by themselves, establish the full business decision-state unless linked to applicable evidence, business authority, human judgement and organisational commitment.

How does VES treat governance evidence?

Governance evidence may be represented as an Evidence Object, but it does not by itself establish the basis of a specific consequential decision.

Does a Verified result mean the decision was correct?

No. It means required checks for the stated evidence-package profile passed. It does not certify correctness, lawfulness, fairness or compliance.

Is VES a certification programme?

No. VES 1.2 publishes an exchange model, schemas, examples and status semantics. A conformance programme remains in development.

Why does portability matter?

Decisions are often reconstructed from fragmented systems long after the event. A portable envelope preserves declared relationships and applicability beyond one workflow.

Does VES store evidence?

No. The standard allows references or manifests and does not require raw insurance evidence to be placed in a VES-operated store.

Who stewards VES?

Veriscopic stewards the public standard, version history, schemas and governance process.