Source: https://guthlabs.ai/docs/instruments/pump-affinity-laws-calculator/implementation/

instrument implementation / implementation-contract

# Pump Affinity Laws Calculator implementation

A source-bound implementation contract for Pump Affinity Laws 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-262

**Effect**: Computation or source lookup only

## Input and validation requirements

A zero baseline speed makes the required speed ratio undefined and must be rejected. The specification also leaves the speed-versus-diameter and ratio-direction conventions implicit, allowing materially different outputs if the ratio is interpreted reciprocally.

## 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": {
    "Q1": 100,
    "Q_unit": "m3/h",
    "H1": 40,
    "H_unit": "m",
    "P1": 10,
    "P_unit": "kW",
    "N1": 1750,
    "N2": 2100,
    "speed_unit": "rpm",
    "ratio_type": "speed"
  },
  "expected_outputs": {
    "Q2": 120,
    "H2": 57.6,
    "P2": 17.28
  },
  "working": "N2/N1 = 2100/1750 = 1.2. Q2 = 100 x 1.2 = 120 m3/h. H2 = 40 x (1.2)^2 = 40 x 1.44 = 57.6 m. P2 = 10 x (1.2)^3 = 10 x 1.728 = 17.28 kW."
}
````

## Other records

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