I've got a much simpler alternative idea: we could say that every clock has a

> static constinit const time_point translation_time;

... data member. There is no potential for ODR violations because you
cannot access it during constant evaluation anyway. It's simply saying
that you're baking the timestamp into the executable. The linker could
still optimize it out if it's unused.