Somebody asked this question as a reply to one of the tweets and the author replied:
https://twitter.com/jxxf/status/1219128189768871936> We considered a number of options, but decided that the fix was not making it about dates at all but rather offsets (e.g. "t+1 year", "t+2 years", etc.), which bypassed the Y2038 issue.
> We then immediately called something else to do the final translation into dates for the CSV.
