[This is just a super low-priority thing that crossed my mind.]
I’m curious about your thoughts on the usefulness/ease-of-implementation of a non-static deadline in the case of t o’clock type goals.
I have a number of goals to get me to do things either earlier and earlier (say start work by t, eat no later that x, turn off screens by x, go to bed by z). The deadlines for these goals become quickly useless, though, since the changing requirement is actually a changing deadline, and so the “due in hh:mm:ss” can match the actual deadline of the first day, but is false the next day, unless you change the deadlines daily.
I’m wondering about a goal type where we could connect the deadline to the value required that day. If the required deadline is 12.50 (because you have to go to bed at 12:30), then the deadline would change to 12:30. The next day, when the required datapoint has to be under 12.35, the deadline would be 12:21am.
Like I said, just a thing that crossed my mind.