if end date is within akrasia horizon then changing rate introduces immediate zero slope

Before: do more goal with target inside akrasia horizon (tracking time/reminder to do work on hour based programming contract, some minor work on geolocating election commissions)

What I did: changed slope (end result on Y-axis it was within akrasia horizon, but as contract extension for more hours is likely I wanted to change future slope)

What I got: zero slope until akrasia horizon ends - there was no such flat segment previously


I tried to reproduce by changing slope again but failed. Maybe you can look into logs and figure what happened.

Main drawback is that there some sort of way of “gimme immediate break” without contacting human.

Obviously, ratcheting is the workaround what I just did.

1 Like

Beautiful bug report! DM me for stickers if you’d like some!

1 Like