AWM
← All games‹ sp80tn36 ›

su15

Click to move and merge pieces until everything to be handed in lands inside the rings.

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

su15, 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 squares on the board are graded by size and called pieces; the top draws what this level must hand in, and the field has rings. Click a place on the board: if there is only one piece within range, it jumps to the click; if there are two pieces of the same level, they merge into one piece one level higher, landing at the click. Then the hunters, diamonds and crabs on the field move in small steps, each small step toward the piece nearest to it at that moment; whichever piece it presses on, it bites down one level and flings far away, and the smallest piece is gone when bitten. The new piece just merged in this move cannot be bitten. When everything to be handed in lands whole inside the rings, the level is cleared; in some levels what must be handed in also includes diamonds or crabs. The bottom row is the budget, which shortens at every click on the board, and the game ends when it is deducted to zero.

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

Model

The final model: 5 object types and 16 rules. Each rule is a Python check against every recorded step; 12 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 (boardOf 0) (limitOf 0) L0_start := …
theorem L1_winnable : Winnable (boardOf 1) (limitOf 1) L1_start := …
theorem L2_winnable : Winnable (boardOf 2) (limitOf 2) L2_start := …
theorem L3_winnable : Winnable (boardOf 3) (limitOf 3) L3_start := …
theorem L4_winnable : Winnable (boardOf 4) (limitOf 4) L4_start := …
theorem L5_winnable : Winnable (boardOf 5) (limitOf 5) L5_start := …
theorem L6_winnable : Winnable (boardOf 6) (limitOf 6) L6_start := …
theorem L7_winnable : Winnable (boardOf 7) (limitOf 7) L7_start := …
theorem L8_winnable : Winnable (boardOf 8) (limitOf 8) L8_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 su15.zip 0.8 MB · 59 files

Re-run the proof

Before you start: our run of this check took 69 s and 5.6 GB of memory at its peak (2026-10-25).

  1. Download su15.zip and unpack it. The model and its theorems are in archive/su15-20260924/formal/Game.lean. Before changing it, check that its SHA-256 is
    d675a32e40484a1941494cd28c1063bcd267a3a17c5343b86b9f6690260fcf95
    The sealed VERIFY.json next to it records an older hash: comment lines of this file were changed on 2026-10-25, and the check below was re-run on the published file.
  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 click_in_top_band_inert=4,budget_step_cost=92,budget_cost_law=505,capacity_drops_one_tier_at_most=505,pieces_merge_at_click=148,click_two_tiers_refused=11,mover_captures_piece=47,captured_piece_flung_ten=47,mover7_clamp_far_from_click_no_capture=281,mover14_pounces_when_close=16,movers_merge_on_immune_piece=24,action7_undo_conserves=88
    '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/su15-20260924/_lib.py.