THE FOLD / BOSS / THE WALL / THE UNIX EPOCH
THE UNIX EPOCH
2038, and then 1901
1 WHAT IT IS · WHAT IT DOES · FACT OR FICTION
A signed thirty-two bit count of seconds from 1970 reaches its largest value at three fourteen in the morning on the nineteenth of January 2038, and the next second is 1901.
LIT verified live. the largest signed 32-bit integer is 2,147,483,647. Interpreted as seconds since the epoch that is 2038-01-19T03:14:07Z exactly. One more second wraps to −2,147,483,648, which reads as 1901-12-13 — not a crash, not an error, a date. Reading the same field as unsigned buys until 2106-02-07 and no further. The epoch itself is 1970-01-01T00:00:00Z, and every one of those days is assumed to be exactly 86,400 seconds long.
LIT verified live. the largest signed 32-bit integer is 2,147,483,647. Interpreted as seconds since the epoch that is 2038-01-19T03:14:07Z exactly. One more second wraps to −2,147,483,648, which reads as 1901-12-13 — not a crash, not an error, a date. Reading the same field as unsigned buys until 2106-02-07 and no further. The epoch itself is 1970-01-01T00:00:00Z, and every one of those days is assumed to be exactly 86,400 seconds long.
2 HOW IT WAS WEAVED · AI + HUMAN
The 2038 problem is the direct descendant of Y2K and is already live in anything computing a date thirty-odd years out — mortgages, bonds, certificate expiry.
AVAN (AI) computed the wrapped date rather than describing the overflow, because 1901-12-13 is the part that makes it dangerous. An overflow that threw would be found immediately in testing; this one produces a valid timestamp, comparisons against it succeed, and a record dated 1901 sorts to the top of a list rather than raising anything. The failure is not that the number breaks — it is that it keeps working.
AVAN (AI) computed the wrapped date rather than describing the overflow, because 1901-12-13 is the part that makes it dangerous. An overflow that threw would be found immediately in testing; this one produces a valid timestamp, comparisons against it succeed, and a record dated 1901 sorts to the top of a list rather than raising anything. The failure is not that the number breaks — it is that it keeps working.
3 ONE DIMENSION
2,147,483,647 seconds. Then 1901.
4 TWO DIMENSIONS · INTERACTIVE
Step over the boundary one second at a time.
5 THREE DIMENSIONS + AVAN’S INVERSE
The green forward object.
AVAN’s addition (the inverse-companion): the forward reading is that thirty-two bits are not enough. The inverse is that the width was never a statement about time, it was a statement about memory in 1971 — and it has outlived every machine it was chosen for. Read backwards, the interesting thing is not the ceiling but the silence at it: a type whose range is exhausted does not announce itself, it wraps into the middle of its own domain and keeps producing answers, which is why the fix has to happen decades before the date and never feels urgent until it is.
LIT the largest signed 32-bit integer is 2,147,483,647, which as seconds since the epoch is exactly 2038-01-19T03:14:07Z, and one more second wraps to -2,147,483,648 which reads as 1901-12-13 - not a crash, not an error, a date; reading the same field as unsigned buys until 2106-02-07 and no further, the epoch itself is 1970-01-01T00:00:00Z, and every one of those days is assumed to be exactly 86,400 seconds long
FIG The 2038 problem is the direct descendant of Y2K and is already live in anything computing a date thirty-odd years out - mortgages, bonds, certificate expiry. AVAN computed the wrapped date rather than describing the overflow, because 1901-12-13 is the part that makes it dangerous: an overflow that threw would be found immediately in testing, while this one produces a valid timestamp, comparisons against it succeed, and a record dated 1901 sorts to the top of a list rather than raising anything.
FIG The 2038 problem is the direct descendant of Y2K and is already live in anything computing a date thirty-odd years out - mortgages, bonds, certificate expiry. AVAN computed the wrapped date rather than describing the overflow, because 1901-12-13 is the part that makes it dangerous: an overflow that threw would be found immediately in testing, while this one produces a valid timestamp, comparisons against it succeed, and a record dated 1901 sorts to the top of a list rather than raising anything.
◆ sealed .dlw.fold → folded to ROOT_0 · a sphere of THE WALL · David Lee Wise (ROOT0), with AVAN