Source: https://guthlabs.ai/docs/instruments/richter-moment-magnitude-seismic-energy/implementation/

instrument implementation / implementation-contract

# Richter/Moment Magnitude ↔ Seismic Energy implementation

A source-bound implementation contract for Richter/Moment Magnitude ↔ Seismic Energy; deployment and executable qualification remain separate.

Status: **VERIFIED_CLEAN**Lifecycle: **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**: t5-038

**Effect**: Computation or source lookup only

## Input and validation requirements

Zero joules is a valid-looking numeric input but makes the inverse logarithm undefined. The instrument must reject E = 0; returning a finite magnitude would be a failure.

## 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": {
    "magnitude": 5,
    "magnitude_type": "Mw"
  },
  "expected_outputs": {
    "energy_j": 1995262314968.879,
    "tnt_tonnes": 476.8791,
    "tnt_kilotonnnes": 0.4768791
  },
  "working": "log10(E) = 4.8 + 1.5*5.0 = 4.8 + 7.5 = 12.3. Therefore E = 10^12.3 = 1.9952623149688788e12 J. TNT tonnes = 1.9952623149688788e12 / 4.184e9 = 476.8791 tonnes. TNT kilotonnes = 476.8791 / 1000 = 0.4768791 kt."
}
````

## Other records

[01**Overview**](<https://guthlabs.ai/docs/instruments/richter-moment-magnitude-seismic-energy/>)[02**Mechanism**](<https://guthlabs.ai/docs/instruments/richter-moment-magnitude-seismic-energy/mechanism/>)[04**Qualification**](<https://guthlabs.ai/docs/instruments/richter-moment-magnitude-seismic-energy/qualification/>)

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `VERIFIED_LEDGER.json`

- `evidence-tranche5/tranche5-results.json`