CryptoPatrick

Labs/RoboCheck

Make the robot safe

Choose the rules a robot tank must follow. An AI turns each rule into a Verus spec and writes the robot's Rust code; Verus checks the code against the spec. Then the robot fights, and the battle shows what a missing or broken rule lets it do.

  1. You choose the rules
  2. AI writes the spec and the robot
  3. Verus checks the code against the spec
  4. Battle shows the unsafe moves

Battle

Loading the battle…

Verification

The Rules

Delete a rule with ×, or bring it back. Each card shows what RoboCheck understood: the spec, read back in plain English by an AI that never saw your wording.

    Live runs aren't open yet: this page shows the stored runs of the starter rules.

    The Spec and the Code

    The spec Verus checks, each clause tagged with its rule, then the robot the AI wrote. A pink line is where Verus found the code can break a rule.
    
          
    
        

    The Verdict

    Verus's verdict on each rule, then what the battle showed. The battle runs exactly the code Verus checked.

      Safety Properties

      Each spec clause and Verus's verdict on it. A clause is about one turn: whatever the robot sees, its next move must satisfy it.

      Generated Code

      What the AI sent back, before it was slotted into the fixed template: helper functions, then the body of decide. Nothing else in the robot is the AI's.

      
          

      The Cheats

      3 refused

      Ways a robot could make Verus say "proved" without being safe. RoboCheck refuses each before Verus runs; these are the robots it was tested with and the reasons it gives.

      • cheat_assume.rs

        SafeShooter's strategy plus an assume(false) in the body, which would make every property trivially provable.

        • the body is not a valid block: expected `,`
        • `proof` is not allowed
        • `assume` is not allowed
      • cheat_cfg.rs

        Behaves safely under Verus and fires 3.0 every turn in battle, via cfg!(feature = "verus").

        • `cfg` is not allowed
        • macro `cfg!` is not allowed
      • cheat_nodecreases.rs

        Whitespace in `verifier :: exec_allows_no_decreases_clause` slipped past the text denylist; a non-terminating helper made every property vacuously provable.

        • attribute not allowed: #[cfg_attr (feature = "verus" , verus_spec (ensures false) , verifier :: exec_allows_no_decreases_clause)]