VAP / VCP — specifications and research tools for verifiable records
"Verify, Don't Trust" — Encoding Trust in the Algorithmic Age

🌐 Website • 🔍 Explorer • 📋 Specification • ⚡ Quick Start • Assessment information

These are separate statuses; publication is not independent validation or certification.

The September 2026 implementation disclosure reports zero external implementations and zero Evidence Packs accepted in proceedings. Correction — 24 October 2026: the earlier commercial contract figure has not been substantiated by reconciliation with primary records and is withdrawn from current public claims pending review. This does not establish a count of zero. See the dated correction. Commercial service activity is separate from external implementations, independent validation and accepted Evidence Packs.

Integrity review — 24 October 2026: VCP v1.1/v1.2 alignment with VAP v1.2 is under review; full conformance has not been established. The technical-errata and normative-change drafts are unadopted proposals, not an issued repair or a production-validation result.

Download the fixed research kit and preserved execution evidence. The distribution preserves the tested ZIP, SHA-256 checksums, complete internal CI outputs and workflow logs separately from the specification release series. It evaluates submitted evidence and a synthetic mock gate / OS-isolation experiment. It does not modify current VAP v1.2, the existing verifier, gate, OS experiment or K3.

The internal record reports 27 package tests plus 138 existing regression tests, and matching results for 16 OS, 15 gate and 14 verifier cases. These are internal checks, not an independent reproduction, a certified product, or a claim that all real-world actions are observed or blocked. Use the fixed English instructions or 日本語手順.

VAP-LAP proposes a domain profile for legal AI workflows, including consultation, document drafting, fact checking and human review. The published proposal is draft-ailex-vap-legal-ai-provenance-05 (26 October 2026; profile version 0.6.0).

Registry boundary: VAP-LAP is the proposal's label, not a registered VSO profile designation. LAP is outside the complete profile registry in VAP v1.2 §4.5.2. “Proposed” describes this related work; it is not a status in that registry. Listing this proposal neither registers it nor changes the registry's status vocabulary.

Explore the English overview, 日本語 or 中文, and the proposal overview on GitHub. AILEX is introduced as a product and use-case reference for legal practice workflows. The overview explains the proposed profile's registration and implementation status; product availability does not establish conformance.

Tokachi Kamimura is the representative of both AILEX LLC and VeritasChain Co., Ltd., which operates VSO. The LAP -05 editor lists AILEX LLC / VSO as the affiliation. AILEX has a commercial interest in this product reference; it is not evidence of adoption by an independent third party. This listing does not establish LAP/VAP conformance, certification or an independently validated implementation.

日本語: 上村十勝は、AILEX合同会社と、VSOを運営するVeritasChain株式会社の双方の代表です。 LAP -05編集者の所属はAILEX LLC / VSOと記載されています。 AILEXはこの製品紹介について商業上の利害を持ち、独立した第三者の採用例には当たりません。 掲載はLAP/VAPへの適合、認証、独立検証済み実装を示すものではありません。

中文: 上村十勝同时担任AILEX LLC及运营VSO的VeritasChain株式会社的代表。 LAP -05编辑者将所属列为AILEX LLC / VSO。AILEX对本产品参考具有商业利益， 因此不将本介绍作为独立第三方采用的证据，也不表示LAP/VAP符合性、认证或独立实现验证。

Kamimura, T. (2025).
Hybrid Post-Quantum Signatures for Tamper-Evident Audit Trails:
Formal Security Analysis and Design Trade-offs.
Zenodo. https://zenodo.org/records/17920524

This paper presents a research-oriented cryptographic design and formal security analysis;
it is not a finalized protocol specification.

The following five VSO individual Internet-Drafts are active in the IETF Datatracker (checked 2026-10-25). None has been adopted by an IETF Working Group.

Individual submissions are works in progress. They are not RFCs or IETF-endorsed standards and have no formal standing in the IETF standards process.

The canonical (normative) specification of VeritasChain Protocol (VCP) is maintained in the following repository and directory structure:

vcp-spec/
 └─ spec/
    ├─ v1.2/   (current specification, GA)
    ├─ v1.1/   (legacy)
    └─ v1.0/   (legacy)

The v1.2 GA specification snapshot is fixed by tag v1.2.0 at the validated correction commit b23acb2. The tag does not target the earlier GA cutover PR #1 merge. See the canonical repository for later editorial corrections and known issues.

All other formats (HTML, PDF, translations) are non-normative.

A vendor-neutral benchmark for evaluating the auditability and evidence quality of AI and algorithmic decision systems.

• Designed for audit, assurance, and compliance teams
• 10 criteria / 20-point evaluation scale
• Includes published regulatory mappings; these do not establish legal compliance

Canonical reference (released v1.0):
https://github.com/veritaschain/vcp-spec/tree/main/benchmark

Theoretical foundation (preprint):
Why Open Cryptographic Standards Matter for AI Auditability
https://zenodo.org/records/17947483

VeritasChain Protocol (VCP) is an open specification for tamper-evident, cryptographically verifiable audit trails in algorithmic and AI-driven trading systems. It is the finance profile of VAP.

Given the required evidence, trusted keys and anchoring assumptions, a third party can check alterations to recorded evidence and omissions relative to an anchored, committed set. Valid signatures do not establish that every real-world action was observed, that a record is factually true, or that the action was authorized. VAP itself does not prevent AI misconduct or recover actions that were never recorded.

An evaluator may receive records without enough evidence to check their integrity, ordering or relationship to a committed set. The design goal is to make those checks explicit, including the conditions under which evidence is insufficient.

VCP defines record structures and verification requirements, including:

As checked on 2026-10-22 (JST), the public npm registry returned 404 for @veritaschain/sdk, and PyPI returned 404 for veritaschain. These names are not currently verified public VSO SDK releases. Do not install packages under these names based on older examples; availability alone would not establish VSO ownership or authenticity.

The PyPI package vcp-sdk belongs to Value Context Protocol, a separate project. It is not a substitute for the VeritasChain Protocol (VCP) SDK.

For producing and verifying VCP v1.2 events offline, use vcp-sdk (unreleased development source; package metadata 0.1.0; first-party), installed from its GitHub repository; its README lists what it does and does not check, and a VALID result from it is not a conformance claim. For historical VCP v1.1 interface guidance, see the archived SDK interface materials or the Python reference implementation. For the Explorer API, follow its local setup and implementation status. Official installation instructions will be added after package publication and publisher verification.

Consult the assessment program information, policies and CAB registry for current published information. No launch date is asserted here. The current VAP repository disclosure explains that the listed CAB, VeritasChain Co., Ltd., operates VSO and is not independent of the scheme owner. Specification publication, reference code and internal research tests do not establish independent certification.

VCP tier requirements belong to the canonical VCP specification. Regulatory mappings are explanatory material, not regulator endorsement or a guarantee of compliance.

We welcome contributions from the community!

• 🐛 Issues: Report bugs or request features
• 💬 Discussions: Ask questions, share ideas
• 🔧 Pull Requests: Contribute code or docs

See CONTRIBUTING.md for guidelines.

VeritasChain Standards Organization (VSO)
Maintainer of VAP and VeritasChain Protocol (VCP)

© 2025-2026 VeritasChain Standards Organization (VSO).