electrical.amps_to_volts

Three distinct suites: educational examples on the calculator page, this legacy regression count (42/42 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.4.2 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.4.2. CVP 1.0.0-proposed. 7/7 golden · 18/18 CVP boundary · 18/18 invalid · 11/11 property · 2/2 metamorphic · 2/2 round-trip · 2/2 cross-interface · 38/38 CVP contract. digest 48f35e3a2921.

• Golden (oracle-backed) 7 / 7
• CVP boundary 18 / 18
• Invalid input 18 / 18
• Property 11 / 11
• Metamorphic 2 / 2
• Round-trip 2 / 2
• Cross-interface 2 / 2
• CVP contract 38 / 38
• Interfaces PASS · UI (SSR) / REST / MCP
• Interface claim ui-ssr is query-result HTML, not a live browser session.
• Assurance Engineering

• 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
• operation input oneof PASS
• output units include v and a PASS
• operation a v ohm schema valid PASS
• operation v a ohm schema valid PASS
• operation a v watt schema valid PASS
• operation v a watt schema valid PASS
• operation dc omits pf PASS
• operation dc rejects power factor PASS
• operation requires mode PASS
• operation ac requires power factor PASS
• operation a v ohm unit V PASS
• operation a v watt unit V PASS
• operation v a ohm unit A PASS
• operation v a watt unit A PASS
• output mode unit binding PASS
• operation result matches detail PASS
• operation formula matches system PASS
• versioned schema pin PASS
• versioned schema id PASS
• jsonld valid json PASS
• jsonld type webapplication PASS
• jsonld name match PASS
• jsonld canonical url PASS
• jsonld software version match PASS
• jsonld system semantics PASS
• jsonld offer free match PASS
• jsonld breadcrumb match PASS
• jsonld visible content match PASS
• rest success payload validates schema PASS

Fingerprint sha256:a3b8a170fa6175c42e55b30a618ec83f5936fd99193720bee8fc25c8252144cb

Input schema sha256:13f02e679f92360d7a2e0bd2cab9f2adb37b7e99488fdafbe821d198caf95f6b · Output schema sha256:d370c0ab19dd413a6bb72ef3b6593168cb1d174f439e77495b8b32a313dad36f · 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.

Tool

amps-to-volts

Engine

amps-volts

Engine build

2026-09-21

Evidence core

2026-09-21T09:47:31.791Z

Rendered

2026-11-10T05:18:41.685Z

Last reviewed

—

Assumptions

• Ohms path assumes resistive Ohm’s-law behavior.
• Watts DC matches P = V·I. Watts AC uses RMS and total power factor λ.
• Three-phase watts path assumes balanced line-to-line voltage.
• DC does not use power factor or phase. Canonical Agent schema forbids power_factor on DC; REST may send it and it is ignored with POWER_FACTOR_IGNORED.
• JSON Schema is a callable-input envelope (types, required fields, enums). Zeros and out-of-range PF may be schema-valid; the engine returns stable error codes.

Limitations

• Composite page: ohms path is V=IR; watts path is P/(I·PF) with optional √3
• Not for converting amps to volts from current alone
• JSON Schema is a callable-input envelope (types/required/enums). Zeros, negatives, and PF outside (0,1] may be schema-valid; the engine returns stable error codes
• DC payloads must omit power_factor. REST may still send PF on DC: ignored with POWER_FACTOR_IGNORED
• AC watts paths require power_factor in (0, 1]. UI initializes AC PF to 1.0; Agent/API clients must send it. Explicit PF=0 is POWER_FACTOR_OUT_OF_RANGE, not a silent 1
• P>0 with I=0 → CURRENT_MUST_BE_NONZERO; V≠0 with R=0 → RESISTANCE_MUST_BE_NONZERO; 0/0 → UNDEFINED
• IEEE-754 binary64; non-finite results → NON_FINITE_RESULT
• Not for unbalanced three-phase