Video Demo

Code

How I Built It

One file, no engine. The game is a single self-contained index.html — vanilla JS, Canvas for the sky simulation (sun arc, color-graded day/dusk/night gradients, twinkling stars), CSS for the teletype-era UI. No build step, no dependencies.

The ciphers are real. Caesar, Atbash/ROT13/reversal lenses, Vigenère, and a progressive-shift rotor cipher are all implemented and encoded at load from plaintext — the decoder tools you're given (dial, lenses, keyword field) apply the genuine inverse transforms. The dial shift, rotor start, and lens are randomized each playthrough, and the hints adapt: every possible answer has its own in-character riddle. A small dictionary makes English words glow gold in the preview as you get close, which turned out to be the single best UX decision in the project: it teaches the game without a tutorial screen.

Daylight is the only resource. The whole game runs on a single counter: daylight starts at eight real minutes and drains a second per second, mapped to an in-game clock that ticks from 16:04 toward 21:58. Spending it is deliberate — a wrong transmission costs 20 seconds, each hint costs 45 — but the design choice I'm proudest of is that the cost only lands when you commit. Turning the dial, swapping lenses, or typing a keyword is free; it just updates the live gold-glow preview. So the game rewards probing and only ever charges you for guessing. Let the counter reach zero and night falls — you finish the last codes by starlight, and the epilogue records whether you beat the sun (it grades the run Perfect Day, Before Sundown, or By Starlight). The solstice isn't a backdrop here; daylight is literally the thing you're spending.

The soundtrack is code, too. No audio files — the score is generated with the WebAudio API: a music-box arpeggio over a four-chord progression, one of three procedural tracks chosen at random each visit. A low-pass filter is tied to the daylight value, so the music literally darkens as the sun sets. All the interactive sounds (teletype clatter, dial ticks, chimes) are synthesized oscillator envelopes.

C is a three-tier system. This was the most interesting engineering problem: how do you put a live AI in a free, static, client-side game safely?

1. 
   Tier 1 — a gated Cloudflare Worker proxy. The Gemini API key lives server-side as a secret. The Worker only accepts requests from this game's origin, rate-limits per IP, caps input and output sizes, and enforces C's persona server-side — so the endpoint is deliberately useless as a general-purpose proxy. All it can do is talk like C.


2. 
   Tier 2 — bring your own key. Players can paste a free Google AI Studio key that never leaves their browser.


3. 
   Tier 3 — a scripted C with keyword-aware responses, so the game is fully playable offline with zero AI.

The game degrades through these tiers silently — if the shared free-tier quota ever runs out, C just gets a little more predictable.

The ending is honest. Whatever you answer at dawn, the game discloses which C you actually talked to — Gemini or the script. The hesitation before you answer is the point. That was Turing's point, too.

My workflow. I built this by hand as a single index.html — no engine, no framework, no build step — and tuned it live in the browser: how fast the sky drains, the resistance of the dial, the exact moment a decoded word starts to glow gold. The hardest part wasn't the ciphers but making C safe to ship to strangers, so I kept iterating on the Cloudflare Worker until the Gemini key was fully server-side and the line degraded gracefully from live AI, to your own key, to a script.

Prize Category

Best Ode to Alan Turing. The game is built around Turing top to bottom: codebreaking as the core mechanic, ending on a rotor machine; an imitation game where the player takes the interrogator's seat (C is named for the interrogator in Turing's 1950 paper); the third transmission decodes to a paraphrase of his famous reframing — "Can machines think?" is the wrong question; and the epilogue at dawn honors the man himself — born in June 1912, the codes he broke, the question he asked, and the persecution he suffered for being gay. The longest light, for someone made to work in the dark.

Best Google AI Usage. C is powered by the Gemini API (Flash models, free tier) — not as a gimmick, but as the game's thesis: it's a Turing Test run on an actual AI. The integration is production-shaped: a Cloudflare Worker keeps the key out of the client entirely, locked to the game's origin, rate-limited per IP, with the persona and token caps enforced server-side and replies trimmed to complete sentences. Model selection falls through a list of current Flash models automatically, and the whole system degrades gracefully to a player-supplied key, then to a script. Judges get live AI with zero setup — just open the game and talk to C.

Thanks for reading — and if you play just one minute of it, make it the last one. Answer honestly.