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.
- Targets
- Game · Website
- Category
- Official REA: case studies
- Relationship
- Official REA case study
- Sources reviewed
Requirements & limits
- Scope: The recorded target is wayou’s HTTP browser edition at the cited revision, not chrome://dino/. Source and observation hashes identify that edition.
- Attribution: After read-only inspection, a separate Playwright controller disabled future scheduling and obstacles to call the original update function under controlled conditions.
- Limits: The reconstructed claim is limited to acceleration. Drawing, jumping, collisions and controls in the teaching game are newly authored, not independently recovered original gameplay.
- Testing evidence: Public result tables and code document the author’s checks. The cited original-source excerpts retain Chromium attribution and BSD-3-Clause terms.
About this entry
The description was reviewed against primary sources.
Primary sources
- website/evidence/calculator-and-dino.md GitHub · morluto/rea · Revision c360cfc
- website/public/assets/licenses/dinosaur.txt GitHub · morluto/rea · Revision c360cfc
More in Websites
- rauchg.com: rebuilding an RSC blog from captured Flight output · Case study
- BaoCut Slides: adapting an interactive web editor · Case study
- REA in Claude Code: an isolated static-analysis A/B trial · Case study
- Dinosaur runner: an REA-inspected speed rule rebuilt with Codex · Case study
- Terminal: a Rust terminal informed by TradingView chart research · Case study
- BaoCut Design: porting reconstructed canvas and design-system editors · Case study