VSO updates VAP-LAP references, VAP errata and SDK boundary checks
VSO has aligned its websites with three GitHub updates: discovery of the proposed Legal AI Profile, current VAP Draft 3 errata references, and the SDK’s synthetic boundary checks. These are distinct publication and first-party verification records.
First-party checks; proposals remain unadopted
Experimental extensions and proposed repairs remain unadopted. Independent third-party reproduction has not been established. Repository publication and successful CI do not establish full conformance, production suitability, certification or formal adoption.
1. VAP-LAP: a related proposed profile
The Legal AI Profile is described in the individual Internet-Draft draft-ailex-vap-legal-ai-provenance-05 (26 October 2026; profile v0.6.0; intended status: Experimental). It covers provenance for consultation, document drafting, fact-checking and professional human review. It is outside the formal VAP §4.5.2 profile registry and is neither an IETF standard nor a working-group-adopted document. AILEX is a product and use-case reference, not a conformance or certification claim. Appendix C of -05 reports no independently validated conforming implementation. VAP-LAP / AILEX →
2. Current VAP Draft 3 references, with history retained
The informative corrections dated 25 and 27 October clarify nanosecond resolution versus PTPv2 clock synchronization below 1 µs, Gold Prop/Institutional wording, the Payload.VCP-ANCHOR namespace and Internet-Draft revisions. The release status is “Specification GA”, not “Production Ready”. Draft 3 remains Draft 3; these corrections do not change normative requirements or establish formal adoption. The VAP site identifies the current text separately from the retained 24 October historical reference. VCP’s full conformance to VAP remains unestablished.
VAP Draft 3 · SHA-256:429ae7765438625adfb5ba66c380b4c2108de3c1be78e376422f25348346e415
3. SDK boundary checks: Python 306, TypeScript 140
SDK PR #2 adds documentation, shared synthetic vectors and tests; it changes no runtime code, API or release version. The 13 shared cases cover numeric interpretation (4), Merkle proofs (2), signature bytes (1) and AnchorRecords (6). Each language has 15 focused tests. In CI 40529498586, both the Python 3.10 and 3.13 jobs passed 306 Python tests, 140 TypeScript tests and the cross-language check. The same cases and repeated matrix jobs are not added together as independent evidence.
The checks expose the SDK’s current interpretation boundaries: exact integer handling is not adoption of RFC 8785; event signatures over ASCII hex differ from signatures over decoded 32-byte roots. A root signature can remain VALID after unsigned count or policy metadata changes while binding and the aggregate result are INVALID. Missing or unsupported external evidence remains INDETERMINATE; timestamp syntax alone does not authenticate time. Hand-derived expected bytes and hashes remain first-party evidence.
The 159-test Explorer notice remains available
The 27 October Explorer API/GUI notice is retained separately, including its 159 API tests, 26 GUI tests and unsigned, unanchored, API-disconnected synthetic-demo limits. SDK counts are not added to Explorer results. This website update does not alter current normative requirements, existing implementations, signed data, fixed distributions or K3. Explorer · 159 / 26 →