Source: https://guthlabs.ai/docs/instruments/force-on-a-current-carrying-wire-in-a-field/implementation/

instrument implementation / implementation-contract

# Force on a Current-Carrying Wire in a Field implementation

A source-bound implementation contract for Force on a Current-Carrying Wire in a Field; 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**: t5-209

**Effect**: Computation or source lookup only

## Input and validation requirements

The extreme-magnitude vector overflows ordinary IEEE-754 plain arithmetic: the mathematically finite representation 1×10^924 N becomes Infinity. The instrument should detect and flag this rather than silently returning an unbounded numeric 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": {
    "I_A": 5,
    "L_m": 0.4,
    "B_T": 0.3,
    "theta_deg": 90
  },
  "expected_outputs": {
    "F_total_N": 0.6,
    "F_per_length_N_per_m": 1.5
  },
  "working": "sin(90°)=1. F_total = BILsinθ = 0.3×5×0.4×1 = 0.3×2 = 0.6 N. F_per_length = F_total/L = 0.6/0.4 = 1.5 N/m; equivalently IBsinθ = 0.3×5×1 = 1.5 N/m."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/force-on-a-current-carrying-wire-in-a-field/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/force-on-a-current-carrying-wire-in-a-field/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/force-on-a-current-carrying-wire-in-a-field/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-tranche5/tranche5-results.json`