REA Reverse – Engineer Anything

Let's try two examples. Change a game's speed, then return to Calculator and rebuild its % button. Example 01 · Chrome’s dinosaur game Why does the dinosaur get faster? Play the reconstruction Original rule: start at 6, then increase toward 13. Enable JavaScript to play the reconstruction. The code and explanation above remain readable. REA returned The script actually running in the page. The agent reads its update function and speed settings, then uses that rule in a new game. ›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. What each part does 01 · REARead the running game’s scriptReturn its actual code and settings to the agent. 02 · Your agentRebuild the rule, add a controlUse the recovered acceleration in a small game with a speed slider. 03 · YouChange the speed and playTry the original acceleration, then choose your own pace. 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