Source: https://guthlabs.ai/docs/instruments/wien-s-law-peak-wavelength/implementation/

instrument implementation / implementation-contract

# Wien's Law Peak Wavelength implementation

A source-bound implementation contract for Wien's Law Peak Wavelength; deployment and executable qualification remain separate.

Status: **VERIFIED_CLEAN**Lifecycle: **implementation-contract**

## Binding contract

This record describes what an executable surface must bind and validate. It does not claim that a public calculator, package, or production route is deployed.

**Record owner**: Guth Instruments

**Lifecycle**: verified-clean

**Evidence ID**: t4-053

**Effect**: Computation or source lookup only

## Input and validation requirements

Unspecified domain and unit handling produce undefined results at 0 K, overflow at extremely small positive temperatures, a rejected negative-temperature branch, and radically different results when 0 is interpreted as Celsius versus Kelvin.

## Required corrections

No binding erratum is attached to this unique-name record. Implementers must still preserve the declared units, domain, and failure behavior.

## Inspectable interface fixture

The sample below is evidence for interface and validation tests, not a production implementation.

````
{
  "inputs": {
    "temperature": 0,
    "temperature_unit": "°C"
  },
  "expected_outputs": {
    "peak_wavelength_m": 0.000010609555,
    "peak_wavelength_um": 10.609555,
    "peak_wavelength_nm": 10609.555
  },
  "working": "Convert to kelvins: T = 0 + 273.15 = 273.15 K. λ_max = 2.898e-3 m·K / 273.15 K = 1.0609555e-5 m. Convert: 1.0609555e-5 m × 1e6 = 10.609555 μm; 1.0609555e-5 m × 1e9 = 10609.555 nm."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/wien-s-law-peak-wavelength/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/wien-s-law-peak-wavelength/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/wien-s-law-peak-wavelength/qualification/>)

## Sources and evidence

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

- `VERIFIED_LEDGER.json`

- `evidence-tranche4/tranche4-results.json`
