About REA Tool

An independent learning resource

This site is not affiliated with the REA maintainers. REA itself is developed in the official repository; its official website is rea.tools. Our tutorials link to upstream documentation and investigations while adding explanations, teaching interfaces and reproducible checks.

How we check our guides

Every investigation should connect a concrete question to identifiable evidence. When we use a package, source snapshot or upstream report, we name the version or link to the source. A page’s reviewed date describes that review, not a promise that every later release behaves identically.

• Observed code: a file, instruction or reported tool result supports what we can see statically.
• Upstream results: a linked project reports a run or comparison. We identify it as that project’s result.
• Local checks: we state what this site actually executed, the inputs used, and the scope of the result.
• Teaching illustrations: new diagrams and browser interactions explain a rule. They are not recordings of the original application.

Try the checks yourself

The slugify investigation includes a reproduction kit. The Aegis guide explains its public TOTP reference vectors. The four newer labs share downloadable rules, executable checks and a numeric results record.

Matching a set of inputs supports the behavior tested. It does not prove that an entire game, application or operating-system integration has been reconstructed.

What our experiments leave out

The dinosaur lab uses new drawing and collision code around a documented acceleration rule. The TH04 diagram approximates pointer aiming rather than reproducing the original iatan2 helper. The DX-Ball tone illustrates direction with Web Audio rather than emulating the game’s audio engine. The calculator lab models one two-operand percentage sequence.

Versions and corrections

If your result differs, compare the target version, tool version, input and test scope with the article. Follow the source links to check newer upstream documentation. Our dated examples remain useful as reproducible snapshots; changes to their claims should be accompanied by an updated explanation or check.

Publication credit is given to REA Tool as this site’s publisher. Upstream investigations retain their own attribution. For an issue with the REA software, use the project’s official issue tracker; that tracker is maintained by the REA project, not this site.