Calorimetry Calculator (q=mcΔT) 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-231

Effect

Computation or source lookup only

Input and validation requirements

The zero-mass solve-for-specific-heat case produces a zero denominator and must be rejected as undefined. The cooling example also exposes a sign-convention hazard that can reverse both solution and reaction heat if ΔT is treated as a magnitude instead of T_final - T_initial.

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": {
    "operation": "coffee_cup_heat_and_reaction_heat",
    "mass_g": 250,
    "specific_heat_J_per_g_C": 4.184,
    "delta_T_C": 5
  },
  "expected_outputs": {
    "q_solution_J": 5230,
    "q_solution_kJ": 5.23,
    "q_rxn_J": -5230,
    "q_rxn_kJ": -5.23
  },
  "working": "q_solution = m·c·ΔT = 250.0 g × 4.184 J/(g·°C) × 5.0 °C = 1046 J/°C × 5.0 °C = 5230 J = 5.23 kJ. Assuming negligible calorimeter heat capacity, q_rxn = -q_solution = -5230 J = -5.23 kJ."
}

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