VSO / Research resourcesOpen issues in the published specification
VCP v1.2 issues include RFC tree requirements versus an odd-node-duplication example, root-only AnchorRecord signatures and exact nanosecond representation. Text/schema differences and field placement also require clause-level review.
VAP alignment is under review; full conformance has not been established. Separate VCP release status, interpretations and known issues from proposed repairs and implementation-specific choices.
From proposals to bounded synthetic tests
- Integrity proposals and byte-contract candidate: candidate hash inputs and signature coverage with synthetic bytes and signatures.
- Numeric-field inventory and candidate representations: numeric-field units, ranges, representations and migration impacts.
- Native-layout and migration subset experiment: a closed subset for field placement, units, ISO time and original-to-derived evidence bindings.
Selected candidates are local test conditions. They neither replace current requirements and GA schemas nor provide a complete native-data migration tool.
Keep the declared experimental baseline
The layout experiment retains a historical source baseline and fingerprints of 204 files. Its instructions copy only the current experiment into a separate baseline checkout. Success is not a test of the newest specification as a changed baseline.
Preserve saved inputs, reports and original signed bytes. Write a fresh run to a separate output location, following the pinned README.
Errata triage is still a proposal
The “v1.2.1” name in Unadopted v1.2.1 errata scope triage is an unadopted scope discussion, not a release or effective repair. Changes to signed bytes or schema acceptance need separate classification, tests and migration review.
Internal synthetic success does not establish normative adoption, full conformance, independent reproduction or safe production migration.
Sources and reviewed revisions
This page summarizes public materials at pinned commits. Creating it is not a new research test run. Historical test records and fixed distributions remain unchanged.
- VCP release status, interpretations and known issues ·
vcp-spec@749b145 - Integrity proposals and byte-contract candidate ·
vcp-spec@749b145 - Numeric-field inventory and candidate representations ·
vcp-spec@749b145 - Native-layout and migration subset experiment ·
vcp-spec@749b145 - Unadopted v1.2.1 errata scope triage ·
vcp-spec@749b145