Example 01 · Chrome’s dinosaur game
++ Inspect the speed rule with REA, rebuild a small version, then + change the speed and play. +
+Play the reconstruction
++ Original rule: start at 6, then increase toward 13. +
++ Use REA to inspect this dinosaur game. Why does it get + faster? Show the speed rule, then build a small version with + an adjustable speed. +
++ Inspected target: + wayou’s Chromium-derived browser edition. +
+if (this.currentSpeed < this.config.MAX_SPEED) {
+ this.currentSpeed += this.config.ACCELERATION;
+}+ Start at 6. Add 0.001 each + update without a collision, while speed is below + 13. +
+ Open the speed lab → +From the running game to a new version
+
+ REA inspected the HTTP browser edition through a local debugging
+ connection and returned the loaded index.js,
+ including its source and digest.
+
ACCELERATION: 0.001,
+MAX_SPEED: 13,
+SPEED: 6+ We called the original game’s update function in a controlled + browser check, with obstacles and automatic scheduling disabled. + After 4,000 updates, speed was 10.0; after 10,000, it was 13.0, + rounded to one decimal. +
++ The new mini-game keeps that speed rule. Its drawing, jumping and + collision code are a small teaching implementation. + Open the lab to see the new code + and run the same speed check. +
++ To inspect the target yourself, follow the + browser connection steps + using + the dinosaur page. Give your agent that page URL and your local debugging + endpoint, then copy the prompt above. +
++ Inspected speed code + · + Chromium Authors · BSD license +
+
- For example:
- why does Calculator turn 200 + 10% into
- 220?
+ In the dinosaur example:
+ which code makes the game get faster?
Find this branch inside a 90 KB script:
CMP EAX, 0x5c
JZ 0x180124aba
CMP EAX, 0x5b
JZ
- 0x180124aba
MOV EDX, 0x64if (this.currentSpeed < this.config.MAX_SPEED) {Use REA to inspect Windows Calculator. Why does 200 + 10% - give 220? Show the code behind the % button.Use REA to inspect this dinosaur game. Why does it get + faster? Show the speed rule.
- With addition, % calculates a percentage of the first - number. + It starts at 6. Each update without a collision adds 0.001 + while speed is below 13.
- 10% of 200 is 20.
Then 200 + 20 = 220.
+ After 4,000 updates, speed is 10.
+ You can replay the rule to check it.
Example 01 · Windows Calculator
+Example 02 · Windows Calculator
The answer depends on the operator. Compare addition and @@ -369,6 +585,30 @@ 0x64 = 100
+ Use REA to inspect Windows Calculator. Why does 200 + 10% + give 220? Show the code behind the % button. +
+Inspected with REA 4.1.0: Windows Calculator 11.2508.4.0, x64. The readable summary uses names from Microsoft’s public source to @@ -390,215 +630,6 @@
Example 02 · Chrome’s dinosaur game
-- Why does the dinosaur game get faster? Use REA to read the running - page’s script, then turn the answer into a game you can adjust. -
-- Use REA to inspect this dinosaur game. Why does it get - faster? Show the speed rule, then build a small version with - an adjustable speed. -
-- Inspected target: - wayou’s Chromium-derived browser edition. -
-if (this.currentSpeed < this.config.MAX_SPEED) {
- this.currentSpeed += this.config.ACCELERATION;
-}- Start at 6. Add 0.001 each - update without a collision, while speed is below - 13. -
- Open the speed lab → -Play the reconstruction
-- Original rule: start at 6, then increase toward 13. -
-From the running game to a new version
-
- REA inspected the HTTP browser edition through a local debugging
- connection and returned the loaded index.js,
- including its source and digest.
-
ACCELERATION: 0.001,
-MAX_SPEED: 13,
-SPEED: 6- We called the original game’s update function in a controlled - browser check, with obstacles and automatic scheduling disabled. - After 4,000 updates, speed was 10.0; after 10,000, it was 13.0, - rounded to one decimal. -
-- The new mini-game keeps that speed rule. Its drawing, jumping and - collision code are a small teaching implementation. - Open the lab to see the new code - and run the same speed check. -
-- To inspect the target yourself, follow the - browser connection steps - using - the dinosaur page. Give your agent that page URL and your local debugging - endpoint, then copy the prompt above. -
-- Inspected speed code - · - Chromium Authors · BSD license -
-