The 42-day loop, explained carefully

The 42-day figure is widely used in public descriptions of Rewinding Cadence's repeating catastrophe. It is a useful way to understand the premise: the player is working inside a bounded cycle rather than an endless open-world timeline.

It is not currently a verified final-version rules table. The public record does not establish every reset condition, whether every day is equally playable, or how the global release would handle the structure.

For now, read 42 days as narrative and planning context. It explains why routes, information, and repeated attempts matter; it does not justify a day-by-day optimisation guide without a stable build to test against.

• Use the number to understand the premise, not to predict a release feature.
• Treat day-specific routes and reset rules as unverified unless a source names the build.
• Expect test observations to change as the project moves toward a wider release.

The final length, reset logic, persistence rules, and relationship between the loop and progression remain open questions. This page will be revised when an official guide or reproducible public test information answers them.