Home Developers Evidence electrical.mosfet.tj

Public evidence

electrical.mosfet.tj

Machine-checked verification for calculation version 1.1.2 · tier internally_reviewed

CVP status

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance

Steady-state thermal; not transient Zth

Declared partition coverage
PASS · 3/3 declared partitions (ja, jc-ca, invalid-domain)
Versions
Calculation 1.1.2 · 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 9cb3923ce22d

Verification

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

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.1.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.1.2. CVP 1.0.0-proposed. 3/3 golden · 8/8 CVP boundary · 6/6 invalid · 5/5 property · 2/2 metamorphic · 1/1 cross-interface · 16/16 CVP contract. digest 9cb3923ce22d.

  • Golden (oracle-backed) 3 / 3
  • CVP boundary 8 / 8
  • Invalid input 6 / 6
  • Property 5 / 5
  • Metamorphic 2 / 2
  • Cross-interface 1 / 1
  • CVP contract 16 / 16
  • 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
  • schema rejects missing rth PASS
  • share url roundtrip ja PASS
  • share url roundtrip jc ca PASS
  • conflicting paths rejected PASS
  • schema rejects conflicting paths PASS
  • output schema enforces path consistency PASS
  • rest success payload validates schema PASS

Fingerprint sha256:d029c5d041be798f8d2b71dbf5075d29c629ca574dba7a49e0019d550e6e8b0e

Input schema sha256:bacbec2deaa82d91b5c2fcf2739bdc94f97e8b6f23cd8352b9b46d77394c1d2d · Output schema sha256:dcdbc531b378ec3e1fa5f3fe4540141378cdacfcff6b8f91e92f0d3ae5220ead · 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-tj
Engine
mosfet-tj
Engine build
2026-09-10
Evidence core
2026-09-05T02:35:39.217Z
Rendered
2026-11-10T05:18:41.741Z
Last reviewed
2026-08-16

Assumptions

  • Steady-state lumped thermal resistance
  • Rθ constant (not Zth(t))
  • RθJA is an effective / application value for the user's thermal environment, not a JEDEC-board package constant
  • JC+CA is a case/heatsink-dominant lumped single-path approximation; it does not model parallel heat-flow through PCB, leads, or package surfaces

Limitations

  • Steady-state only; not Zth or CFD
  • Rth_JA is effective/application RθJA for the user's PCB and cooling environment, not a universal JEDEC package constant
  • JC+CA is a case/heatsink-dominant lumped single-path approximation; it is not a universal equivalent of RθJA and ignores parallel PCB/package heat flow
  • Rth_JA and Rth_JC or Rth_CA together is schema-invalid and CONFLICTING_INPUTS

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.