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

instrument implementation / implementation-contract

DSP: Sample Rate & Nyquist Calculator implementation

A source-bound implementation contract for DSP: Sample Rate & Nyquist 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
t4-208
Effect
Computation or source lookup only

Input and validation requirements

The arithmetic formulas produce expected finite results, including at the exact Nyquist boundary and at the largest finite sample rate. However, the specification leaves the signed-frequency convention undefined, allowing the same input (-25000 Hz at a 48000 Hz sample rate) to produce either an aliasing warning or no warning. Input-domain validation for nonphysical or extreme values is also unspecified.

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": {
    "sample_rate_hz": 48000,
    "bit_depth_bits": 16,
    "signal_frequency_hz": 1000
  },
  "expected_outputs": {
    "nyquist_frequency_hz": 24000,
    "max_representable_frequency_hz": 24000,
    "aliasing_warning": false,
    "dynamic_range_db": 98.08
  },
  "working": "Nyquist = 48,000 / 2 = 24,000 Hz. Max representable frequency = 24,000 Hz. Signal comparison: 1,000 Hz > 24,000 Hz is false, so aliasing_warning = false. Dynamic range = 6.02 × 16 + 1.76 = 96.32 + 1.76 = 98.08 dB."
}

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-tranche4/tranche4-results.json