AWM
← All games‹ sc25sp80 ›

sk48

Stretch and slide ropes so each rope's target blocks match the colour order shown in the diagram.

8 levels · 7 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.

sk48, 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 kinds of player: the horizontal player hangs on the vertical track on the left and extends a horizontal rope to the right; the vertical player hangs on the horizontal track at the top and extends a vertical rope downward. Click a player to select it. Pressing a key along the rope's direction lengthens or shortens the rope by one cell, the coloured target blocks strung on the rope move along, and the run in front of the rope tip is pushed away; pressing a key perpendicular to the rope translates the player together with the whole rope by one cell, and the target blocks the rope sweeps over are carried away. When the colour order of each rope, counted outward from the player, agrees with the corresponding group in the diagram at the bottom of the screen, the level is cleared. Things cannot be pushed when they hit the board edge, a wall, or are pinned by another rope; dead ropes hanging from the top are also named in the diagram.

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

Model

The final model: 6 object types and 7 rules. Each rule is a Python check against every recorded step; 4 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 L6_winnable : Winnable L6_board L6_start := …
theorem L7_winnable : Winnable L7_board L7_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 sk48.zip 0.8 MB · 75 files

Re-run the proof

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

  1. Download sk48.zip and unpack it. The model and its theorems are in archive/sk48-20260920/formal/Game.lean. Before changing it, check that its SHA-256 is
    54a19b11042fe8c83267871ed9eb27f1a5218cee6d96475e973fd1c0f047880d
  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 a1_up=209,a2_down=188,a3_retract=194,a4_extend=256,a6_select=59,a7_bounce=1,a7_drag=4,a7_fallthrough=4,a7_shuttle=31,bar_clock=1007,bar_monotone=1013,board_static=1013,frame_not_state=1007,hmove_blocks=452,hud_checklist=1013,levelup_threaded=975,move_block=245,rail_band=402,retract_floor=196,rope_ceiling=12,rope_limit=1013,v_capture=17,v_carry=12,v_drag=63,v_extend=89,v_push=49,v_retract=63,v_slide=55,vmove_blocks=245,vrope_static=138,vslide_blocks=55
    '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/sk48-20260920/_lib.py.