AWM
← All games‹ tr87vc33 ›

tu93

Move the player along bridges, avoiding sentries, patrols and chasers; walking onto the goal clears the level.

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

tu93, 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 cells are connected by grey bridges. The blue one is the player, and the small mark on it shows its facing; the green cell is the goal. Press a direction key: if there is a bridge in that direction, the player moves over one cell, then each orange patrol walks one cell along its bridge (turning around at the end), and each awake dark-red chaser pounces one cell along the shortest path toward the cell the player was on; if there is no bridge in that direction, nobody moves. Walking onto the goal clears the level. Red sentries stand still and stare at the cell right in front of them: stepping into that cell from the front loses, while stepping into their cell from the side or from behind can trample them away; patrols and sleeping chasers can also be trampled from the side. Being landed on by a patrol or chaser loses, and if in the same step that the player walks onto the goal a patrol also lands on the goal, it likewise counts as a loss. A chaser wakes when the player walks to within two cells in front of it. The budget band along the bottom edge gets a notch shorter with each press, and reaching zero also counts as a loss.

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

Model

The final model: 8 object types and 10 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 := …
theorem L1_winnable : Winnable (levelBoard 1) L1_start := …
theorem L2_winnable : Winnable (levelBoard 2) L2_start := …
theorem L3_winnable : Winnable (levelBoard 3) L3_start := …
theorem L4_winnable : Winnable (levelBoard 4) L4_start := …
theorem L5_winnable : Winnable (levelBoard 5) L5_start := …
theorem L6_winnable : Winnable (levelBoard 6) L6_start := …
theorem L7_winnable : Winnable (levelBoard 7) L7_start := …
theorem L8_winnable : Winnable (levelBoard 8) L8_start := …
theorem bridged_winnable : Winnable bridgedBoard start0 := …

What cannot be won under the model

theorem key_no_win (b : Board) (C : List Cell) (t : Cell) (hc : closedIn b.bridges C = true)
    (ht : b.target = some t) (hout : C.contains t = false) :
    ∀ s d, C.contains s.player = true → step b s d ≠ .won := …
theorem unsolvable_by_cut (b : Board) (C : List Cell) (t : Cell) (hc : closedIn b.bridges C = true)
    (ht : b.target = some t) (hout : C.contains t = false) (s : St) (hp : C.contains s.player = true) :
    Unsolvable b s := …
theorem cut_unsolvable : Unsolvable cutBoard start0 := …

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 tu93.zip 0.3 MB · 56 files

Re-run the proof

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

  1. Download tu93.zip and unpack it. The model and its theorems are in archive/tu93-20260910/formal/Game.lean. Before changing it, check that its SHA-256 is
    fd131f2c2774deecc5afe16ae31904dd67f9b0940417421e052c5743e13e5bff
  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_shift=286,bridge_gate=286,mark_faces=286,reach_goal=303,hud_drain=289,hud_reset=14,foe_walks=187,foe_kills=23,patrol_kills=1,patrol_steps=140,patrol_turns=69,chaser_wakes=87,chaser_alarm=15,chaser_steps=71,chaser_hunts=75,chaser_hidden=3,game_over=289
    '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/tu93-20260910/_lib.py.