Home Developers Evidence electrical.swg_to_mm

Public evidence

electrical.swg_to_mm

Machine-checked verification for calculation version 1.3.1 · tier engine_tested

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance

Discrete gauges 7/0 (−6)…50 only

Declared partition coverage
PASS · 8/8 declared partitions (heavy-gauge, zero-alias, ordinary-gauge, endpoints, field-mm, field-mm2, invalid-type, invalid-range)
Versions
Calculation 1.3.1 · CVP protocol 1.0.0-proposed · Evidence 2026-10-28.meta-metrics-v2
Verification revision
2026-10-28.meta-metrics-v2 · 3/3 property · digest 03c18b9f6ed6

Verification

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

Three distinct suites: educational examples on the calculator page, this legacy regression count (76/76 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.3.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.3.1. CVP 1.0.0-proposed. 62/62 golden · 7/7 CVP boundary · 13/13 invalid · 3/3 property · 2/2 metamorphic · 4/4 cross-interface · 6/6 CVP contract. digest 03c18b9f6ed6.

  • Golden (oracle-backed) 62 / 62
  • CVP boundary 7 / 7
  • Invalid input 13 / 13
  • Property 3 / 3
  • Metamorphic 2 / 2
  • 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. Error-path engine·REST·MCP 1/1 (status, code, calculation_version). SSR compared on URL-canonical requested calculations; empty query is idle (not an error) and JSON-typed object/array inputs are REST/MCP-only.
  • 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:6681584e7bcf14adc599b12fb4de1ab3655d15c60d532bfe5b5a75e7060b4209

Input schema sha256:86262535bd5cf3d7af1106f20ae6d1ee4c4e3e4b01dc827e8f6a5b202b8e5b7c · Output schema sha256:e6a848b5ea8b44c3868034828fca95d72270e291ca16e3e92bdfb8284f7b808a · 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
swg-to-mm
Engine
swg
Engine build
2026-09-10
Evidence core
2026-09-10T22:48:17.762Z
Rendered
2026-11-10T05:18:41.709Z
Last reviewed
—

Assumptions

  • Canonical size is the Imperial SWG inch table (7/0–50). millimetre = inch × 25.4 (exact).
  • Area uses that millimetre, not a rounded display value.
  • Area assumes a solid circular cross-section of that diameter.
  • For tube/sheet use-cases, interpret d as wall/sheet thickness.
  • SWG 0 and 1/0 share the tabulated 0.324 in size used here; some catalogues list 1/0 separately.

Limitations

  • Lookup table only for integer SWG 7/0 (−6) through 50
  • Out-of-range → SWG_OUT_OF_RANGE (not 0 mm)
  • Non-integer → SWG_NOT_INTEGER (not Math.round)
  • Canonical diameter is inch; mm = inch × 25.4 (exact); area uses that mm
  • SWG ≠ AWG; same number different diameter

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.