Page actions
instrument mechanism / verified-clean
Unit Converter (electrical) mechanism
The inspectable method record for Unit Converter (electrical), kept separate from implementation and qualification.
Model scope
The claimed scope is ambiguous because it lists multiple electrical quantities but supplies only value, from-unit, and to-unit. The exact missing constraint is that source and destination units must have compatible dimensions; cross-quantity conversion requires additional physical relationships and inputs.
- "SI prefix scaling" is incomplete without an explicit prefix-to-factor mapping and the rule converted_value = input_value × factor(from-unit) ÷ factor(to-unit).
- Conversions are valid only between units of the same physical quantity; V cannot be converted to A, W, Ω, F, H, Hz, VA, or VAR without additional circuit or power-factor inputs.
- VA, W, and VAR must not be treated as interchangeable: VA is apparent power, W is real power, and VAR is reactive power, despite related dimensional scaling.
- The specification does not define whether unit symbols are case-sensitive or how prefixed forms such as kV, mA, MΩ, kVA, and kVAR are parsed.
Units and conventions
- The vectors assume SI decimal prefixes: m = 10^-3, k = 10^3, and an unprefixed unit = 1.
- Conversion is performed only between units representing the same physical quantity.
- Unit symbols are assumed to be case-sensitive: V, A, W, Ω, F, H, Hz, VA, and VAR are distinct tokens.
- The numerical value is dimensionless before applying the source and destination unit scale factors.
Inspectable vector
One of 4 source-bound review vectors:
{
"inputs": {
"value": 3.3,
"from_unit": "kV",
"to_unit": "V"
},
"expected_outputs": {
"converted_value": 3300
},
"working": "kV factor = 1000; V factor = 1. converted_value = 3.3 × 1000 ÷ 1 = 3300 V."
}Failure boundary
BREAK_CLAIMED · SELF_FLAGGED
The extreme conversion 10^308 W to nW requires 10^317 nW, which overflows standard JavaScript Number arithmetic to Infinity. The converter should reject, flag overflow, or use arbitrary-precision handling.
Other records
Sources and evidence
These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.
VERIFIED_LEDGER.jsonevidence-tranche4/tranche4-results.jsonBOUNDARY_HAZARD_CATALOG.json