Source: https://guthlabs.ai/docs/instruments/escape-velocity/implementation/

instrument implementation / implementation-contract

# Escape Velocity implementation

A source-bound implementation contract for Escape Velocity; 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-197

**Effect**: Computation or source lookup only

## Input and validation requirements

The specification does not define altitude units, sign convention, or required behavior for h<=-R. Inputs at h=-R produce division by zero, and inputs below that limit produce a negative square-root argument. The formula also has no actual physical branch, so domain handling must be implemented explicitly.

## 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": {
    "body": "Earth",
    "gravitational_parameter_m3_per_s2": 398600441800000,
    "radius_m": 6371000,
    "altitude_m": 0
  },
  "expected_outputs": {
    "escape_velocity_m_per_s": 11186.14
  },
  "working": "r = R + h = 6,371,000 + 0 = 6,371,000 m\nv = sqrt(2μ/r) = sqrt((2 × 398,600,441,800,000) / 6,371,000)\n= sqrt(7.972008836 × 10^14 / 6.371 × 10^6)\n= sqrt(1.251296317 × 10^8)\n= 11,186.14 m/s"
}
````

## Other records

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