Earthquake Magnitude Comparison (energy ratio) mechanism

Model scope

The numerical formulas are correct under the stated assumptions, but the spec needs an explicit ΔM convention, magnitude-scale constraint, and scientifically accurate amplitude labeling before release.

• The formulas are standard only when both magnitudes use the same compatible magnitude scale and ΔM is explicitly defined as M1 − M2.
• The phrase "amplitude one quake releases" is scientifically incorrect: amplitude is a measured wave-motion quantity, not something released. Label the output as seismic-wave amplitude ratio.
• The input specification does not define which quake is the numerator/reference and therefore does not define the sign of ΔM or the direction of either ratio.

Units and conventions

• Magnitude values are dimensionless logarithmic quantities, not physical units.
• Both magnitudes are measured on the same magnitude scale or on scales for which these relations are valid; mixing Mw, ML, Ms, or other scales without conversion is not valid.
• Define ΔM = M1 − M2. The reported ratios are quake 1 divided by quake 2.
• Energy ratio 10^(1.5·ΔM) is an approximate empirical seismic-energy relation; it assumes comparable event definitions and does not provide absolute energy.
• Amplitude ratio 10^ΔM assumes comparable amplitude measurements and the same magnitude convention.

Inspectable vector

One of 4 source-bound review vectors:

{
  "inputs": {
    "magnitude_1": 6,
    "magnitude_2": 5
  },
  "expected_outputs": {
    "energy_ratio": 31.6227766017,
    "amplitude_ratio": 10
  },
  "working": "ΔM = 6.0 − 5.0 = 1.0. Energy ratio = 10^(1.5 × 1.0) = 10^1.5 = 31.6227766017. Amplitude ratio = 10^1.0 = 10.0."
}

Failure boundary

BREAK_CLAIMED · SELF_FLAGGED

At magnitude difference ΔM = 1000, both mathematical ratios exceed JavaScript's finite numeric range and evaluate to Infinity in plain JavaScript arithmetic. The instrument should detect and flag this overflow.

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-tranche5/tranche5-results.json
• BOUNDARY_HAZARD_CATALOG.json