VES Public Schema (v1.0)

The Veriscopic Evidence Standard (VES) defines normative requirements for preserving evidence of judgement, context, and responsibility as they existed at a specific point in time.

This schema describes what evidence objects are and what they mean. It intentionally does not define cryptographic algorithms or verification procedures.

Core integrity statement

Evidence objects

1) Evidence Record

The atomic unit in VES. An Evidence Record fixes a discrete governance artefact in time (e.g. a consent event, a decision entry, an approval, an assessment, or an acknowledgement).

Required fields

• ves_id — globally unique identifier for the record.
• record_type — the class of record (see Record Types).
• subject — plain-language description of what the record concerns.
• organisation — the legal entity the record is issued under.
• timestamp_created (UTC) — the time the record was fixed.
• evidence_scope — explicit statement of what this record evidences and what it does not.
• immutability_status — immutable | superseded | withdrawn (see Immutability).

Optional fields (recommended where available)

• decision_roles[] — roles involved (role-based, not necessarily named individuals).
• inputs_available[] — documents, data sources, assumptions available at the time.
• known_unknowns[] — declared uncertainties or missing information at the time.
• linked_records[] — references to other VES IDs forming an evidence chain.

2) Evidence Chain

A structured set of linked Evidence Records describing how governance judgement emerged over time. Chains support sequence integrity without rewriting history.

Typical chains include: consent → assessment → decision → approval → implementation note → supersession.

3) Integrity Declaration

A statement attached to an export describing the verification posture and limits. It enables reviewers to rely on integrity and non-tampering without relying on the platform.

Record types

VES v1.0 recognises the following record types:

• consent — a recorded reliance event (e.g. consent relied upon under defined terms).
• decision — a judgement exercised (what was decided, by whom, when, and on what basis).
• assessment — a recorded evaluation step (risk, impact, suitability), without asserting outcomes.
• approval — an authorisation event (sign-off), role-bound.
• policy — a governance artefact describing intent or requirement, version-bound.
• override — an exception or departure from a standard path, recorded explicitly.
• acknowledgement — a recorded receipt or acknowledgement (e.g. disclosure accepted).

Immutability semantics

Immutable

Immutable records cannot be edited. They remain verifiable indefinitely.

Superseded (with reference)

Supersession records do not rewrite the past. They create a new record that references the prior record and explains what changed (and why).

Withdrawn (with reason + reference)

Withdrawal indicates a record should no longer be relied upon as representative, while preserving the fact it existed and was fixed in time.

What this schema is not

• It is not a compliance framework or certification scheme.
• It does not assign risk ratings or outcomes.
• It does not determine liability, coverage, or legal sufficiency.
• It does not replace professional judgement.

Further reading

• VES overview
• VES v1.0 specification (verification mechanics)
• How to cite VES
• VES for insurers

This page is intended to be citeable in board papers, underwriting files, audit reports, and review memos as a description of VES evidence object semantics.