Source: https://guthlabs.ai/docs/instruments/inductor-energy-calculator/mechanism/

instrument mechanism / verified-clean

# Inductor Energy Calculator mechanism

The inspectable method record for Inductor Energy Calculator, kept separate from implementation and qualification.

Status: **VERIFIED_CLEAN**Lifecycle: **verified-clean**

## Model scope

The stated formula is standard and correct. NEEDS_REVIEW is required because the spec names inputs only as L and I without defining their units or conversion behavior. The blank honest_label should be supplemented with an SI-unit requirement such as 'Enter L in H and I in A; result in J.'

- The formula E = ½LI² is correct for energy stored in an ideal inductor, but the input units are unspecified. E is in joules only when L is entered in henries and I in amperes.

## Units and conventions

- L must be inductance in henries (H), or converted to H before calculation.

- I must be current in amperes (A); its sign does not affect the result because it is squared.

- E is returned in joules (J).

## Inspectable vector

One of 4 source-bound review vectors:

````
{
  "inputs": {
    "L": 0.002,
    "L_unit": "H",
    "I": 4,
    "I_unit": "A"
  },
  "expected_outputs": {
    "E": 0.016,
    "E_unit": "J"
  },
  "working": "E = ½LI² = ½ × 0.002 × 4² = 0.5 × 0.002 × 16 = 0.001 × 16 = 0.016 J"
}
````

## Failure boundary

**BREAK_CLAIMED** · SELF_FLAGGED

Extreme finite inputs overflow ordinary JavaScript numeric arithmetic to Infinity instead of producing a finite result or an explicit range error. The unit probe also exposes a potentially severe 1000-fold error if the mH prefix is not normalized; the formula itself has no genuine regime switch.

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/inductor-energy-calculator/>)[03**Implementation**](<https://guthlabs.ai/docs/instruments/inductor-energy-calculator/implementation/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/inductor-energy-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-tranche5/tranche5-results.json`

- `BOUNDARY_HAZARD_CATALOG.json`