VSO announcements

VSO · · RESEARCH & SOURCE REVIEW

VSO updates VAP IETF references, interoperability guidance and the Commission incident record

VeritasChain Standards Organization (VSO) has reflected merged GitHub documentation and an incident source review in its website guidance. Document publication, other projects’ reported results, first-party CI and independent VAP reproduction remain distinct.

References to VAP Internet-Draft -03

Published on 15 November, draft-kamimura-vap-framework-03 explains the correspondence between three conceptual groups and the VSO specification’s five mandatory layers, and updates its VCP reference to -05. Its change history states that no framework requirement is added or changed.

This website update corrects references. It does not replace the VSO specification or adopt a normative change. The specification SHA-256 remains a35d5e082fd4b2f9921a78b1a71df263018320375e09fa18cf81533a18a19998. Dated preparation notes and their original references remain historical records.

IETF 127 review and external implementation guidance

The IETF 127 research note examines signed-object identification, receipts across logs, encodings, numbers and parser behavior. External experiment results are participants’ published reports, not VSO reruns or evidence of an external VAP implementation. Additions to the CHANGE-002 preparation register are unnumbered, unadopted questions.

The external implementation handoff explains how to retain separate contract, implementation and dataset commits, original input bytes, trust inputs, dependencies, expected results and observations. Unexecuted or unsupported checks and operational errors must not be reported as expected rejections. External maintainers’ runs and VSO checks remain separately attributable. The guidance does not add or change challenge acceptance criteria.

The published vap-interop-demo-v0.2.0 baseline (cbd4502) and later main snapshot (a9ee3a5) are distinct; the shared contract ID does not identify the exact revision. Explicit signature-input screening described in the fixed release’s known-issue notice is on main only, absent from the existing tag and source ZIP. The historical eight-vector result and later security runs remain separate.

European Commission record: official statements, reporting and analysis

This notice links to the existing V1119EUCOMMISSION source review. Its status is “verified, pending registration”; this is not a duplicate registration.

Official account: answering questions about a Politico report at the Commission’s 19 November briefing, the spokesperson acknowledged a campaign involving misuse of a publicly available AI tool and precautionary application shutdowns. This was an answer to press questions, not an initial announcement on the Commission’s own initiative.

Press reporting and unresolved points: reported disruption duration and affected systems are not treated as Commission-confirmed details. Attribution to ARTEX and fully autonomous operation remain unconfirmed. The qualified statement that no evidence had been detected, at that stage, of a breach affecting staff as a whole does not establish that no data was exposed.

VSO analysis: an attacker’s tool cannot be expected to supply VAP records. VAP is neither a general-purpose logging system nor an intrusion-prevention measure, and it cannot recover unrecorded actions. Defensive observations, authorization and verifiability of records need separate assessment.

Case record with official and press sources · Corrections and verification boundaries

Scope of first-party CI

The merged VAP PR #76 passed the interoperability demo and settings guard; the merged #77 passed its change-applicable settings guard. This does not mean every research suite was rerun for #77. CI also passed for the PR #250 reference correction. These are first-party checks, not independent reproduction of external results or adoption of a specification.

Fixed distributions and historical records preserved

Normative requirements, existing implementations, signed data, fixed tags and ZIPs, and K3 are unchanged. The SDK’s fixed-release 125-test record and latest-main 186-test record, and earlier interoperability and site-CI records remain revision-scoped history. This is not a new release or an announcement of established independent reproduction.

Fixed interop release / known issue · Fixed research kit

GitHub and public sources

Announcement archive Research and verification resources