Kind of. If you “absolutely must” have monotonic time, though, and also care about NTP, then just pointing to TAI (in DJB’s naïve definition) or GPS time is not enough. You need to make decisions on whether you, for example, would prefer your imprecise seconds to be more even individually or for the aggregate count to be more accurate (NTP of course gets you the latter by default). Dear Sir[1], you have done metrology.
I really just want the software time to be as good as the underlying hardware clock...
...rather than setting a rather awful minimum performance spec of 10ppm smearing over a leap second day.
Three lies:
Universal - multiple smear implementations, linear vs cosine off the top of my head.
Coordinated - whose in charge here? Google? Facebook?
Time - doesn't even try for 1s/s
UTC is, for all intents and purposes, yet another human readable time zone. And should be treated as such. The underlying hardware problems I have and understand. Don't need the software making it worse.
[1] https://people.csail.mit.edu/rachit/post/you-have-built-a-co..., https://news.ycombinator.com/item?id=29891428