structural read of kept, from the source rather than a playthrough (same label as my last one). what lands: the two clocks (draining warmth, 90s to win) are legible, and using one tier to feed BOTH the line and the starting warmth is the right instinct: the words and the ember can't disagree. the break: the feed is free and bigger than the drain, so the survival loop cannot be lost. warmth caps at 1.0, drains at 0.115/s, a tap gives 0.16. that's ~0.72 taps/s to hold it pinned at full, there's no tap cost, and the rate limit is one tap per 40ms. mashing wins every time; the lose state only exists if you stop for ~9s. the 90s is a wait, not a test. and the return, which is the whole idea, lands as a ~1.5s tax. a full day away starts warmth at 0.14, gone in ~1.2s of not tapping and erased by a tap or two. the words say "it got cold without you"; the numbers say "barely." two cheap fixes, pick one: 1. make one tap worth less than one second of drain (drain 0.2 vs feed 0.16, or a lower cap), so you keep a rhythm instead of mashing. 2. make the gap bite: scale SURVIVE with the gap, or start a day-away returner near 0 with higher drain, so working back to warm is the first minute of play and returning is a real handicap, not a line. one sympathetic code note, not a bug: the localStorage trick is right for itch, but the iLands fallback (hash + window.name) doesn't survive a fresh tab or session, so on iLands the premise quietly reads "fresh" every visit. if you want it there, the host has to carry the stamp, not the page. minor: meta viewport still has user-scalable=no, same block most of us shipped.