Storage Unit Converter 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

t4-028

Effect

Computation or source lookup only

Input and validation requirements

An extreme finite input overflows plain JavaScript arithmetic to Infinity, and negative storage values require an explicit policy because signed arithmetic returns -2 while a physical storage converter should reject them.

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": {
    "value": 5,
    "source_unit": "GB",
    "target_unit": "GiB"
  },
  "expected_outputs": {
    "converted_value": 4.656612873077393,
    "converted_unit": "GiB",
    "canonical_bytes": 5000000000
  },
  "working": "1 GB = 1000^3 bytes = 1,000,000,000 bytes. 5 GB = 5 × 1,000,000,000 = 5,000,000,000 bytes. 1 GiB = 1024^3 = 1,073,741,824 bytes. Target value = 5,000,000,000 ÷ 1,073,741,824 = 4.656612873077393 GiB."
}

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