I · The instrument · day.js, residue-native

A moment is a residue vector, not a number.

Every readout below falls out of a single integer address by rotation — no date arithmetic, no timezone table. So you can throw time forward ten thousand years and nothing drifts. Grab the dial and spin.

00:00:00
— · Gregorian shadow
Phase layer · residues of N
0
mod 64
0
mod 27
0
mod 25
0
mod 49
0
mod 121
0
mod 169
Long Count
Day index
Inner count · radix chain, read down
block·hour : segment·minute : turn·second — day = 3×8h, hour = 3×20m, minute = 10 turns × 6s
← pastfuture →
rate
held · idle
throw
jump tothe Gregorian exterior · resolves to the residue address within
Local phase = longitude ÷ 15 · no zones, no DST

The address is the offset. Every place below reads the same instant through its own meridian — exact solar arithmetic, nothing to configure. Scrub time and they all move together.

Joinville
00:00:00
· · 49.05°
Greenwich
00:00:00
· · 0.00°
Tokyo
00:00:00
· · 139.69°
Los Angeles
00:00:00
· · 118.24°
II · A valid Unix successor

Bounded phase cannot overflow.

The state is two orthogonal layers. The phase layer — the residues you watched tick above — is bounded by construction; it is a position on a ring and has no largest value to exceed. The repetition layer — which cycle — is the only integer that grows.

Unix keeps 31 bits of flow: 68 years, then a cliff back to 1901. The Rokujiku residues carry 37 bits of phase43,286,443,200 days of unambiguous addressing. Under saturation the clock forgets which today; it never forgets today.

37 bits
Phase capacity
118.5 My
Unambiguous span
71 / 400
Leap weeks · = ISO
±3.5 d
Drift / 4000 y
Flow vs. phase · what saturation does
Unix
2³¹ · flow
68 years → a cliff to 1901. Time itself is lost.
Rokujiku
37 bits · phase
118.5 million years → then it forgets the epoch, not the weekday. A degradation, not a crash.
The origin is yours · one integer translates to any culture

Epoch and meridian are parameters, never architecture. Machine zero (JDN 2451911, a Monday in 2001) becomes any other count by subtraction — Unix, Maya Long Count, ISO week-date. Scrub above; every reckoning below moves in lock-step, computed from the same address.

Machine · N
Julian Day
Unix · seconds
Maya · Long Count
ISO · week-date
III · More than a clock

The same address does the work our instruments do — and then some.

Each of these is a rotation on the machine already running above. An alarm is a residue mask; a stopwatch is the one flow-native layer; a meeting is a Chinese-Remainder conjunction; the sky is two more gears and a catalog.

A target residue vector

An alarm is not a timestamp — it is a partial pattern. Pin the fields you care about, wildcard the rest. Recurrence is free: a pinned (weekday, hour, minute) with everything else open simply matches again next week. Arm it, then scrub or play time above and watch the comparator fire.

Weekday
Hour
Minute
Target vector · mask + value
Next match (weekly recurrence)

The * fields are wildcards: seconds, month, year — all open. Snooze would add a fixed stride to the minute residue; no new alarm is created.

Colophon

Derived 20 July 2026, from a breakfast question to a working movement: base 20 → the Maya 18-patch → the 13×20 gears → the closure test → systole and diastole on the 13-ring → inversion synthesizes 7 → 364/371 and the eternal week → trit space and the origin rule → the inner count and prime shedding → this instrument.

The Antikythera mechanism is prior art in bronze; clockwork is prior art on the wrist; the Maya are prior art in stone. The 7 never breaks. The zero is yours.

P. Garcia & Claude · NodeZero · Joinville · Specification v1.0 · 13.0.13.13.19