Session lengths the Lena Arcade protocol accepts
Timed-run checklist used before a browser build keeps a Lena Arcade seat. Reference windows checked through 20 November 2026.
The protocol records session length as a hard gate. A build that cannot finish a readable run inside its band does not hang on the ridgepole. This file lists the steps applied to Ripple Reel, Shanty Slide, and Site Kite.
-
Step 1 — Choose the band by filter
Ice filter: ~45–90 seconds. Tower filter: ~20–60 seconds. Bands come from the Lena Arcade methodology page and are not adjusted mid-check to save a failing build.
-
Step 2 — Discard invalid clocks
AFK time, tab-hidden time, and intentional stalls are discarded. Only intentional runs count. The protocol notes the discard rule so later readers do not treat max wall-clock as the session length.
-
Step 3 — Sample at least five intentional runs
Median and range are logged. A single lucky short run does not clear the gate. On the dated pass, all three shortlist builds produced medians inside their bands.
-
Step 4 — Pair length with fail clarity
A short run that ends without a nameable cause fails even if the clock looks good. Thin ice, seals, hooks, beams, and concrete must remain narratable. Length without clarity is incomplete.
-
Step 5 — Publish absences with the times
No public store rating — browser build, not a store listing. Session times are desk measurements, not store “play time” fields. Contact: [email protected].
What to expect when re-checking
If a future build update pushes medians outside the band, the seat is reopened. The ridgepole prefers an empty hook to a padded one. That preference is the Lena Arcade length discipline in practice.