Thanks for that intel! Good to know. (It might be nice “customer journey” practice to briefly note that on the dashboard, to clear up confusion like mine.)
On a related note, I wonder then if it makes sense to insta-archive Do More goals that have 7+ days of buffer, since they’re in no danger of derailing within the archive window.
And on a related related note, it seems like consistent behavior might be something more like this:
- Goal is marked for archiving. If 7+ days of buffer: insta-archives. Else stays active.
- Goal in archive period derails. If it rerails with more buffer than days left before archive, it insta-archives. Else stays active.
My thinking is that Beeminder’s point is not to let you off the hook because right now you don’t want to do the thing. But that’s exactly what the existing “derail during archive window” lets you do. Example:
Suppose I have a goal to do the thing, which I’ve set up to give me no extra buffer when I derail. I’ve done this because it motivates me not to slack off on the thing; derailing won’t help me avoid doing it. But now I’m in a bind, so I mark it for archiving on a day when I know I’m going to derail. Boom, it insta-archives. Then I restart it with a bunch of buffer.
Related loophole is that when you change how many days of buffer you get after a derail, it takes instant effect (and is functionally equivalent to doing the above to weasel out of past-you decisions), so if one of these is contra-Beeminder-principles, then the other is, too.
Long story short, there are a few places where Beeminder does not enforce the akrasia horizon.