VSO announcements

VSO · · RESEARCH & MAINTENANCE

VSO reports change-evidence research and verifier repairs — SDK main and fixed release remain separate

On 20 November 2026, VSO summarizes four merged research and maintenance updates. VeraSnap Verify SDK’s original 125-test release record is preserved alongside the later 186-test main revision. The separate VCP SDK MQL5 compilation and self-test remain unfinished.

VAP: binding evidence for AI-assisted changes

VAP #75 adds an informative proposal and local experiment binding seven synthetic artifacts: finding, patch, target baseline, environment, test plan, test results and approval conditions. Integrity, authorization, test evidence, conditions, mock execution, health and rollback evidence are assessed separately.

The recorded internal checks cover 26 new tests, 46 existing gate tests, 17 matching scenario expectations and offline rechecking of all 17 exports. Post-merge Python 3.12/3.14 CI succeeded. The backend only writes a mock record; it does not deploy a patch or execute the supplied test plan.

An explicit negative control reaches the lower-level gate without the companion policy. Matching this expected bypass demonstrates a limitation, not non-bypassable enforcement. Keys, clocks and services remain under one harness operator; independent observation and external anchoring are not established.

vap-spec #75

VeraSnap Verify SDK: 125-test release versus 186-test main

#1 prevents repeat device-key enrollment from overwriting original enrollment and revocation history. #3 enforces Android enrollment issuer CA authorization, key usage and path-length constraints, rejecting malformed or unsupported paths. The separate Apple/TSA helper has not thereby become a complete general-purpose PKIX verifier.

Both repairs are on main and absent from the fixed v0.1.0 tag.Both revisions still identify the package as 0.1.0, so record the source commit, not just the version label. The counts below belong to separate revisions and are not additive.

verasnap-verify-sdk #1 · verasnap-verify-sdk #2 · verasnap-verify-sdk #3

VeraSnap Verify SDK revision records
RevisionFirst-party test recordRepair scope
Fixed v0.1.0 tag
0caa054
125 at releaseOriginal release; neither #1 nor #3 included.
Source after #1
5b19884
131Repeat enrollment preserves enrollment/revocation history.
Main inspected on 20 November
4eaa3b7
186Also enforces Android certificate-path constraints.

The latest main revision passed 186 tests on each of Python 3.10, 3.12 and 3.13 in first-party CI. The 18 November article and its original 125-test record are unchanged. This is neither a replaced tag nor a newly published release.

Fixed release v0.1.0 · Original 125-test release article

CAP-SRP and VCP: false-pass prevention and evidence preservation

CAP-SRP #6 restores supported PyNaCl selection and applies shared input checks before both signature backends. Synthetic data reproduced and repaired acceptance of weak keys/signatures; the full recorded suite passed 412 tests. This is local PoC policy, not a normative CAP/VAP amendment or a complete prime-subgroup membership test.

VCP #33/#36 address duplicate JSON keys, invalid numbers, validation bypasses and custom-schema input exceptions. Invalid files are reported individually while later files are still checked. The latest contract/CLI suite passed 22 tests; this does not add signature verification or establish complete VCP conformance.

Supervision Node PoC #8 rejects ambiguous JSON and protects existing input/output files. The full recorded suite has 177 passes and three existing skips. Skipped external TSA, blockchain and network checks are not counted as successes.

cap-srp #6 · vcp-spec #33 · vcp-spec #36 · vcp-supervision-node-poc #8

VeraCheck: unchecked evidence no longer appears fully verified

Site #242/#245 render imported metadata as literal text and stop empty, unrelated or unsupported input from receiving an overall success or Gold conformance indication. Conformance is always “Not assessed”; analytics is excluded. The public viewer already contains these repairs.

A supported individual signature matching an embedded key does not establish trust in that key or authenticity/completeness of the whole pack. The viewer does not provide full CPP schema, Merkle, timestamp, device-identity or conformance verification.

vcp-site #242 · vcp-site #245

VeraCheck

Unfinished: VCP SDK MQL5 compilation and terminal self-test

This concerns VCP SDK, a different repository from VeraSnap Verify SDK. The MQL5 run on current main a81806d was cancelled during setup. Remedial PR #20 remains unmerged; its run stopped before installer execution because the official download no longer matched the pinned digest. Download/signature checks are distinct from actual compilation and terminal self-test. Those latter results remain unverified; “all CI passed” or “MQL5 complete” would be inaccurate.

MQL5 main · cancelled · PR #20 · open · PR MQL5 · failure

Post-merge CI for the referenced revisions

These are first-party GitHub Actions records. Synthetic scenarios, test methods, Python/OS configurations and workflow counts are different units. Checks for this article’s publication, served hashes and layout are recorded separately from the research and implementation tests.

Fixed distributions and historical records remain intact

This site update does not change normative requirements, schemas, existing implementations, signed data, fixed tags/ZIPs or K3. Main-only repairs and known issues in the fixed VAP interop ZIP remain distinct. Earlier 125-test, 159-test and 110-image-comparison records retain their original revision and verification scope.

Fixed interop release / known issue · Fixed research kit

VeritasChain Co., Ltd., which operates VSO, develops VeraSnap and this SDK. This is a first-party research and maintenance report, not an independent audit, product endorsement or certification.

Pull requests and primary records

Announcements archive