Home Developers Evidence electrical.mosfet.switching_loss

Public evidence

electrical.mosfet.switching_loss

Machine-checked verification for calculation version 1.0.0 · tier internally_reviewed

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance

Hard-switching approximation — soft-switching / Coss / Qrr excluded here

Declared partition coverage
PASS · 3/3 declared partitions (overlap-only, with-gate, invalid-domain)
Versions
Calculation 1.0.0 · CVP protocol 1.0.0-proposed · Evidence 2026-10-28.meta-metrics-v2
Verification revision
2026-10-28.meta-metrics-v2 · 5/5 property · digest 63609c269766

Verification

Legacy regression suite: 13/13 calculation tests · Production surface contract 13/13

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

  • Golden (oracle-backed) 2 / 2
  • CVP boundary 6 / 6
  • Invalid input 6 / 6
  • Property 5 / 5
  • Metamorphic 2 / 2
  • Cross-interface 1 / 1
  • CVP contract 13 / 13
  • 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
  • share url roundtrip si PASS
  • share url qg overlap heading PASS
  • unit hydrate ns khz nc PASS
  • rest success payload validates schema PASS

Fingerprint sha256:81d79dfa33e0dfffd963aff7c6d865c435d7232fa86a12ad9442a63d99ca6cc9

Input schema sha256:691a1017c9dc2931d1dc3d0dbb6d5b5323d77bedf81a182526d195503eb741b2 · Output schema sha256:5fb55f7eccfcd2870897ca921972e8b1212bea9ab915f39863c854ff1812c67e · 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
mosfet-switching-loss
Engine
mosfet-switching-loss
Engine build
2026-09-10
Evidence core
2026-09-05T02:35:39.217Z
Rendered
2026-11-10T05:18:41.727Z
Last reviewed
2026-08-16

Assumptions

  • Linear V/I transition; neglects Coss/Qoss and diode recovery.
  • tr/tf are effective overlap times at the operating point.
  • P_gate is gate-drive power shared among driver, Rg, and Rg,int — not MOSFET junction dissipation.
  • Qg is total gate charge at approximately the entered Vdrive, not an unscaled datasheet Qg at a different VGS.

Limitations

  • Hard-switching linear transition only — not soft-switching or Eon/Eoff tables
  • Qg and Vdrive must both be present or both omitted (else NEEDS_TWO_INPUTS)
  • Conduction loss is a separate capability
  • P_gate is gate-drive power — not necessarily dissipated entirely in the MOSFET junction

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.