Inspect → rebuild → change
- REA found how the running game increases its speed. This small - reconstruction lets you keep that rule or choose a new speed and play. + To recreate the game’s acceleration, first find the rule that controls + its speed. REA returned the running script; + we used its rule to build this mini-game with + adjustable speed.
+ Finding out how software works by + examining the program itself. +
++ The goal: understand a feature well enough to + explain it, + change it or + rebuild it. +
+Before REA · You investigate
+With REA · You ask your agent
++ Use REA to inspect this dinosaur game. Why does it get + faster? Show the speed rule. +
++ The game adds a little speed on each update. Its script sets + the starting speed, the increment and the stopping + point. +
+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
@@ -193,6 +302,14 @@ >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. +
+From the running game to a new version
+What each part does
- Finding out how software works by examining the program. -
-- In the dinosaur example: - which code makes the game get faster? -
-Before REA · You investigate
-Find this branch inside a 90 KB script:
-if (this.currentSpeed < this.config.MAX_SPEED) {
- this.currentSpeed += this.config.ACCELERATION;
- }
- With REA · You ask your agent
-- Use REA to inspect this dinosaur game. Why does it get - faster? Show the speed rule. -
-- It starts at 6. Each update without a collision adds 0.001 - while speed is below 13. -
-
- After 4,000 updates, speed is 10.
- You can replay the rule to check it.
-
- Your agent uses REA to locate and read the code, then connects - the findings to your question. -
-Example 02 · Windows Calculator
-- The answer depends on the operator. Compare addition and - multiplication. -
+Try the calculation
@@ -507,11 +526,45 @@ SPEED: 6REA returned
++ The % handler’s original instructions and decompiled + code. + The agent reads the two branches and explains which rule each + operator uses. +
+
- The installed app’s calculation code checks for multiplication
- or division before computing the percentage.
+ For this example, previous = 200 and
+ current = 10.
+ Use REA to inspect Windows Calculator. Why does 200 + 10% + give 220? Show the code behind the % button. +
+200 + 10% → 200 + 20 → 22010% of 200 = 20 → 200 + 20 = 220
+ 200 × 10% → 200 × 0.1 → 20200 × 0.1 = 20
+ From the installed app to an explanation
+ShellExecuteW opening
- ms-calculator:.The code opens ms-calculator:. The agent then
+ selects the installed app’s library.
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 diff --git a/website/style-guide.md b/website/style-guide.md index d8afc1c00..e8c5085d4 100644 --- a/website/style-guide.md +++ b/website/style-guide.md @@ -65,9 +65,14 @@ requiring the reader to understand either language. Show a simple agent prompt and the specific facts REA supplies to answer it. Put compact setup at the beginning of the homepage: a copyable installation -prompt and the ordinary setup command. Follow it with the beginner examples. -Put the most immediate result first. An interactive example can precede the -process explanation; on mobile, show the demo before its supporting code. +prompt and the ordinary setup command. Then explain what reverse engineering +means and what it lets someone do, before the worked examples. +Begin each example with its goal and the reason to inspect that program. +Name the actual evidence REA returned and what the agent did with it. +Use short labels, selective bold text and the shared blue highlight to make +those facts visible when scanning. Keep source, interpretation and new code +attributed to their respective roles. On mobile, the demo can precede its +supporting code once its purpose is clear. Show how the reader's task changes using the same question on both sides of a manual/agent comparison. Let returned evidence make REA's contribution visible.