AWM
← All games‹ ar25cd82 ›

bp35

Move the player sideways, click to change terrain and gravity, and reach the pink cross to clear the level.

9 levels · 11 rules · all levels replayed in Lean

Replay

The certified run that cleared every level, one action at a time.

bp35, first frame of the certified run

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

Each level is a vertical shaft taller than the screen, and the camera follows the player. The player is one cell in the liquid, and its yellow nose points the way it faces. The left and right keys move it one cell sideways; vertically it cannot move by itself — after every step and every click it is carried all the way along the direction of gravity by the liquid. What can be clicked changes the terrain: the red switch flips gravity (floating up becomes sinking), the green rounded block turns into liquid when clicked, an orange block and an empty slot with a small cross swap when clicked, and when a purple foam block is clicked the liquid around it also turns into foam. The level is cleared when the player walks sideways into, or is carried into, the pink cross cell. When floating up the cross is below, and cannot be reached without flipping gravity. The undo key can step back one step at a time, and the step counter in the bottom row still grows.

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

Model

The final model: 3 object types and 11 rules. Each rule is a Python check against every recorded step; 10 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 : ∃ as : List Act, stepWins (L0_start : State) as = true := …
theorem L1_winnable : ∃ as : List Act, stepWins (L1_start : State) as = true := …
theorem L2_winnable : ∃ as : List Act, stepWins (L2_start : State) as = true := …
theorem L3_winnable : ∃ as : List Act, stepWins (L3_start : State) as = true := …
theorem L4_winnable : ∃ as : List Act, stepWins (L4_start : State) as = true := …
theorem L5_winnable : ∃ as : List Act, stepWins (L5_start : State) as = true := …
theorem L6_winnable : ∃ as : List Act, stepWins (L6_start : State) as = true := …
theorem L7_winnable : ∃ as : List Act, stepWins (L7_start : State) as = true := …
theorem L8_winnable : ∃ as : List Act, stepWins (L8_start : State) as = true := …

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 bp35.zip 0.6 MB · 57 files

Re-run the proof

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

  1. Download bp35.zip and unpack it. The model and its theorems are in archive/bp35-20260920/formal/Game.lean. Before changing it, check that its SHA-256 is
    f455a788e565472fb9c00365f49c608e80bbd8df7b4a5124683eb852fe17130d
  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 move_left=223,move_right=279,gd_move=317,rise_after_move=425,step_ticks=1422,action7_is_undo=27,click_clears_block=136,click_toggles_cyan=70,click_switch_consumes=82,flip_gravity=553,spikeblock_splits_cross=137,click_ceiling_block_lifts_one=66,spike_kills=882,spike_kills_falling=317,switch_tile_blocks_walk=6,tide_rises_and_kills=1416,levelup_iff_goal=1416
    '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/bp35-20260920/_lib.py.