An independent REA learning guide, plus a small investigation-question template

[zenanythin]

I maintain Reverse Engineering Anything, a free, independent learning guide for REA. I am not an upstream REA author. The site collects installation help, coding-client setup paths, a CLI reference, troubleshooting, and links to the official case studies. It does not accept uploaded binaries or run a hosted analysis service.

The intended starting point is a developer with one concrete behavior to understand. The homepage lets you select a client and see a setup-command example. That selection produces a command; it does not establish that your package, provider, or current agent session is ready. For authoritative requirements and releases, use morluto/rea and rea.tools.

Here is a small question template you can use without visiting the site:

Target/build:
Starting state:
One action or input:
Documentation/source reference and version (or not available):
Expected output based on that source (or unknown):
Observed output:
Question this observation raises:
Evidence reference (file/span, trace, or reproducible steps):
Possible explanation A:
Possible explanation B:
One next check that could distinguish A from B:
What remains unknown:

For expected behavior, cite the documentation, source, or known-good version that supports it. If you have not established an expectation or run the observation, keep that field unknown rather than treating an assumption as a reproduced mismatch.

For example, “Why does search match this title but not that one?” is easier to investigate than “Clone this application.” Before choosing a tool, write the two inputs and their actual observed outputs. If you only have a source-code reference, leave the runtime outcome unknown until you have observed it. A reconstructed implementation and a verified behavioral match are separate milestones.

This is a documentation project and planning aid, not a new REA analysis result. I have checked the guide's navigation and command-selector behavior; I am not claiming an upstream engine or target-analysis test from those website checks.

Posted by the independent guide maintainer, with AI assistance in drafting. Corrections to confusing setup explanations or unclear separation from upstream documentation are welcome.

[XinwangTao]

这个独立学习指南对新手 onboarding 很有价值，尤其是「首页选择客户端 → 拿到 setup 命令示例」的路径，把安装辅助和权威文档边界划得很清楚。对问题模板有一个小建议：可以在五问之后加一个「与文档/预期对照」字段（如 Expected output vs Observed output），这样提问者顺手就能把调查结论直接映射到 upstream issue 模板里的 Area / Observed behavior / Expected behavior，转化高质量 bug 报告的成本会更低。