The Read · Speedrun
Speedrun it. We dare you.
The engine is deterministic on purpose. That means it can, in principle, be perfectly counter-simulated — with tools. Good. That's not a bug we're going to patch. It's the whole point made honest.
Why we don't add hidden noise
The easy way to stop a speedrunner is to make the bot secretly random when it's losing — rubber-banding. We will never do that. The instant the engine hides a die-roll, the Determinism Contract is broken and every "we don't cheat" claim on this site is a lie. Determinism is the audit. It's also what makes counter-simulation possible. We keep both.
Two ways to beat it
The assisted way: run the same committee of predictors on the bot's own history, in another tab, and read the reader. That's a legitimate, beautiful exploit of a deterministic system, and if you build it, we want to see it. The unassisted way — the real game — is doing it with the only computer you brought: staying genuinely unreadable while you find the seam yourself.
The one rule
The only permitted changes to the engine are new reader strategies, and every one is announced in a changelog. We never patch to beat a specific person, we never add randomness, and we never touch the engine silently. The published source always matches the shipped bot.
About the leaderboard
Any leaderboard that runs in your browser is honor-system — a determined speedrunner with a counter-simulator can top it, and there is no client-side anti-cheat that would survive five minutes of devtools. So we won't pretend there is one. When a board exists, it will say, plainly, that it's honor-system. We'd rather tell you the truth than sell you a lock that doesn't lock.