Motion-activated lights turn off while motion is actively happening! No, seriously, they do

Can someone please explain why the algorithm (or whatever) that runs your motion-activated lights turns the lights off a certain amount of time after motion is FIRST detected rather than after motion is LAST detected?? This ridiculous setting has the effect of **turning off motion-activated lights while motion is actively taking place**! This makes absolutely zero sense in the context of...wait for it...motion-activated lights. I've had non-smarthome motion-activated lights, and they ALL would remain lit for however long motion was taking place, plus a set amount of time after motion ceased. Ring's bass-ackwards lights turn off based on when motion is first detected, not last detected. Again, I would love to hear Ring's rationale for doing this backwards...because my Ring lights regularly turn off while motion is taking place. PLEASE, Ring, please change this protocol. Make your lights turn off a certain amount of time AFTER motion CEASES, not a certain amount of time after motion BEGINS.