Luminosity from Radius & Temperature 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-041

Effect

Computation or source lookup only

Input and validation requirements

The extreme-magnitude vector produces Infinity in ordinary JavaScript arithmetic because T⁴ overflows binary64, and the specification provides no stated overflow handling or input validation. A secondary hazard is unit ambiguity because the formula requires metres and Kelvin but the input schema does not specify units.

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": {
    "radius_m": 695700000,
    "effective_temperature_K": 5772
  },
  "expected_outputs": {
    "luminosity_W": 3.82799e+26,
    "luminosity_L_sun": 0.999996
  },
  "working": "R² = (6.957×10^8 m)² = 4.8399849×10^17 m². T² = 5772² = 33,315,984 K², so T⁴ = 33,315,984² = 1.10995479×10^15 K⁴. 4πR²σ = 12.566370614 × 4.8399849×10^17 × 5.670374419×10^-8 = 3.448776×10^11 W K^-4. L = 3.448776×10^11 × 1.10995479×10^15 = 3.82799×10^26 W. L/L_sun = 3.82799×10^26 / 3.828×10^26 = 0.999996."
}

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