The problem is that enjoyment has, oddly enough, been misallocated to all the liminal spaces and moments in life. So most optimization tends to elide enjoyment.

Enjoyment elision is the number one cause of meat suit user dissatisfaction. The engineers insist it's not a compiler design bug, stating that those moments of enjoyment are, in fact, unreachable. The UX team says it's not the user's fault either, as it's a fully intended UX choice. The current proposed solution is to push this issue upstream, requesting that all enjoyment be moved from the journey to the destination.

Oh very well, so it's corruption on the enjoyment program that leads to misallocation.

What are good logs or signals a meat suit user could monitor in order to watch for misallocation and allow the program to recover?