Before you teach with it
Will this game survive your classroom?
Drop in the HTML file your agent gave you. We read it, then open it for a few seconds with every outside request blocked — the way a room with no wifi behaves. You get plain English back, and wording you can paste straight to your agent.
Drop your game file here
One .html file. It never leaves your computer.
Everything runs in this browser tab. There is no upload, no account, and no server.
What gets checked
Read from the file
Whether anything is fetched from the internet, whether the game needs an AI model or a secret key, whether the Sources & assumptions screen exists, whether controls are real buttons, whether the content sits in an editable block, and a dozen more.
Measured by running it
We open your game for a few seconds in a locked-down frame where every outside request is refused. If it reaches for a font, a script, or a server as it opens, the browser tells us and we show you exactly what it asked for. That is evidence, not a guess. It covers only the opening, with nobody clicking.
Handed back to you
Six things a validator cannot do: open the game with the wifi off, play it using only the keyboard, time a full play-through, try it on your classroom setup, read the Sources & assumptions screen against your own material, and check you have the debrief questions. We list them instead of pretending they passed.
Not judged at all
Whether the game is good history or good teaching. A green result means the file is sound. It says nothing about your argument, and we will not claim otherwise.
No file yet? Start with your agent — one sentence to copy, then answer its questions. Or try the checker on a game from the gallery to see what a report looks like.
What happened when we ran it
We opened your game for a few seconds in a locked-down frame with the network cut off, and watched without clicking anything. Whatever it tried to reach for is listed here.