Source: https://guthlabs.ai/docs/instruments/wave-speed-wavelength-frequency-calculator/mechanism/

instrument mechanism / verified-clean

# Wave Speed / Wavelength / Frequency Calculator mechanism

The inspectable method record for Wave Speed / Wavelength / Frequency Calculator, kept separate from implementation and qualification.

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

## Model scope

The formulas are standard, but verdict is NEEDS_REVIEW because the spec leaves units, zero/negative-input behavior, and the applicability assumptions of the string formula ambiguous.

No additional formula finding is recorded.

## Units and conventions

- For v=fλ, use v in m/s, f in Hz (s^-1), and λ in meters; units must be mutually consistent.

- For v=√(T/μ), use tension T in newtons and linear density μ in kg/m; the result is in m/s.

- The string formula assumes an ideal, flexible, uniform, taut string with negligible bending stiffness and appropriate non-dispersive behavior.

- Wavelength inputs such as nanometers must be converted to meters before applying the formula.

## Inspectable vector

One of 4 source-bound review vectors:

````
{
  "inputs": {
    "f_Hz": 2.5,
    "lambda_m": 0.8
  },
  "expected_outputs": {
    "v_m_per_s": 2
  },
  "working": "v=fλ\nv=(2.5 s^-1)(0.8 m)\nv=2.0 m/s"
}
````

## Failure boundary

**BREAK_CLAIMED** · SELF_FLAGGED

The string-wave formula divides by zero when linear density is zero, and negative frequency exposes an unresolved signed-versus-magnitude convention. The input-schema branch also requires explicit mode selection.

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/wave-speed-wavelength-frequency-calculator/>)[03**Implementation**](<https://guthlabs.ai/docs/instruments/wave-speed-wavelength-frequency-calculator/implementation/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/wave-speed-wavelength-frequency-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`