Domain profiles & cross-cutting capabilities

VAP is a meta-framework — never a protocol. Profiles bind the framework’s invariants to sector semantics and event vocabularies. Exactly one document in the family carries the Protocol designation: VCP.

Domain profiles

VCPv1.2 RC1

VeritasChain Protocol

Finance / algorithmic trading — the audit-standards profile for capital-markets AI. The only document in the family carrying the Protocol designation.

CAPv1.0 Released

Content / Creative AI Profile

A verifiable evidence layer for AI workflows involving content and intellectual property — ingestion, training, generation, transformation, export — for games, film, animation, publishing, and music.

CPPv1.4 Released

Capture Provenance Profile

Provenance for media captured by a device the operator controls (first-party capture). Sibling of OAP.

MAPv0.1.2 Working Draft

Medical AI Profile

Clinical and benefits workflows: AI outputs, human review, override, and sign-off records made tamper-evident and third-party inspectable.

OAPv0.1.1 Working Draft

Observed Artifact Provenance (VAP-WEB)

Records of third-party web resources observed at a URL — material published by someone else, preserved because it may later be disputed, deleted, edited, or denied.

PAPFragment v0.2 Draft

Public Administration Profile

Credit scoring, welfare determination, immigration, recruitment AI. The Investigative-Decision Vocabulary fragment (v0.2 draft) is the first published track.

Cross-cutting capabilities

Capabilities apply across profiles rather than to one sector.

DAPv0.1 Working Draft

Delegated Access Provenance (VAP-AGENT)

Cross-cutting capability for agentic AI systems acting under delegated authority — who delegated what scope to which agent, and what the agent did with it.

SMPv0.2.0 Working Draft

Self-Modification Provenance (VAP-SLEEP)

Cross-cutting capability for systems that modify themselves — records of self-directed change made attributable after the fact.

Registry: announced & planned

IAPAnnounced

Industry Accountability Profile

Sector-specific extensions and regulatory mappings layered on other profiles.

DVPPlanned

Driving Vehicle Protocol

Registry entry (planned).

AAPPlanned

Aviation AI Protocol

Registry entry (planned).

EIPPlanned

Energy Infrastructure Profile

Grid, water/telecom/gas control, nuclear monitoring; offline-anchoring semantics.

Statuses above reflect the current working state of each document, which can run ahead of the printed registry table in VAP v1.2 §4.5.2 (e.g., MAP is listed there as Planned; its working draft is v0.1.2). The registry is corrected at the next framework patch. Working drafts are published for technical discussion, not for production conformance claims.

How profiles relate

CPP vs OAP — the boundary is who controls the thing being recorded: CPP covers media produced by a device the operator holds; OAP covers a resource published by a third party at a URL. DAP applies whenever observation or action is performed by an autonomous agent under delegated authority, in any profile’s domain. Profiles released after VAP v1.2 target v1.2 at first release (VSO-VAP-CHANGE-001 Annex B.2).