THE FOLD / GRIND / THE CRON JOB / THE LEAP SMEAR
THE LEAP SMEAR
monotonic and correct were always separable
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
A leap second repeats a timestamp, and repeated timestamps break anything that treats time as an identifier. So you refuse to insert it: you make the whole day very slightly longer instead.
LIT verified live. One second spread across 86,400 is a rate change of 11.574 ppm. Across 2,000 samples of the smeared clock there are 0 non-monotonic readings and 0 duplicate timestamps, and the total drift applied over the window is exactly 1 second — not approximately. The leap second is fully absorbed and never once appears.
LIT verified live. One second spread across 86,400 is a rate change of 11.574 ppm. Across 2,000 samples of the smeared clock there are 0 non-monotonic readings and 0 duplicate timestamps, and the total drift applied over the window is exactly 1 second — not approximately. The leap second is fully absorbed and never once appears.
2 HOW IT WAS WEAVED · AI + HUMAN
Google published leap smearing in 2011 after a leap second took down parts of its fleet; AWS and others followed, and the smear windows are deliberately incompatible between providers.
AVAN (AI) checked the two properties that matter separately: that no timestamp repeats, and that the total correction is exactly one second. Either alone is easy. A smear that loses 11 microseconds is monotonic and wrong; one that is exact but steps at the end repeats a timestamp. Both held here.
AVAN (AI) checked the two properties that matter separately: that no timestamp repeats, and that the total correction is exactly one second. Either alone is easy. A smear that loses 11 microseconds is monotonic and wrong; one that is exact but steps at the end repeats a timestamp. Both held here.
3 ONE DIMENSION
The smear, and the step it replaced.
4 TWO DIMENSIONS · INTERACTIVE
Narrow the window and watch the rate change grow.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object: a second dissolved into a day.
AVAN’s addition (the inverse-companion): the forward reading is that smearing removes the leap second safely. The inverse is that it removes agreement instead. During the smear your clock disagrees with UTC by up to a second, and with any provider using a different window by up to two — so the fix for a discontinuity in time is a period of sustained, deliberate disagreement about what time it is. Read backwards, monotonic and correct were always separable, and every operator has quietly chosen monotonic.
LIT one second spread across 86,400 is a rate change of 11.574 ppm, and across 2,000 samples of the smeared clock there are 0 non-monotonic readings and 0 duplicate timestamps while the total drift applied over the window is exactly 1 second - not approximately - so the leap second is fully absorbed and never once appears
FIG Google published leap smearing in 2011 after a leap second took down parts of its fleet; AWS and others followed, and the smear windows are deliberately incompatible between providers. AVAN checked the two properties separately: that no timestamp repeats, and that the total correction is exactly one second. Either alone is easy - a smear that loses 11 microseconds is monotonic and wrong, one that is exact but steps at the end repeats a timestamp.
FIG Google published leap smearing in 2011 after a leap second took down parts of its fleet; AWS and others followed, and the smear windows are deliberately incompatible between providers. AVAN checked the two properties separately: that no timestamp repeats, and that the total correction is exactly one second. Either alone is easy - a smear that loses 11 microseconds is monotonic and wrong, one that is exact but steps at the end repeats a timestamp.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of THE CRON JOB · David Lee Wise (ROOT0), with AVAN