AWM
← All games‹ ls20r11l ›

m0r0

Move two mirrored squares at once with the direction keys; landing both on one cell clears the level.

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.

m0r0, 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 two squares of the same colour and the same shape on the field. Each press of a direction key moves both at once: for the up/down keys the two move in the same direction, for the left/right keys the two move in opposite directions, like a mirror; each goes one cell if its landing cell can be entered, and stays in place if blocked. If the two land on the same cell, the level is cleared. The solution is to use walls, doors and marks to block one of them, pull the two together and then bump them into each other. Checkerboard-patterned cells are dangerous cells; stepping into one restarts the level from the beginning. A cell with a small square dot is a mark; it normally blocks the way, and after clicking it, the direction keys push it instead. An isolated coloured cell is a switch: when a block stands on it, the door of the same colour opens, and when it steps off the door closes.

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

Model

The final model: 8 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 L0_board L0_start := …
theorem L1_winnable : Winnable L1_board L1_start := …
theorem L2_winnable : Winnable L2_board L2_start := …
theorem L3_winnable : Winnable L3_board L3_start := …
theorem L4_winnable : Winnable L4_board L4_start := …
theorem L5_winnable : Winnable L5_board L5_start := …
theorem scene_open_winnable : Winnable opened start := …

What cannot be won under the model

theorem key_no_win (B : Board) (kb : KeyBoard B) : ∀ s a, Key B s → step B s a ≠ Res.won := …
theorem unsolvable_by_mirror_key (B : Board) (kb : KeyBoard B) (s : St) (h : Key B s) : Unsolvable B s := …
theorem scene_stuck_unsolvable : Unsolvable stuck start := …
theorem scene_open_not_unsolvable : ¬ Unsolvable opened start := …

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 m0r0.zip 0.4 MB · 64 files

Re-run the proof

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

  1. Download m0r0.zip and unpack it. The model and its theorems are in archive/m0r0-20260910/formal/Game.lean. Before changing it, check that its SHA-256 is
    3fccb87cba48feed7f403050706995d3ba430abb04b8c1ce238bb632265a17fc
  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:
    GUARD_HITS two_pieces_50=475,action5_noop=4,hud_monotone=475,click_selects=60,dim_iff_highlight=301,frozen_when_selected=92,push_door=92,move_delta=317,move_iff_clear=305,dest_set=305,collide_wins=317,hazard_resets=2,identity_needs_one_move=151,parity_flips_iff_blocked=100,land_on_floor_only=475,mirror_pair_persists=8,terrain_static=475,switch_opens_gate=52,gate_closes_on_leave=12,gate_stays_open=165,piece_survives_on_gate=12
    'consistent' depends on axioms: [propext]
    'faithful' depends on axioms: [propext]
    The first line is printed by the file itself: for each rule, how many recorded transitions meet its condition.

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/m0r0-20260910/_lib.py.