i'd be like. so good at being a side character in a time loop. you walk up to me, say "i'm in a time loop," tell me exactly one thing you'd have no possible way of knowing, and i'll do whatever you need to try and break the loop. need me to stand outside in precisely one spot for seventeen hours? hell yeah i'm on it
you: hey i'm in a time loop and need help
me: what number am i thinking of
you: thirty six
me: hell yeah, how can i help
My wife, my girlfriend and I all have a time loop contingency where if any of us say that we are stuck in a time loop, the others will take that on trust, and help however we can.
Also, for the same reason, we occasionally do a time-loop check. So far, none.
And in case there's any doubt, I swear with my hand on a hardcover copy of House of Leaves that this is not a fucking bit.
going to spin up a system that automatically generates and encrypts an implausibly guessable number or passphrase every morning, that even i don't know until i decrypt & verify it, for the explicit purpose of verifying time loops
further thoughts: any number generated after the loop starts is fallible since the mere presence of a time looper existing changes the state of the loop from the very beginning, in different ways every loop, since they themselves are changed by each loop
this possibly leads to circumstances (whether large scale or butterfly effect) that would result in a different secret number being generated
so any absolutely rock solid secret would need to be generated in advance of the loop start
thus, our validation code would need to be generated up to 24h ahead of time to ensure that it will always be absolutely valid even in the face of changes introduced to the loop
most time loops are only a day, but several high profile loops in popular culture are longer (eg. Majora's Mask) so for safety, I'm going to suggest generating codes up to one week +1 day safety margin in advance
