The instrument
A Voltry certificate is a replayable statement about one specific GPU, bound to an identity whose strength is stated on the face. Evidence class, assurance, coverage, gaps, and Not Assessed outcomes remain visible; no Voltry surface states or implies asset value.
This page is a presentation study, not a current issuance. The current field-exercised path is C0/A0; higher assurance, functional coverage, continuous coverage, and VGR-1 grading remain separately statused in the VCM-1 maturity matrix. Read the governing draft and download the source material.
Certificate specimen
The visual below contrasts a transcription of the field-exercised C0/A0 state with a higher-level face that is explicitly marked specified only. The tamper control is a visual explanation of signature and ledger failure, not a live certificate-verification result.
A visual specimen only. No commercial certificate is represented.
Certificate of Record · VCM-1 visual study
FIELD EXEMPLAR
NVIDIA A10 · 24GB · reconstructed history
Captured 2026-08-08 · single point-in-time attempt · C0 / A0
Certificate of Record · VCM-1 visual study
NO COMMERCIAL ARTIFACT
Higher-assurance record · not issued · specified architecture
No field artifact · no commercial exercise · SPECIFIED ONLY
Anatomy
The order is fixed. Deterministic facts appear first, followed by modeled content and provenance. No single composite score replaces them.
Authenticity, firmware and VBIOS, functional burn-in, the silent-data-corruption functional test, and data sanitization. Each appraisal reads Pass, Fail, or Not Assessed under its stated evidence and coverage prerequisites.
Device facts retain their measured class; rates and distances computed over them are derived. Seven named axes remain visible, and no Voltry surface renders a weighted or compensatory composite.
A statistical estimate, where present, carries stated uncertainty and a calibration snapshot. It renders in a separate decision-inert block and never enters a grade, axis, or covenant status.
Assurance, coverage, record tier, history basis, gaps, version stamps, and exposure status remain distinct. A0 is operational identity, not hardware authenticity; C0 establishes only the scan moment.
Worked examples
VCM-1 separates operational maturity from normative architecture. The field program routinely produces C0/A0 bundles; no external counterparty holds a commercial certificate yet. Higher assurance, functional coverage, and continuous coverage cannot be inferred from the design.
A point-in-time, read-only NVIDIA capture signed under a software key. It provides operational visibility and cumulative counters as of the attempt, not hardware authenticity or interval coverage.
Coverage class C0 · scan moment only
A1 adds challenge-fresh GPU-bound attestation; A2 adds platform state; A3 adds an independent witness. C1 adds a governed drained-unit session; C2 adds an acknowledged, gap-accounted chain.
Maturity specified / in development
Tiers
A tier summarizes the depth and continuity of the record, never hardware quality or trust. Bronze is computed from the record alone. Silver and Gold are policy-qualified and are not comparable across policies.
The condition grade is a different indicator. VGR-1 is still in ratification, so no surface renders a letter grade until the rubric publishes. Once published, the grade is the minimum across required gradable axes - a gate, not an average - and missing required evidence produces UNGRADED.