Source: https://guthlabs.ai/docs/instruments/induction-motor-slip-speed-calculator/implementation/

instrument implementation / implementation-contract

# Induction Motor Slip & Speed Calculator implementation

A source-bound implementation contract for Induction Motor Slip & Speed Calculator; 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-078

**Effect**: Computation or source lookup only

## Input and validation requirements

A zero pole count produces division by zero in the synchronous-speed formula, so the calculator must reject that input. The specification does not state validation behavior, creating a potential undefined, Infinity, or NaN result.

## 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": {
    "frequency_Hz": 50,
    "pole_count": 4,
    "rotor_speed_rpm": 1440
  },
  "expected_outputs": {
    "Ns_rpm": 1500,
    "slip_percent": 4,
    "rotor_frequency_Hz": 2
  },
  "working": "Ns = 120×50÷4 = 6000÷4 = 1500 rpm. Slip fraction = (1500−1440)÷1500 = 60÷1500 = 0.04. Slip percent = 0.04×100 = 4%. Rotor frequency = 0.04×50 = 2 Hz."
}
````

## Other records

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