Reverse engineer anything with agents, from app behavior down to native binaries.
TypeScript agent-skillsai-agentsbinary-analysisclaude-codeclicodexcordisdecompilerdeveloper-toolsdshdsh-pluginghidrahopperllmmcpmodel-context-protocolreareverse-engineeringstatic-analysistouhou
feat(website): clarify reverse engineering and showcase goals
N0zoM1z0e750c262fbf3
diff --git a/website/README.md b/website/README.mdindex ae758a895..f0da06ca4 100644--- a/website/README.md+++ b/website/README.md@@ -26,7 +26,7 @@ Open <http://127.0.0.1:4173/>. Refresh the browser after editing a file.## Pages-- `public/index.html`: compact setup, playable dinosaur reconstruction, manual/agent comparison, Calculator percentage example and case-study overviews.+- `public/index.html`: compact setup, reverse-engineering definition and purpose, manual/agent comparison, dinosaur and Calculator examples, and case-study overviews.- `public/examples/dino-lab/index.html`: adjustable-speed mini-game, recovered rule, original-game check and browser analysis steps.- `public/first-investigation/index.html`: a guided Notes export investigation, from setup to a checked CSV prediction.- `public/showcase/index.html`: the case-study index.@@ -98,12 +98,15 @@ their provenance and the scope of the validation claims. The original executableand complete private Evidence records are not website assets.The homepage starts with a short installation prompt and the ordinary setup-command, followed immediately by the playable dinosaur example. Its game-precedes the prompt and code on small screens. The manual/agent comparison-then explains the investigation using the same dinosaur speed question.-Calculator follows as a native example: its excerpt comes from an installed-model DLL, and Microsoft’s public implementation supplies names and a-crosscheck. Its controls illustrate the percentage rule with generic inputs.+command, then explains what reverse engineering is and why someone would use+it. The manual/agent comparison introduces REA’s role before the examples.+Dinosaur is the first example; Calculator follows as the native example.+Both name the goal and the reason to inspect the program before showing the+demo. A labeled finding explains what REA returned, and the flow distinguishes+REA’s inspection from the agent’s interpretation and implementation.+Its game precedes the prompt and code on small screens. Calculator’s excerpt+comes from an installed model DLL; Microsoft’s public implementation supplies+names and a crosscheck. Its controls apply the percentage rule to generic inputs.The dinosaur example connects an inspected running script to a new playablemini-game. `public/assets/dino-speed.js` owns the recovered speed rule and replay;diff --git a/website/evidence/calculator-and-dino.md b/website/evidence/calculator-and-dino.mdindex e89138d54..b46d2113e 100644--- a/website/evidence/calculator-and-dino.md+++ b/website/evidence/calculator-and-dino.md@@ -1,8 +1,10 @@# Calculator and dinosaur beginner examplesEvidence collected on 9 October 2026 with the published REA 4.1.0 package.-The homepage offers compact setup first, then a playable dinosaur reconstruction,-a manual/agent comparison of that investigation, and the Calculator example.+The homepage offers compact setup first, then a reverse-engineering definition,+purpose and manual/agent comparison. Dinosaur is the first worked example;+Calculator is the second. Each states its goal, why the program is inspected,+what REA returned and how the agent uses it.Prompts and replies are examples based on thefindings below. Selected code and generic inputs are public; raw captures stayoutside the website.@@ -54,7 +56,8 @@ in the installed DLL. The public source commit is a crosscheck; it is not anidentified build commit for that installed package. No PDB symbols were loaded.The homepage's named C-like rule is an explanatory summary. Its `200 + 10%`-and `200 × 10%` displays are derived from that rule. Browser checks exercise+and `200 × 10%` controls compute those cases from that rule using the fixed+inputs 200 and 10. Browser checks exerciseboth percentage illustrations, their results, operator selection and reset.The Microsoft tests were inspected, not executed. A probe-owned Calculatorwindow could be inspected, but it was no longer present at the input-checkdiff --git a/website/figures.md b/website/figures.mdindex a87cf7b19..e02f894ef 100644--- a/website/figures.md+++ b/website/figures.md@@ -49,6 +49,12 @@ HTML. Calculator’s assembly comes from a real installed model DLL; the namedcalculation is a readable summary crosschecked against Microsoft’s public source. See[evidence/calculator-and-dino.md](evidence/calculator-and-dino.md).+The homepage explains reverse engineering before the worked examples. Each+example opens with its goal and reason for inspecting the program. A selected+highlight marks the intended result; the “REA returned” block identifies the+evidence. The flows label REA’s inspection and the agent’s interpretation or+reconstruction explicitly. Preserve this context when moving a demo.+The dinosaur sequence uses an HTML flow: inspect the loaded script, rebuild thespeed rule, then change and play. Its canvas mini-game and static SVG fallbackare authored code, without generated images or copied game sprites. The gamediff --git a/website/public/assets/home.js b/website/public/assets/home.jsindex 61f22231b..448052cc7 100644--- a/website/public/assets/home.js+++ b/website/public/assets/home.js@@ -11,13 +11,15 @@ function initializePercentDemo() {const render = () => {const adding = operation === "add";- const percent = adding ? 20 : 0.1;- const result = adding ? 220 : 20;+ const previous = 200;+ const current = 10;+ const percent = adding ? (current * previous) / 100 : current / 100;+ const result = adding ? previous + percent : previous * percent;const operator = adding ? "+" : "×";expression.textContent =stage === "result" ? `200 ${operator} ${percent} =` : `200 ${operator}`;display.textContent = String(- stage === "input" ? 10 : stage === "percent" ? percent : result,+ stage === "input" ? current : stage === "percent" ? percent : result,);equals.disabled = stage !== "percent";status.textContent =diff --git a/website/public/assets/styles.css b/website/public/assets/styles.cssindex 54bf52f67..55b04ee22 100644--- a/website/public/assets/styles.css+++ b/website/public/assets/styles.css@@ -1244,6 +1244,57 @@ pre code {color: var(--ink);font-weight: 500;}+.home-purpose {+ max-width: 850px;+ margin-bottom: 2rem;+ color: var(--muted);+}+.prose-highlight {+ padding: 0.04em 0.16em;+ border-radius: 2px;+ background: #e4ecf5;+ color: var(--accent);+ font-weight: 600;+ box-decoration-break: clone;+ -webkit-box-decoration-break: clone;+}+.case-brief {+ display: grid;+ grid-template-columns: minmax(0, 1fr) minmax(0, 1.3fr);+ gap: 2.5rem;+ margin: 0 0 2rem;+ padding-block: 1.2rem;+ border-top: 1px solid var(--line);+ border-bottom: 1px solid var(--line);+}+.case-brief dt,+.finding-label {+ margin-bottom: 0.45rem;+ font-size: 0.8rem;+ font-weight: 600;+ color: var(--accent);+}+.case-brief dd {+ margin: 0;+ color: var(--muted);+ font-size: 0.95rem;+}+.case-brief dd strong {+ color: var(--ink);+}+.rea-finding {+ margin-bottom: 1.4rem;+ padding-left: 1rem;+ border-left: 2px solid var(--accent);+}+.rea-finding > :last-child {+ margin: 0;+ font-size: 0.95rem;+ color: var(--muted);+}+.rea-finding strong {+ color: var(--ink);+}.home-role-comparison {display: grid;grid-template-columns: minmax(0, 1fr) minmax(0, 1fr);@@ -1416,6 +1467,14 @@ pre code {margin: 0;font-size: 0.9rem;}+.percent-rules dd strong,+.percent-rules dd code {+ display: block;+}+.percent-rules dd strong {+ margin-bottom: 0.25rem;+ font-weight: 500;+}.home-evidence-details {margin-top: 2rem;padding-block: 1rem;@@ -1541,6 +1600,10 @@ pre code {}}@media (max-width: 640px) {+ .case-brief {+ grid-template-columns: minmax(0, 1fr);+ gap: 1.2rem;+ }.home-hero {padding-block: 2.8rem;}diff --git a/website/public/examples/dino-lab/index.html b/website/public/examples/dino-lab/index.htmlindex a0578a487..38038c91d 100644--- a/website/public/examples/dino-lab/index.html+++ b/website/public/examples/dino-lab/index.html@@ -57,8 +57,10 @@<p class="eyebrow">Inspect → rebuild → change</p><h1>Rebuild the dinosaur’s speed rule.</h1><p class="lede">- 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. <strong>REA returned the running script;</strong>+ we used its rule to build this mini-game with+ <mark class="prose-highlight">adjustable speed.</mark></p></div><div class="article-layout">@@ -149,7 +151,7 @@</figure></section><section class="article-section" id="rule">- <h2>What REA found</h2>+ <h2>Read the script REA returned</h2><p>We inspected<a href="https://wayou.github.io/t-rex-runner/"diff --git a/website/public/index.html b/website/public/index.htmlindex 636ade994..1722767dd 100644--- a/website/public/index.html+++ b/website/public/index.html@@ -62,7 +62,7 @@what it does.</p><div class="actions">- <a class="button" href="#dinosaur">Play the dinosaur ↓</a>+ <a class="button" href="#what-is-re">See how REA works ↓</a><a class="text-link" href="get-started/">Setup guide</a></div></div>@@ -113,16 +113,125 @@</div></section>+ <section class="section" id="what-is-re">+ <div class="container">+ <div class="home-definition">+ <h2>What is reverse engineering?</h2>+ <p class="lede">+ Finding out how software works by+ <strong>examining the program itself.</strong>+ </p>+ </div>+ <p class="home-purpose">+ The goal: understand a feature well enough to+ <mark class="prose-highlight">explain it</mark>,+ <mark class="prose-highlight">change it</mark> or+ <mark class="prose-highlight">rebuild it.</mark>+ </p>+ <figure class="home-role-comparison">+ <div class="manual-investigation">+ <p class="comparison-label">Before REA · You investigate</p>+ <ol class="manual-steps">+ <li>+ <span>01</span>+ <div>+ <strong>Find the relevant code.</strong+ ><small+ >Locate the loaded script or the binary function.</small+ >+ </div>+ </li>+ <li>+ <span>02</span>+ <div>+ <strong>Work out its rules.</strong+ ><small>Follow the inputs, calls and settings.</small>+ </div>+ </li>+ <li>+ <span>03</span>+ <div>+ <strong>Use and check the result.</strong+ ><small+ >Explain the behavior, rebuild it or make a change.</small+ >+ </div>+ </li>+ </ol>+ </div>+ <div class="agent-investigation" id="ask-your-agent">+ <p class="comparison-label">With REA · You ask your agent</p>+ <div class="agent-terminal home-analysis-terminal">+ <div class="terminal-header">+ <span class="terminal-title"+ ><span class="terminal-dots" aria-hidden="true"+ ><i></i><i></i><i></i></span+ >Example question · Dinosaur game</span+ >+ <button+ class="copy-button"+ type="button"+ data-copy="home-analysis-prompt"+ aria-label="Copy dinosaur speed question"+ >+ Copy+ </button>+ </div>+ <p class="terminal-prompt">+ <span class="prompt-symbol" aria-hidden="true">›</span+ ><span id="home-analysis-prompt"+ >Use REA to inspect this dinosaur game. Why does it get+ faster? Show the speed rule.</span+ ><span class="terminal-cursor" aria-hidden="true"></span>+ </p>+ <div class="agent-reply">+ <p class="reply-label">+ Example explanation from the findings+ </p>+ <p>+ The game adds a little speed on each update. Its script sets+ <strong+ >the starting speed, the increment and the stopping+ point.</strong+ >+ </p>+ </div>+ </div>+ </div>+ <figcaption>+ <strong+ >REA supplies code and observations from the program.</strong+ >+ Your agent uses that evidence to explain, rebuild or test a+ feature.+ </figcaption>+ </figure>+ </div>+ </section>+<section class="section" id="dinosaur"><div class="container"><div class="section-heading"><p class="eyebrow">Example 01 · Chrome’s dinosaur game</p>- <h2>Change the dinosaur’s speed.</h2>- <p>- Inspect the speed rule with REA, rebuild a small version, then- change the speed and play.- </p>+ <h2>Why does the dinosaur get faster?</h2></div>+ <dl class="case-brief">+ <div>+ <dt>Goal</dt>+ <dd>+ Rebuild the game with+ <mark class="prose-highlight">adjustable speed.</mark>+ </dd>+ </div>+ <div>+ <dt>Why reverse engineer it?</dt>+ <dd>+ To reproduce its acceleration, we need+ <strong>the rule in the running game</strong>: how fast it+ starts, how much it increases and when it stops.+ </dd>+ </div>+ </dl><div class="home-example-grid dino-example-grid"><figure class="dino-demo" data-dino-demo><p class="figure-title">Play the reconstruction</p>@@ -193,6 +302,14 @@></figure><div>+ <div class="rea-finding">+ <p class="finding-label">REA returned</p>+ <p>+ <strong>The script actually running in the page.</strong> The+ agent reads its update function and speed settings, then uses+ that rule in a new game.+ </p>+ </div><div class="agent-terminal home-analysis-terminal"><div class="terminal-header"><span class="terminal-title"@@ -243,28 +360,28 @@</div></div><figure class="workflow-figure dino-loop">- <p class="figure-title">From the running game to a new version</p>+ <p class="figure-title">What each part does</p><ol class="flow-steps"><li>- <span class="flow-label">01 · Inspect</span- ><span class="flow-node">REA returns the loaded script</span+ <span class="flow-label">01 · REA</span+ ><span class="flow-node">Read the running game’s script</span><span class="flow-note"- >The agent reads the update function and its speed- settings.</span+ >Return its actual code and settings to the agent.</span></li><li>- <span class="flow-label">02 · Rebuild</span- ><span class="flow-node">Use the recovered rule</span+ <span class="flow-label">02 · Your agent</span+ ><span class="flow-node">Rebuild the rule, add a control</span><span class="flow-note"- >Start at 6 and add 0.001 while speed is below 13.</span+ >Use the recovered acceleration in a small game with a speed+ slider.</span></li><li>- <span class="flow-label">03 · Change and play</span- ><span class="flow-node">Make speed adjustable</span+ <span class="flow-label">03 · You</span+ ><span class="flow-node">Change the speed and play</span><span class="flow-note"- >Keep the original acceleration, or choose your own+ >Try the original acceleration, then choose your ownpace.</span></li>@@ -322,129 +439,31 @@ SPEED: 6</code></pre></div></section>- <section class="section" id="what-is-re">- <div class="container">- <div class="home-definition">- <h2>What is reverse engineering?</h2>- <p class="lede">- Finding out how software works by examining the program.- </p>- </div>- <p class="home-question">- In the dinosaur example:- <strong>which code makes the game get faster?</strong>- </p>- <figure class="home-role-comparison">- <div class="manual-investigation">- <p class="comparison-label">Before REA · You investigate</p>- <ol class="manual-steps">- <li>- <span>01</span>- <div>- <strong>Find the script behind the game.</strong- ><small>Which loaded file controls the dinosaur?</small>- </div>- </li>- <li>- <span>02</span>- <div>- <strong>Find the update function.</strong- ><small>Where does the game change its speed?</small>- </div>- </li>- <li>- <span>03</span>- <div>- <strong>Recover the speed rule.</strong- ><small- >Follow the starting speed, increment and- threshold.</small- >- </div>- </li>- <li>- <span>04</span>- <div>- <strong>Check the result.</strong- ><small- >Replay the rule and compare it with the game.</small- >- </div>- </li>- </ol>- <div class="manual-code">- <p class="caption">Find this branch inside a 90 KB script:</p>- <code- >if (this.currentSpeed < this.config.MAX_SPEED) {<br />- this.currentSpeed += this.config.ACCELERATION;<br />- }</code- >- </div>- </div>- <div class="agent-investigation" id="ask-your-agent">- <p class="comparison-label">With REA · You ask your agent</p>- <div class="agent-terminal home-analysis-terminal">- <div class="terminal-header">- <span class="terminal-title"- ><span class="terminal-dots" aria-hidden="true"- ><i></i><i></i><i></i></span- >Example prompt · Dinosaur game</span- >- <button- class="copy-button"- type="button"- data-copy="home-analysis-prompt"- aria-label="Copy dinosaur speed question"- >- Copy- </button>- </div>- <p class="terminal-prompt">- <span class="prompt-symbol" aria-hidden="true">›</span- ><span id="home-analysis-prompt"- >Use REA to inspect this dinosaur game. Why does it get- faster? Show the speed rule.</span- ><span class="terminal-cursor" aria-hidden="true"></span>- </p>- <div class="agent-reply">- <p class="reply-label">- Example explanation from the findings- </p>- <p>- It starts at 6. Each update without a collision adds 0.001- while speed is below 13.- </p>- <p>- <strong- >After 4,000 updates, speed is 10.<br />- You can replay the rule to check it.</strong- >- </p>- </div>- </div>- <p class="agent-investigation-note">- Your agent uses REA to locate and read the code, then connects- the findings to your question.- </p>- </div>- <figcaption>- You describe the behavior. The agent carries out the investigation- with REA.- </figcaption>- </figure>- </div>- </section>-<section class="section" id="calculator"><div class="container"><div class="section-heading"><p class="eyebrow">Example 02 · Windows Calculator</p>- <h2>What does the % button actually do?</h2>- <p>- The answer depends on the operator. Compare addition and- multiplication.- </p>+ <h2>Why does 200 + 10% give 220?</h2></div>+ <dl class="case-brief">+ <div>+ <dt>Goal</dt>+ <dd>+ Explain the result and+ <mark class="prose-highlight"+ >recreate Calculator’s % rule.</mark+ >+ </dd>+ </div>+ <div>+ <dt>Why reverse engineer it?</dt>+ <dd>+ The same button uses+ <strong>different rules after + and ×.</strong> We inspect the+ installed app to find which number the percentage is applied to.+ </dd>+ </div>+ </dl><div class="home-example-grid"><figure class="percent-figure" data-percent-demo><p class="figure-title">Try the calculation</p>@@ -507,11 +526,45 @@ SPEED: 6</code></pre></figcaption></figure><div class="percent-explanation">- <h3>REA finds the branch. The agent explains it.</h3>+ <div class="rea-finding">+ <p class="finding-label">REA returned</p>+ <p>+ <strong+ >The % handler’s original instructions and decompiled+ code.</strong+ >+ The agent reads the two branches and explains which rule each+ operator uses.+ </p>+ </div><p>- The installed app’s calculation code checks for multiplication- or division before computing the percentage.+ For this example, <code>previous = 200</code> and+ <code>current = 10</code>.</p>+ <div class="agent-terminal">+ <div class="terminal-header">+ <span class="terminal-title"+ ><span class="terminal-dots" aria-hidden="true"+ ><i></i><i></i><i></i></span+ >Example prompt · Calculator</span+ >+ <button+ class="copy-button"+ type="button"+ data-copy="calculator-analysis-prompt"+ aria-label="Copy Calculator analysis prompt"+ >+ Copy+ </button>+ </div>+ <p class="terminal-prompt">+ <span class="prompt-symbol" aria-hidden="true">›</span+ ><span id="calculator-analysis-prompt"+ >Use REA to inspect Windows Calculator. Why does 200 + 10%+ give 220? Show the code behind the % button.</span+ ><span class="terminal-cursor" aria-hidden="true"></span>+ </p>+ </div><div class="code-block"><div class="code-header"><span>Readable summary of the % handler</span>@@ -524,44 +577,54 @@ SPEED: 6</code></pre></div><dl class="percent-rules"><div>- <dt>Addition</dt>- <dd><code>200 + 10% → 200 + 20 → 220</code></dd>+ <dt>With +</dt>+ <dd>+ <strong>Take 10% of the first number.</strong+ ><code>10% of 200 = 20 → 200 + 20 = 220</code>+ </dd></div><div>- <dt>Multiplication</dt>- <dd><code>200 × 10% → 200 × 0.1 → 20</code></dd>+ <dt>With ×</dt>+ <dd>+ <strong>Turn 10% into 0.1.</strong+ ><code>200 × 0.1 = 20</code>+ </dd></div></dl></div></div>- <details class="home-evidence-details">- <summary>See the real code and how the answer was checked</summary>- <ol class="flow-steps calculator-trace">+ <figure class="workflow-figure calculator-trace">+ <p class="figure-title">From the installed app to an explanation</p>+ <ol class="flow-steps"><li>- <span class="flow-label">01 · Inspect calc.exe</span- ><span class="flow-node">A launcher</span+ <span class="flow-label">01 · REA reads calc.exe</span+ ><span class="flow-node">It launches the Calculator app</span><span class="flow-note"- >REA finds <code>ShellExecuteW</code> opening- <code>ms-calculator:</code>.</span+ >The code opens <code>ms-calculator:</code>. The agent then+ selects the installed app’s library.</span></li><li>- <span class="flow-label">02 · Inspect the app</span- ><span class="flow-node">CalcViewModel.dll</span+ <span class="flow-label">02 · REA reads the library</span+ ><span class="flow-node">Return the % handler’s code</span><span class="flow-note"- >Its % handler checks two operator IDs and uses the constant+ >The function checks the operator and uses the constant<code>100</code>.</span></li><li>- <span class="flow-label">03 · Interpret and check</span- ><span class="flow-node">Two percentage rules</span+ <span class="flow-label">03 · Your agent interprets it</span+ ><span class="flow-node">Explain and reproduce the rules</span><span class="flow-note"- >Microsoft’s public implementation and unit tests explain the- same distinction.</span+ >Crosscheck the branch with Microsoft’s source, then try + and+ × above.</span></li></ol>+ </figure>+ <details class="home-evidence-details">+ <summary>See the real code and how the answer was checked</summary>+<div class="code-comparison"><div class="code-block"><div class="code-header">@@ -585,30 +648,7 @@ SPEED: 6</code></pre>0x64 = 100</code></pre></div></div>- <div class="agent-terminal">- <div class="terminal-header">- <span class="terminal-title"- ><span class="terminal-dots" aria-hidden="true"- ><i></i><i></i><i></i></span- >Example prompt · Calculator</span- >- <button- class="copy-button"- type="button"- data-copy="calculator-analysis-prompt"- aria-label="Copy Calculator analysis prompt"- >- Copy- </button>- </div>- <p class="terminal-prompt">- <span class="prompt-symbol" aria-hidden="true">›</span- ><span id="calculator-analysis-prompt"- >Use REA to inspect Windows Calculator. Why does 200 + 10%- give 220? Show the code behind the % button.</span- ><span class="terminal-cursor" aria-hidden="true"></span>- </p>- </div>+<p class="caption">Inspected with REA 4.1.0: Windows Calculator 11.2508.4.0, x64. Thereadable summary uses names from Microsoft’s public source todiff --git a/website/style-guide.md b/website/style-guide.mdindex 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 promptand 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 amanual/agent comparison. Let returned evidence make REA's contribution visible.