Home Developers Evidence units.rf.dbm_watts

Public evidence

units.rf.dbm_watts

Machine-checked verification for calculation version 1.3.1 · tier internally_reviewed

Open calculator API Capability Download JSON CVP Manifest MCP Review policy

CVP: CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance· RF power unit conversion (dBm ↔ W and dBm ↔ mW). Not a dBW / dBµV converter. · Protocol · Schema · Production report

Declared partition coverage
PASS · 5/5 declared partitions (dbm-w, w-dbm, dbm-mw, mw-dbm, invalid-domain)
Versions
Calculation 1.3.1 · CVP protocol 1.0.0-proposed · Evidence 2026-09-13.overflow-ssr-rollout
Verification revision
2026-09-13.overflow-ssr-rollout · 2/2 property · digest 250f2cc95400

Verification

Legacy regression suite: 22/22 calculation tests · Production surface contract 4/4

Three distinct suites: educational examples on the calculator page, this legacy regression count (22/22 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-09-13.overflow-ssr-rollout. Calculation version 1.3.1. CVP 1.0.0-proposed. 6/6 golden · 8/8 CVP boundary · 14/14 invalid · 2/2 property · 4/4 metamorphic · 4/4 round-trip · 10/10 cross-interface · 4/4 CVP contract. digest 250f2cc95400.

  • Golden (oracle-backed) 6 / 6
  • CVP boundary 8 / 8
  • Invalid input 14 / 14
  • Property 2 / 2
  • Metamorphic 4 / 4
  • Round-trip 4 / 4
  • Cross-interface 10 / 10
  • CVP contract 4 / 4
  • Interfaces PASS · UI (SSR) / REST / MCP
  • Interface claim ui-ssr is query-result HTML, not a live browser session. Error-path engine·REST·MCP 5/5 (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. Public share URLs use UI alias `a` plus `mode`. Canonical Agent/API field is `value`; mode defaults to dbm-w.
  • Assurance Engineering
  • release artifacts aligned PASS
  • schema valid input executes PASS
  • engine success output validates schema PASS
  • schema rejects incomplete input PASS

Fingerprint sha256:70149db348a403e63c9b97ad4beab414c61eaf2afd8f6a75b247bc1cd5c5ca9c

Input schema sha256:5c5082367485b8e59088bb08713c44d492dd090fe1de3b0106d7d9e0f24a0864 · Output schema sha256:70209a1ef3a4b1bd56a1e3ccd63ca6fd22bbbe5c4076cda21fff1bade4645a74 · 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
dbm-watt
Engine
dbm-watt
Engine build
2026-09-13
Evidence core
2026-09-13T01:52:28.084Z
Rendered
2026-09-16T22:03:43.730Z
Last reviewed
2026-09-13

Limitations

  • W/mW must be >0 for reverse log
  • Hard INVALID_MODE
  • IEEE-754 binary64 overflow → NUMERIC_OVERFLOW
  • IEEE-754 binary64 underflow to 0 → NUMERIC_UNDERFLOW

Sources

Standards and references supporting this tool specification. Methods are listed separately — they are algorithms, not bibliographic sources.

Legacy published checks

Golden and boundary cases from the legacy Evidence JSON. CVP property, metamorphic, round-trip, O3, and interface statuses/checks are recorded in the Manifest — including SKIP when a suite has no vectors.

IDKindStatusDetail
30dbmgoldenpassExpected 1 · Actual 1
0dbmgoldenpassExpected 0.001 · Actual 0.001
13dbmgoldenpassExpected 0.0199526231496888 · Actual 0.0199526231496888
neg30dbmgoldenpassExpected 0.000001 · Actual 0.000001
3dbm-mwgoldenpassExpected 1.9952623149688795 · Actual 1.9952623149688795
1mw-dbmgoldenpassExpected 0 · Actual 0
w-badboundarypassExpected VALUE_MUST_BE_POSITIVE · Actual VALUE_MUST_BE_POSITIVE
mw-badboundarypassExpected VALUE_MUST_BE_POSITIVE · Actual VALUE_MUST_BE_POSITIVE
bad-modeboundarypassExpected INVALID_MODE · Actual INVALID_MODE
roundtripgoldenpassExpected 30 · Actual 30
missingboundarypassExpected MISSING_REQUIRED_INPUT · Actual MISSING_REQUIRED_INPUT
0p023wgoldenpassExpected 13.617278360175927 · Actual 13.617278360175927
neg174dbmgoldenpassExpected 3.981071705534986e-21 · Actual 3.981071705534986e-21
mw-negboundarypassExpected VALUE_MUST_BE_POSITIVE · Actual VALUE_MUST_BE_POSITIVE
overflowboundarypassExpected NUMERIC_OVERFLOW · Actual NUMERIC_OVERFLOW
underflowboundarypassExpected NUMERIC_UNDERFLOW · Actual NUMERIC_UNDERFLOW
property-0dbm-1mwpropertypass0 dBm = 1 mW
property-neg30dbm-1uwpropertypass−30 dBm = 1 µW
property-plus10db-times-10propertypassP(dBm+10)=10 P(dBm)
property-mw-is-1000-wpropertypassP_mW = 1000 P_W
property-roundtrip-13dbmpropertypassdBm→W→dBm
property-roundtrip-3dbm-mwpropertypassdBm→mW→dBm