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

instrument implementation / implementation-contract

Op-Amp Bandwidth / Gain-Bandwidth Product Checker implementation

A source-bound implementation contract for Op-Amp Bandwidth / Gain-Bandwidth Product Checker; 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-257
Effect
Computation or source lookup only

Input and validation requirements

The formula is undefined when desired gain is zero, so the instrument must reject Av = 0 or explicitly report an undefined result. The specification also does not define a formula branch, a feasibility-warning threshold, or whether gain should be signed or treated by magnitude.

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": {
    "gbw": 1,
    "gbw_unit": "MHz",
    "desired_gain": 10
  },
  "expected_outputs": {
    "achievable_bandwidth": 100000,
    "bandwidth_unit": "Hz",
    "feasibility_warning": "Cannot be determined: no target bandwidth or feasibility criteria were supplied."
  },
  "working": "1 MHz = 1,000,000 Hz. BW = GBW / Av = 1,000,000 Hz / 10 = 100,000 Hz."
}

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