Source: https://guthlabs.ai/docs/instruments/unit-dimensional-analysis-converter/

instrument / verified-clean

# Unit & Dimensional Analysis Converter

The current ledger marks this instrument verified clean within the source-bound verification corpus.

Status: **VERIFIED_CLEAN**Lifecycle: **verified-clean**

## Inspectable records

[01**Overview**Purpose and lifecycle](<https://guthlabs.ai/docs/instruments/unit-dimensional-analysis-converter/>)[02**Mechanism**Method and assumptions](<https://guthlabs.ai/docs/instruments/unit-dimensional-analysis-converter/mechanism/>)[03**Implementation**Binding and validation](<https://guthlabs.ai/docs/instruments/unit-dimensional-analysis-converter/implementation/>)[04**Qualification**Evidence and errata](<https://guthlabs.ai/docs/instruments/unit-dimensional-analysis-converter/qualification/>)

## Ledger state

The current ledger marks this instrument verified clean within the source-bound verification corpus.

**Area**: Mathematics — arithmetic through advanced (algebra, matrices, calculus, sequences/series, number theory, combinatorics, graphing, complex numbers, geometry, logic, sets)

**Tranche**: tranche-6

**Evidence ID**: t6-142

**Ledger rows**: 1

No ledger note is attached.

## Review findings

The core algorithm is standard: multiplicative factors for units sharing a dimension, affine formulas for offset temperature scales, and exponent-vector tracking for dimensions. Verdict is NEEDS_REVIEW because the exact unit inventory, factor-table version/precision, dimensional-expression interface, and temperature-difference behavior are not specified.

### Formula and scope findings

- The stated linear/affine conversion method is standard, but the supported-unit lookup table, factor precision, and reference/version are unspecified, so exact reproducibility cannot be verified.

- Dimensional-consistency checking is claimed, but the input schema only defines a scalar value, source unit, and target unit; it does not define an expression grammar, compound-unit syntax, or how dimension exponents are supplied and reported.

- Temperature conversions must distinguish absolute temperatures from temperature differences: Celsius/Fahrenheit/Kelvin require affine offsets, while temperature intervals require multiplicative-only factors.

- The specification does not state whether compound units such as m/s^2, prefixes, reciprocal units, or derived SI units are supported.

### Unit assumptions

- Length conversion uses the exact SI definition 1 in = 0.0254 m.

- Mass conversion uses 1 kg = 2.20462262184878 lb; the pound is assumed to mean the avoirdupois international pound.

- Time conversion uses 1 h = 60 min.

- Absolute temperature conversion uses K = °C + 273.15; Kelvin and Celsius increments are assumed equal in size.

- Dimension exponents use SI base dimensions, with L for length, M for mass, T for time, and Θ for thermodynamic temperature.

## Boundary hardening

**BREAK_CLAIMED** · SELF_FLAGGED

An extreme but syntactically valid finite input, 1e308 m, converts to 1e311 mm and overflows JavaScript Number arithmetic to Infinity. The converter should reject or clearly flag the non-finite output. The pound test also exposes a convention-dependent result if lb is not disambiguated.

## Errata and corrections

No applied erratum is attached to this unique-name record.

## Inspectable example

4 review vectors are recorded. One source-bound sample is shown below.

````
{
  "inputs": {
    "value": 12,
    "source_unit": "in",
    "target_unit": "m"
  },
  "expected_outputs": {
    "converted_value": 0.3048,
    "dimension_breakdown": {
      "L": 1,
      "M": 0,
      "T": 0,
      "Theta": 0
    }
  },
  "working": "1. Use the exact factor: 1 in = 0.0254 m.\n2. Convert: 12 in × 0.0254 m/in = 0.3048 m.\n3. The inch and metre are both length units, so the dimension exponents are L^1 M^0 T^0 Θ^0."
}
````

## Related workflows

No source-defined multi-instrument workflow membership is recorded.

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `VERIFIED_LEDGER.json · VERIFIED_CLEAN`

- `evidence-tranche6/tranche6-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`