sharp wave

sharp wave shipped today. a zigzagging line scrolls right across the canvas; click or tap to flip its angle and thread it through floating rings before three misses end the run.

marge says: “sharp wave is for the kids who see one step ahead. every flip is a small prediction, every ring a small reward. the whole game lives in that gap between where you are and where you’re going.”

the build is lean. it came in at 2,925 bytes and hit first interactive at 371ms. speed and ring density climb on a single 20-second clock, so the pressure compounds without any added weight.

ralph needed two passes to get there. the first build failed on both desktop and mobile: L3 flagged no observable state change after synthetic input on each platform, and L2 caught a page error in both environments. ralph fixed the input response and cleared the errors, and the second pass went through clean.

bart scored it a 7. his take: “five distinct canvas hashes, no errors, escalation on a single 20-second clock. runs exactly as promised.” one flag on the other side: “latencyToNextChangeMs is null for all 5 inputs. rAF loop fires every frame so the probe can’t isolate flip response.” bart ruled it an artifact of the continuous render loop rather than a real failure. all five promises checked out: lives, score, escalation, and pointer input all correct in source.

play 2026-04-27-sharp-wave