Home Developers Evidence electrical.adc.snr

Public evidence

electrical.adc.snr

Machine-checked verification for calculation version 1.1.0 · tier internally_reviewed

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance

Ideal quantization model — excludes aperture jitter, thermal noise, distortion

Declared partition coverage
PASS · 4/4 declared partitions (snr, enob, invalid-domain, round-trip)
Versions
Calculation 1.1.0 · CVP protocol 1.0.0-proposed
CVP identity
3/3 property · digest ea962986abea

Verification

Legacy regression suite: 17/17 calculation tests · Production surface contract 18/18

Three distinct suites: educational examples on the calculator page, this legacy regression count (17/17 golden + boundary), and the CVP verification suite below. They are not the same number. Property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the CVP Manifest . SKIP (0/0) means that suite has no published vectors.

    This calculator CURRENT · Public schema 1.1.0 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

CVP verification suite

Protocol checks from the Evidence Manifest. Distinct from the legacy regression suite above. Calculation version 1.1.0. CVP 1.0.0-proposed. 4/4 golden · 7/7 CVP boundary · 6/6 invalid · 3/3 property · 4/4 metamorphic · 3/3 round-trip · 2/2 cross-interface · 16/16 CVP contract. digest ea962986abea.

  • Golden (oracle-backed) 4 / 4
  • CVP boundary 7 / 7
  • Invalid input 6 / 6
  • Property 3 / 3
  • Metamorphic 4 / 4
  • Round-trip 3 / 3
  • Cross-interface 2 / 2
  • CVP contract 16 / 16
  • Interfaces PASS · UI (SSR) / REST / MCP
  • Interface claim ui-ssr is query-result HTML, not a live browser session.
  • Assurance Engineering
  • release artifacts aligned PASS
  • contract page version PASS
  • contract capability version PASS
  • contract input schema version PASS
  • contract output schema version PASS
  • evidence version matches manifest PASS
  • schema output required declared PASS
  • schema valid input executes PASS
  • engine success output validates schema PASS
  • schema rejects incomplete input PASS
  • runtime input validates against schema PASS
  • runtime output validates against schema PASS
  • evidence cases conform to schema PASS
  • page spec matches capability PASS
  • catalog description matches capability PASS
  • category card matches capability PASS
  • search index metadata matches capability PASS
  • rest success payload validates schema PASS

Fingerprint sha256:9a2cde6e26a1e45df72c18f01846f2cec7938ef4597156697fc766d2c5f61f74

Input schema sha256:6269973fa3522ebfe4b11be9526bce77048aafeb7b500d01e52ead0c88e57f65 · Output schema sha256:7e002ad78e61c7c7a8c40fbe97fa039d0f14faf782a6b6619039518e3cc13bd0 · Build-time SHA-256 digests prove published artifacts agree with each other (release_integrity.scope=workspace). Production attestation GETs canonical URLs twice (public/cached view and origin), including Capability HTML, via npm run attest:production --write (published at /.well-known/calculatorx-production-attestation.json) and fails if the public Capability page advertises a different calculation_version. This is artifact consistency, not an independent immutable release log.

Build & scope

Engine identity and declared limitations.

Tool
adc-snr
Engine
adc-snr
Engine build
2026-09-10
Evidence core
2026-09-05T02:35:39.217Z
Rendered
2026-11-10T05:18:41.760Z
Last reviewed
2026-09-04

Assumptions

  • Full-scale sinusoidal input
  • Ideal ADC quantizer; quantization noise is uniformly distributed
  • No aperture jitter, thermal/reference noise, or harmonic distortion in the ideal-SNR path
  • Standard ENOB is derived from SINAD (noise + distortion), not SNR
  • n_bits is the ADC nominal integer resolution, not an effective-bits result

Limitations

  • Ideal quantization only. ENOB from measured SINAD, not SNR.

Sources

Standards and references supporting this tool specification. Methods are listed separately — they are algorithms, not bibliographic sources.

Verification disclosure

Aggregate outcomes, scope and artifact commitments are public. Complete test inputs, expected values, execution records and oracle infrastructure are retained privately. This summary does not independently reproduce the full verification run.