AWM
← All games‹ m0r0re86 ›

r11l

Click diamonds to move them; the level is cleared when each group's jar presses on a locked target ring.

6 levels · 9 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.

r11l, 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

There are several groups of diamonds on the board, each group leading a jar, and the jar always stays at the centre of this group of diamonds. The jar cannot be clicked, only the diamonds can be moved: first click a diamond to select it, then click a piece of empty ground, it jumps over, and the jar immediately moves to the new centre. When a jar lands on a paint block, it covers itself with the colour of that block, and the paint block disappears with it. When the colour on the jar matches the colour a target ring wants and it presses on that ring's target centre, the target ring locks. The level is cleared when each group's jar presses on a locked target ring. Grey hard walls cannot be stepped on by anyone, and light-blue soft-ground diamonds can be stood on but a jar cannot press onto them; a move that would step on these places is voided. The vertical bar on the left records how many clicks have been made.

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

Model

The final model: 6 object types and 9 rules. Each rule is a Python check against every recorded step; 8 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 (levelBoard 0) (L0_start : World) := …
theorem L1_winnable : Winnable (levelBoard 1) (L1_start : World) := …
theorem L2_winnable : Winnable (levelBoard 2) (L2_start : World) := …
theorem L3_winnable : Winnable (levelBoard 3) (L3_start : World) := …
theorem L4_winnable : Winnable (levelBoard 4) (L4_start : World) := …
theorem L5_winnable : Winnable (levelBoard 5) (L5_start : World) := …
theorem twin_winnable : Winnable blankBoard (twin : World) := …

What cannot be won under the model

theorem unsolvable_by_noInk (b : Board) (w : World) (h : NoInk w) :
    ∀ as : List Cell, everGoal b w as = false := …
theorem stuck_unsolvable : ∀ as : List Cell, everGoal blankBoard (stuck : World) as = false := …

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 r11l.zip 0.3 MB · 58 files

Re-run the proof

Before you start: our run of this check took 252 s and 16.8 GB of memory at its peak (2026-10-24).

  1. Download r11l.zip and unpack it. The model and its theorems are in archive/r11l-20260907/formal/Game.lean. Before changing it, check that its SHA-256 is
    9ce832789da3054c5316e1f8848a8eb309d3ad5137cc7006eed99f264c721ed4
  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/r11l-20260907/_lib.py.