Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

instrument implementation / implementation-contract

Beat Frequency Calculator implementation

A source-bound implementation contract for Beat Frequency Calculator; deployment and executable qualification remain separate.

Status: VERIFIED_CLEANLifecycle: 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-095
Effect
Computation or source lookup only

Input and validation requirements

Equal input frequencies produce a zero beat frequency, causing the period calculation 1/f_beat to divide by zero. Negative-frequency handling is also convention-dependent and can produce a materially different result if signed and unsigned interpretations are not distinguished.

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": {
    "f1": 440,
    "f2": 442,
    "unit": "Hz"
  },
  "expected_outputs": {
    "beat_frequency": 2,
    "beat_frequency_unit": "Hz",
    "period": 0.5,
    "period_unit": "s"
  },
  "working": "f_beat=|440−442|=|−2|=2 Hz. T_beat=1/f_beat=1/2=0.5 s."
}

Other records

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