Verified technical workflow
The Daily Challenge is reproducible only within its stated inputs and local browser context. This page explains the current implementation, the meaning of Official and Practice, the unfinished-start rule, and why a repeatable layout is not a globally verified result.
The guide documents the current local workflow: date, size, direction, and version determine the repeatable layout; records and streaks remain in this browser, with no account or global leaderboard.
The device-local YYYY-MM-DD date, grid size, ascending or descending direction, and challenge version v1 form the challenge context. The implementation hashes those values and feeds a deterministic pseudo-random generator into a Fisher–Yates shuffle.
For a date, size, and direction, an eligible start is marked locally. If it completes normally, that result becomes Official. After an Official completion—or after the browser later detects an unfinished eligible start—the same configuration opens as Practice. Practice records do not replace the Official daily record.
The challenge changes when the device crosses local midnight, not at one global UTC boundary. Current and longest streaks use completed Official dates retained in this browser. Clearing site data or changing browsers can remove or isolate that local history.
Matching inputs reproduce a layout under the current version. They do not verify identity, input conditions, an unassisted first attempt, clock integrity, cross-device history, or a universal rank. The site has no account-backed Official lock or global leaderboard.
No. They can be on different local dates at the same instant, and local date is one of the layout inputs.
When the page later finds the active marker, it marks that configuration unfinished locally. Later starts for it are Practice replays rather than a new Official opportunity.
No. It identifies the date and configuration-derived challenge; it does not verify identity, conditions, or completion outside this browser.