Primary sources for technical claims.
We check setup commands, capabilities and constraints against the official REA repository and guides. Publication dates describe when our page was published; a linked investigation may describe a different package version and date. We preserve that distinction.
Tested means a named test.
The Pocket Notes lab retains the actual REA output from static analysis of our five-file learning fixture on 27 October 2026. It does not claim a runtime Electron session or successful save. The report includes artifact identity, counts, coverage and limitations.
Other pages are marked as documented workflows, explainers, prompts, or attributed case studies. An external result remains the original investigator's result until independently reproduced.
Screenshots should help you find the right thing.
Procedural guides use relevant screenshots and descriptive captions. Each numbered procedural step has a screenshot of actual REA CLI output, recorded locally with REA 6.8.0 and rendered in xterm.js. jq projections preserve returned values. Captions distinguish REA facts from numbered source excerpts, setup dry runs and runtime evidence. The downloadable capture kit retains the full analysis, exact commands and view requests. The separate learning workbench remains a reading aid. Orange callouts occupy reserved space so they do not cover source text. Screenshots can be expanded and the underlying evidence remains available.
Community reports are useful context.
Creator videos and forum posts reveal questions, demonstrations and failures worth investigating. They do not by themselves verify a technical claim. We attribute reports, avoid unsupported popularity numbers, and describe engagement opportunities as editorial judgments rather than measured demand.
No invented firsthand story.
We write in a curious, direct tone. We do not borrow another writer's personal experiments or present outside experiences as our own. AI-assisted drafting is disclosed on the About page, and a polished explanation still needs a source or a clearly labeled hypothesis.
Corrections and maintenance.
If a command changes, the relevant guide needs to be rechecked against the current release before being described as current. Readers can compare linked sources and use the official project's issue tracker for reproducible REA defects. This site does not have a monitored correction inbox at launch.
For practical reading, use the evidence checklist. For the original project, visit morluto/rea.