AWM
← All games‹ cn04ft09 ›

dc22

Walk on the map, click cards that change it, and walk into the yellow exit to clear the level.

6 levels · 17 rules · all levels replayed in Lean

Replay

The certified run that cleared every level, one action at a time. Beside each step: the rules of the model that explain it; they are also marked in the rule list below.

dc22, first frame of the certified run

Explained by

Press Play or step to load the run. Keys, while the player is on screen: ← → step, Space play / pause. A click is circled; cells that changed are outlined.

How it plays

The left of the screen is the map and the right is the card panel. The arrow keys make the player walk on the map, and clicking presses a card on the panel. Each card remote-controls a group of cells on the map that belongs to it: a bridge of the same colour flips once between passable and impassable, the arm of a hub flips over along the diagonal, a bar on a track moves one notch to the right, a band extends or retracts one notch, a teleport card makes the player swap places with a pad of the same pattern colour, and the four-colour small icon changes the pattern colour of a pad. Walking into an icon on the ground adds one card of the same colour to the panel. Use the cards to pave the road through, and walk into the yellow exit to clear the level. The cell under the player's feet will not be pulled away, and a click that would leave the player hanging in the air has no effect; when standing on a bridge of a certain colour, clicking the card of the same colour does not flip it. The last two levels also have mechanisms such as claws, rods, cross pieces and square frames.

dc22, first frame of the certified run
Start
dc22, last frame of the certified run
After the winning move

Model

The final model: 8 object types and 17 rules. Each rule is a Python check against every recorded step; 14 of them are translated into Lean (the paper's per-game table). Code under a rule is the file of the same name in the agent's Lean project.

Object types

Rules

Code is shown with comments and the agent's notes removed; the files as written are in the archive under Check it yourself.

Proof

For every level, Lean starts from the level's first screen, applies the model's rules to the certified actions, and checks that every computed state agrees with the recorded frame on the components the model represents, and that the last one wins. Each theorem is closed by the Lean kernel and is a statement about the learned model.

Every level can be won

theorem L0_winnable : Winnable (boardAt 0) (startAt 0 1628) := …
theorem L1_winnable : Winnable (boardAt 1) (startAt 1 1652) := …
theorem L2_winnable : Winnable (boardAt 2) (startAt 2 1695) := …
theorem L3_winnable : Winnable (boardAt 3) (startAt 3 1740) := …
theorem L4_winnable : Winnable (boardAt 4) (startAt 4 1832) := …
theorem L5_winnable : Winnable (boardAt 5) (startAt 5 1946) := …

Statements only; the proofs and the full Lean project are in the archive, with the steps to re-run them, under Check it yourself.

Check it yourself

Everything on this page comes from files you can download and check. The archive holds the agent's files: the recorded run, the concept book, the concept sources, the Lean project and the sealed model file, plus the record of our kernel check.

Download dc22.zip 4.2 MB · 87 files

Re-run the proof

Before you start: our run of this check took 426 s and 18.6 GB of memory at its peak (2026-10-23).

  1. Download dc22.zip and unpack it. The model and its theorems are in archive/dc22-20260920/formal/Game.lean. Before changing it, check that its SHA-256 is
    d1021cb4846d84634f376a24006d7d39b05888a2b99e57cb2b5b2f07e8005bd4
  2. Install Lean with elan, then the version named in the archive's lean-toolchain:
    elan toolchain install leanprover/lean4:v4.34.0
  3. Copy the model file to Check.lean and append these two lines to the copy:
    #print axioms consistent
    #print axioms faithful
  4. In the folder that holds Check.lean, run:
    lean +leanprover/lean4:v4.34.0 -M60000 Check.lean
  5. Lean should finish without errors and print:
    'consistent' depends on axioms: [propext]
    'faithful' depends on axioms: [propext]

What a pass establishes

consistent: for every recorded transition, as read by the agent's parser and with duplicates removed, every rule whose condition holds also has its effect hold. faithful: the certified run, recomputed step by step from the first screen of each level, matches the record and ends in a win. Axioms used: propext, all among Lean's standard ones.

What it does not establish: that the parser reads the screens correctly (that step runs in Python, outside Lean), or that a rule whose condition never occurs in the record is right. The Python file that produced the readings inside the model file is in the archive at meta/repair-20260928/lib/dc22-20260920/_lib.py.