Source: https://guthlabs.ai/docs/instruments/motor-torque-power-speed-converter/implementation/

instrument implementation / implementation-contract

# Motor Torque/Power/Speed Converter implementation

A source-bound implementation contract for Motor Torque/Power/Speed Converter; 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-090

**Effect**: Computation or source lookup only

## Input and validation requirements

The reverse calculation of torque is undefined when power is nonzero and speed is exactly zero; the instrument should reject that input rather than produce a numeric result. A separate convention hazard also produces opposite power signs for signed versus magnitude-only speed.

## 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": {
    "torque_Nm": 20,
    "speed_rpm": 1500
  },
  "expected_outputs": {
    "power_W": 3141.592654,
    "power_kW": 3.141592654,
    "power_mechanical_hp": 4.211250206
  },
  "working": "ω=2πN/60=2π(1500)/60=50π rad/s. P=Tω=20(50π)=1000π W=3141.592654 W=3.141592654 kW. HP=P/746=3141.592654/746=4.211250206 hp."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/motor-torque-power-speed-converter/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/motor-torque-power-speed-converter/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/motor-torque-power-speed-converter/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`