CODATA Physical Constants Reference implementation

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

t6-134

Effect

Computation or source lookup only

Input and validation requirements

The principal hazards are ambiguity and boundary handling: an empty query may be mishandled as an invalid zero-length operation, an extreme selector may be coerced instead of rejected, and the query e can return the wrong sign if elementary charge and signed electron charge are not explicitly distinguished. The CODATA-year branch also produces different alpha values and must not be silently mixed.

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": {
    "search": "speed of light in vacuum",
    "constant_symbol": "c",
    "catalog_year": 2022
  },
  "expected_outputs": {
    "value": "299792458",
    "unit": "m s^-1",
    "symbol": "c",
    "uncertainty": "0 (exact)",
    "codata_year": 2022
  },
  "working": "1. Search the catalog for the canonical name 'speed of light in vacuum'. 2. Select symbol c and CODATA 2022. 3. Return the tabulated exact SI-defined value: c = 299792458 m s^-1. 4. Because the value is exact by definition, uncertainty = 0."
}

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