Case study
Dinosaur runner: recovering one acceleration rule
REA’s documented teaching case inspects the HTTP t-rex-runner edition and reconstructs its speed-update rule. A separate controlled original-game check and a new demonstration compare update counts, including the floating-point step that crosses the nominal speed threshold.
Requirements and limitations
- The recorded target is wayou’s HTTP browser edition at the cited revision, not chrome://dino/. Source and observation hashes identify that edition.
- After read-only inspection, a separate Playwright controller disabled future scheduling and obstacles to call the original update function under controlled conditions; this was not passive REA behavior.
- The reconstructed claim is limited to acceleration. Drawing, jumping, collisions and controls in the teaching game are newly authored, not independently recovered original gameplay.
- Public result tables and code document the author’s checks; this catalog did not rerun them. The cited original-source excerpts retain Chromium attribution and BSD-3-Clause terms.
About this entry
- Type
- Case study
- Category
- Official REA: case studies
- Relationship
- Official REA case study
- Targets
- Game · Website
Sources reviewed
The description was reviewed against primary sources. This does not establish runtime testing, security auditing or verified compatibility.