Public evidence

electrical.diode.equation

Machine-checked verification for calculation version 1.1.0 · tier internally_reviewed

Open calculator API Capability Download JSON CVP Manifest MCP Review policy

CVP status

No series Rs / breakdown / recombination extras / high-injection. Is is specified at T, not computed from a reference-temperature value.

Declared partition coverage: PASS · 5/5 declared partitions (fwd-id, inv-vd, reverse-bias, small-x, invalid-domain)
Versions: Calculation 1.1.0 · CVP protocol 1.0.0-proposed · Evidence 2026-10-28.meta-metrics-v2
Verification revision: 2026-10-28.meta-metrics-v2 · 2/2 property · digest 89f3b93c0517

Verification

Legacy regression suite: 15/15 calculation tests · Production surface contract 6/6

Three distinct suites: educational examples on the calculator page, this legacy regression count (15/15 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. Verification revision 2026-10-28.meta-metrics-v2. Calculation version 1.1.0. CVP 1.0.0-proposed. 6/6 golden · 10/10 CVP boundary · 11/11 invalid · 2/2 property · 2/2 metamorphic · 8/8 round-trip · 4/4 cross-interface · 6/6 CVP contract. digest 89f3b93c0517.

Golden (oracle-backed) 6 / 6
CVP boundary 10 / 10
Invalid input 11 / 11
Property 2 / 2
Metamorphic 2 / 2
Round-trip 8 / 8
Cross-interface 4 / 4
CVP contract 6 / 6
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
schema output required declared PASS
schema valid input executes PASS
engine success output validates schema PASS
schema rejects incomplete input PASS
rest success payload validates schema PASS

Fingerprint sha256:fc82f7c2c6e183ced77f89b0b803cd01f2d9689ef4c4a3de8c82e173fa0599f3

Input schema sha256:0d09a1811597bcb8e9ac11e11c59ade2a938a949011800cf5c13af56be3d58d0 · Output schema sha256:765f987f71f4acf69f378cc438657d8325ff6a6ac883763d79d2a92110199837 · 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: diode-equation
Engine: diode-equation
Engine build: 2026-09-12
Evidence core: 2026-09-12T22:51:46.658Z
Rendered: 2026-11-10T05:18:41.759Z
Last reviewed: 2026-09-13

Assumptions

Ideal Shockley; no series Rs, breakdown, recombination extras, or high-injection
I_S is the saturation current at the selected junction temperature; I_S(T) is not derived

Limitations

Ideal Shockley; no Rs/breakdown/high-injection
Is is specified at T; Is(T) is not derived
mode=vd requires Id > -Is
binary64 overflow → NUMERIC_OVERFLOW

Sources

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

Shockley — The theory of p–n junctions in semiconductors and p–n junction transistors — Bell System Technical Journal 28(3), 1949 · 1949
Supports: Ideal exponential Id–Vd relationship of a p–n junction
CODATA 2022 — Boltzmann constant k — Fundamental Physical Constants
Supports: Vt = kT/q thermal voltage
CODATA 2022 — elementary charge e — Fundamental Physical Constants
Supports: Vt = kT/q thermal voltage

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.