Source: https://guthlabs.ai/docs/instruments/harris-benedict-bmr-legacy/implementation/

instrument implementation / implementation-contract

# Harris-Benedict BMR (legacy) implementation

A source-bound implementation contract for Harris-Benedict BMR (legacy); 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**: t2-026

**Effect**: Computation or source lookup only

## Input and validation requirements

An extreme but representable JavaScript input produces NaN through Infinity minus Infinity rather than a controlled rejection. The unit probe also shows that omitted units can change the estimate from 2317.120 to 1807.137855 kcal/day.

## 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": {
    "weight": 70,
    "weight_unit": "kg",
    "height": 175,
    "height_unit": "cm",
    "age": 30,
    "age_unit": "years",
    "sex": "male"
  },
  "expected_outputs": {
    "bmr_kcal_per_day": 1695.667
  },
  "working": "13.397×70 = 937.790; 4.799×175 = 839.825; 5.677×30 = 170.310; 88.362 + 937.790 = 1026.152; 1026.152 + 839.825 = 1865.977; 1865.977 − 170.310 = 1695.667 kcal/day."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/harris-benedict-bmr-legacy/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/harris-benedict-bmr-legacy/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/harris-benedict-bmr-legacy/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-tranche2/tranche2-results.json`