Conversely, there’s also a general assumption that the goal’s rate dominates, whether it’s explicit or implied. So arguably, endlessly striving is the current default, apart from the minor niggle that there is, um, an end date.
In the new UI, we get asked to set a rate, and the end date gets set to sometime in 2027. (At least, that’s what just happened for me, can’t swear that it’s the default.) But it’s far enough out that we’re unlikely to trip over it for a while. So I think that is the simpler thing, code-wise, and that we’ve done it.
The next simple thing would be to show or hide the three-field road dial (a.k.a. ‘commit to’) depending on the value of that end date. At a minimum, we should show the three field version if the end date is imminent; it’s too mysterious otherwise when the countdown isn’t related to the safety buffer.
Those of us who try to set explicit real-world end dates on goals have encountered all sorts of trouble, depending on which of the fields we used to specify the goal’s slope. (To be clear, not trouble in the day-to-day sense, but after a derailment or a ratchet, etc.)