R01 · BRIEF A · GAME · PILOT PROTOCOL

Lighthouse Keeper

The same brief, handed once to each of six model-through-CLI configurations, no retries. Open each recovered artifact in its plate and judge with your own eyes.

RECOVERED
06
PENDING
00
VERDICT
UNGRADED
EFFORT
MAX
RUN
2026-07-24

Pilot evidence predates the levelled harness. Any released pilot round is shown as-is and excluded from cross-vendor conclusions; protocol v1 is the canonical series.

THE BRIEF

Each configuration was asked for a complete arcade game in one self-contained HTML file: rotate a lighthouse beam to guide ships past hidden rocks, with a start screen, keyboard and touch controls, rising difficulty, Web Audio sound, and a restart loop.

WHY THIS TEST

A game is a merciless brief. Collision, input, game state, difficulty, and audio all have to work together in one shot, and any dropped piece is visible the moment you press play. There is nowhere to hide a stub.

THE GOAL

See which configurations carry a full interactive system end to end in one reply, with no retries.

THE PROMPT · SENT VERBATIM TO ALL SIX

Build a complete, playable browser game in a single self-contained HTML file: a lighthouse-keeper arcade game. The player rotates a lighthouse beam to guide incoming ships safely past rocks in the dark. Ships spawn at the edges and drift toward the harbor; the beam reveals rocks and calms ships it touches; any ship that hits a rock ends the game. Score = ships saved. It must include: a start screen with instructions, keyboard and mouse/touch controls, increasing difficulty, sound effects generated with the Web Audio API, and a game-over screen with restart. No external resources, no libraries, no network requests. Reply with ONLY the complete HTML file.

HOW THESE RUNS WORK · METHODOLOGY →