VSTD v0.2.0 — Universal Accelerator Accountability
Historical-coordinate notice (added 2026-08-27): This page records the tagged
repository releasev0.2.0; that semantic-version coordinate is not the current VSTD-2
layer. The accelerator surface described below is now named VSTD-3, while issued
receipts retain the frozenVSTD-3.0wire identifier. The tag and attached assets
remain unchanged. References below to the historicalconformanceworkflow name
identify a repository job, not an earned VSTD conformance result. See
the current identifier map.
VSTD 3: Universal Accelerator Accountability
VSTD v0.2.0 adds a normative, evidence-bounded standard and reference implementation for accelerator identity, firmware evidence, execution evidence, accounting continuity, complete-mediation claims within declared boundaries, fleet completeness, and provenance propagation.
Included
- VSTD 3.0 normative specification and strict JSON Schemas
- deterministic virtual accelerator and adversarial conformance suite
- 37-profile data-driven accelerator registry
- NVIDIA and AMD host-observed adapters with opaque attestation preservation
- strict provider-evidence boundaries for Google TPU, AWS Neuron, and Microsoft Maia
- continuity, reset anchoring, partition/topology, fleet, and provenance validation
vstd hardware,continuity,fleet,evidence, andclaimsCLI families- threat model, migration guide, vendor integration guide, references, and translated claim limits
Verification performed
- public checkout: 105 passed, 2 skipped
- internal full suite: 152 passed, 3 skipped
- Ruff and mypy passed
- source archive built twice byte-identically
- wheel built twice byte-identically using
SOURCE_DATE_EPOCH=1787270400 - clean wheel install and virtual accelerator receipt verification passed
- GitHub conformance and stdlib-smoke checks passed
Artifact digests
verifiable-standard-0.2.0.zip:b23b4e939109fc9c73d8044d59c4fd8a7cffd7c5d005494446f5d6ef078c169fverifiable_standard-0.2.0-py3-none-any.whl:8a06d78652f6cbf837b0deab57dc5fe085482523af090356202a128bc8c2c79e
Claim boundary in plain language
A VSTD receipt can support only the claims justified by its evidence, independent verification, declared conformance profile, and observation boundary. This release does not establish vendor endorsement, accredited certification, physical-world completeness, or universal observation of accelerator activity. HMAC evidence is test-only. Opaque vendor evidence remains unverified unless an independent verifier is configured. UNKNOWN, UNSUPPORTED, and FAIL remain distinct from PASS.
Licensed under Apache-2.0. Edited and published by Tyler Roost / TimeLordRaps.