Public evidence

electrical.ohms_law

Machine-checked verification for calculation version 1.5.1 · tier internally_reviewed

Open calculator API Capability Download JSON CVP Manifest MCP Review policy

CVP status

Resistive DC identities; SI only

Declared partition coverage: PASS · 4/4 declared partitions (pair-vi, pair-vr, with-power, invalid-domain)
Versions: Calculation 1.5.1 · CVP protocol 1.0.0-proposed · Evidence 2026-10-28.meta-metrics-v2
Verification revision: 2026-10-28.meta-metrics-v2 · 6/6 property · digest 32686ded381b

Verification

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

Three distinct suites: educational examples on the calculator page, this legacy regression count (18/18 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.5.1 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.5.1. CVP 1.0.0-proposed. 4/4 golden · 4/4 CVP boundary · 4/4 invalid · 6/6 property · 2/2 metamorphic · 1/1 cross-interface · 5/5 CVP contract. digest 32686ded381b.

Golden (oracle-backed) 4 / 4
CVP boundary 4 / 4
Invalid input 4 / 4
Property 6 / 6
Metamorphic 2 / 2
Cross-interface 1 / 1
CVP contract 5 / 5
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
rest success payload validates schema PASS

Fingerprint sha256:845486e8afd4bb526b648e0d4fb60c21d595aff586d2719d8c5d545cf700b1d3

Input schema sha256:a57a0030ddac026cdbc3f5ac8722a6df635bee154adbb29c68e19f2897e79b20 · Output schema sha256:796c868957dd0501e42d16a60ad1c67434f36023b0560cf2b0ff77222988f4e9 · 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: ohms-law
Engine: ohms-law
Engine build: 2026-09-17
Evidence core: 2026-09-17T23:14:49.080Z
Rendered: 2026-11-10T05:18:41.663Z
Last reviewed: 2026-08-08

Assumptions

Ohmic (constant) resistance
Resistive power P = V × I

Limitations

Resistive model only
Not for reactive impedance networks
Fewer than two inputs → NEEDS_TWO_INPUTS; non-finite → INVALID_NUMBER
Zero divisors yield 0 for dependents (soft boundary)

Sources

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

Georg Simon Ohm (1827) — Foundational V ∝ I relationship for ohmic conductors
Supports: V = I × R
NIST Guide to the SI (SP 811) — Volt, ampere, ohm, and watt as coherent SI units
Supports: V, A, Ω, W base relationships
IEC 60050 — International Electrotechnical Vocabulary — Resistance (IEV 131-12-04)
Supports: R = u/I for a resistive two-terminal element; rearranges to u = R·I (Ohm’s law for ohmic conductors). Coherent SI unit ohm (Ω).
IEC 60050 — International Electrotechnical Vocabulary — Active power (IEV 131-11-42)
Supports: P is active power; unit watt (W). For ohmic DC, P = u·I.
BIPM SI Brochure (9th edition, version 4.01) — SI units for volt, ampere, ohm, and watt · 2026-06 · DOI
Supports: V, A, Ω, W coherent unit relationships

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.