Source: https://guthlabs.ai/docs/instruments/suvat-kinematics-solver/implementation/

instrument implementation / implementation-contract

# SUVAT Kinematics Solver implementation

A source-bound implementation contract for SUVAT Kinematics Solver; 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**: live-source boundary

**Effect**: Computation or source lookup only

## Input and validation requirements

The solver can encounter an undefined 0/0 computation and an underdetermined solution when a = 0 and u = v. It can also produce two valid nonnegative time branches for the same supplied u, a, and s, so a unique output is impossible without a branch-selection rule. Additionally, interpreting s as distance instead of signed displacement changes the result from 16 m to 34 m.

## 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": {
    "u": 5,
    "a": 2,
    "t": 4,
    "units": "u in m/s; a in m/s^2; t in s"
  },
  "expected_outputs": {
    "v": 13,
    "s": 36,
    "units": "v in m/s; s in m"
  },
  "working": "v=u+at=5+(2)(4)=5+8=13 m/s. s=ut+½at²=(5)(4)+½(2)(4²)=20+1(16)=36 m."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/suvat-kinematics-solver/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/suvat-kinematics-solver/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/suvat-kinematics-solver/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/batch10-output.jsonl`