Nice idea and interesting discussion in the article. However, I think the article might benefit from a few more editing iterations by a human author.

As others already mentioned: the article first sets out to strip away all culture-specific aspects of a clock but then retains the concept of seconds, minutes and hours. This makes some sense, of course, and is implicitly mentioned as "Calibration to a timescale". However, I would have liked a discussion of alternative ways how this could have been achieved and why the 12/24-hour system is used in the end.

Another nitpick:

> 4. A readable mapping. Humans don't read raw oscillations. We read "14:37:09" or "sunset in 42 minutes." Reading time is always a translation layer.

> That fourth point matters more than most people think. A sundial reads apparent solar time, which is local and visibly tied to the Sun. But apparent solar time is not uniform.

This argument - which is used to introduce the next section - makes no sense. A sundial has a readable mapping. (And I would argue that it might be the most non-culturally-defined, useful type of clock for humans).

Next, the author introduces "layers of time" that do not actually seem to be layers but different views (though partially layered).

Then we are given a number of requirements for the implementation - e.g., "no daylight savings time". The clock at the top is adjusted for local daylight savings time, however.

Finally, large parts read as if an LLM has written them (many cases of "Not X, Y", a full screen page explaining that n*2+1 is more than twice as large as n, a discussion of the irrelevant test suite, ...). [^1]

[^1] the few references to other sources have apparently been copied without changing the source markdown to hyperlinks. I think a human author would notice this when checking the rendered article, no?