electrical.voltage_drop

Three distinct suites: educational examples on the calculator page, this legacy regression count (38/38 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.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-09-11.schema-coverage-u. Calculation version 1.5.2. CVP 1.0.0-proposed. 4/4 golden · 11/11 CVP boundary · 10/10 invalid · 14/14 property · 4/4 metamorphic · 1/1 cross-interface · 6/6 CVP contract. digest e4ca53248b8b.

• Golden (oracle-backed) 4 / 4
• CVP boundary 11 / 11
• Invalid input 10 / 10
• Property 14 / 14
• Metamorphic 4 / 4
• Cross-interface 1 / 1
• 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 valid input executes PASS
• engine success output validates schema PASS
• schema rejects incomplete input PASS
• schema coverage requires u PASS
• schema rejects boundary unc k without u PASS

Fingerprint sha256:706e4bbf603a233a4f99d57b83a663ff4374263e7271a2bf3db58c58842133d3

Input schema sha256:3bfb5b8d5c9afbe1a91d8aeecdd27df18b533a1ffd75dd2f33b9b214e8fdd429 · Output schema sha256:4f13f3ba3869b287cbb38a6c062ea47c40fbd60156baf76d993ec648fb392075 · 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

voltage-drop

Engine

voltage-drop

Engine build

2026-09-12

Evidence core

2026-09-12T08:31:40.839Z

Rendered

2026-09-16T22:03:43.700Z

Last reviewed

—

Assumptions

• Constant resistance; temperature neglected.
• AC estimate assumes PF ≈ 1 and neglects conductor reactance.
• DC / resistive 1φ uses round-trip path; 3φ assumes balanced line-to-line drop.
• V_system for 3φ is line-to-line; V_load = V_system − V_drop on that same basis.
• User supplies an appropriate Ω/km for the conductor and conditions.
• When u_* are set, first-order GUM sensitivity with independent inputs (no ρ on this page).

Limitations

• Resistance-only estimate — AC reactance neglected; AC modes assume PF ≈ 1
• Not a substitute for code-compliant cable sizing or ampacity
• 3φ V_system is line-to-line; percent_drop and V_load use that same basis
• Zero I/length/R → 0 V (valid); negatives → VALUE_MUST_BE_NON_NEGATIVE
• mode must be dc or three (INVALID_MODE otherwise); REST/UI default dc if omitted
• V_system if set must be > 0 (VALUE_MUST_BE_POSITIVE); omit it to return volts only
• Optional u_* use GUM sensitivity only; empty u_* still returns { V_drop, R_one_way, P_loss, … } without uncertainty
• Engine tested, source checked, evidence published (L1). Named expert review is a higher assurance tier (L3), not required for engine-tested status. Not a code-compliance certification.